From: Benjamin Peterson <benjamin@python.org>
Date: Sat, 30 Jul 2011 17:26:27 +0000 (-0500)
Subject: transition move technically correct to obviously so
X-Git-Tag: v3.3.0a1~1798
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=98f2b9bff0c3d884fdcf827a10b856afcde13bc2;p=python

transition move technically correct to obviously so
---

diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst
index 2840055a94..8a117ba668 100644
--- a/Doc/library/stdtypes.rst
+++ b/Doc/library/stdtypes.rst
@@ -2706,7 +2706,7 @@ The Null Object
 
 This object is returned by functions that don't explicitly return a value.  It
 supports no special operations.  There is exactly one null object, named
-``None`` (a built-in name).  Calling ``type(None)`` produces the same singleton.
+``None`` (a built-in name).  ``type(None)()`` produces the same singleton.
 
 It is written as ``None``.
 
@@ -2718,7 +2718,7 @@ The Ellipsis Object
 
 This object is commonly used by slicing (see :ref:`slicings`).  It supports no
 special operations.  There is exactly one ellipsis object, named
-:const:`Ellipsis` (a built-in name).  Calling ``type(Ellipsis)`` produces the
+:const:`Ellipsis` (a built-in name).  ``type(Ellipsis)()`` produces the
 :const:`Ellipsis` singleton.
 
 It is written as ``Ellipsis`` or ``...``.
@@ -2729,8 +2729,8 @@ The NotImplemented Object
 
 This object is returned from comparisons and binary operations when they are
 asked to operate on types they don't support. See :ref:`comparisons` for more
-information.  There is exactly one ``NotImplemented`` object.  Calling
-``type(NotImplemented)`` produces the singleton instance.
+information.  There is exactly one ``NotImplemented`` object.
+``type(NotImplemented)()`` produces the singleton instance.
 
 It is written as ``NotImplemented``.