Changed all True/False/None to simple code markups, according to the …

…DevGuide
python · yyyyyyyan · Jul 11, 2020 · Jul 12, 2020 · Jul 12, 2020 · Jul 12, 2020
commit 06275f2dfaa10448970ac5dc21c81974c81d10ef
@@ -614,7 +614,7 @@ Notes:
   chance at implementing mixed-type comparison. If not, when a :class:`date`
   object is compared to an object of a different type, :exc:`TypeError` is raised
   unless the comparison is ``==`` or ``!=``. The latter cases return
-   :const:`False` or :const:`True`, respectively.
+   ``False`` or ``True``, respectively.

 In Boolean contexts, all :class:`date` objects are considered to be true.

@@ -1189,7 +1189,7 @@ Supported operations:
      chance at implementing mixed-type comparison. If not, when a :class:`.datetime`
      object is compared to an object of a different type, :exc:`TypeError` is raised
      unless the comparison is ``==`` or ``!=``. The latter cases return
-      :const:`False` or :const:`True`, respectively.
+      ``False`` or ``True``, respectively.

 Instance methods:

@@ -1660,7 +1660,7 @@ day, and subject to adjustment via a :class:`tzinfo` object.
   * ``fold in [0, 1]``.

   If an argument outside those ranges is given, :exc:`ValueError` is raised. All
-   default to ``0`` except *tzinfo*, which defaults to :const:`None`.
+   default to ``0`` except *tzinfo*, which defaults to ``None``.

 Class attributes:

@@ -1734,7 +1734,7 @@ subtracting their UTC offsets (obtained from ``self.utcoffset()``). In order
 to stop mixed-type comparisons from falling back to the default comparison by
 object address, when a :class:`.time` object is compared to an object of a
 different type, :exc:`TypeError` is raised unless the comparison is ``==`` or
-``!=``. The latter cases return :const:`False` or :const:`True`, respectively.
+``!=``. The latter cases return ``False`` or ``True``, respectively.

 .. versionchanged:: 3.3
  Equality comparisons between aware and naive :class:`~datetime.time` instances