summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTerry Jan Reedy <tjreedy@udel.edu>2014-09-30 23:07:49 (GMT)
committerTerry Jan Reedy <tjreedy@udel.edu>2014-09-30 23:07:49 (GMT)
commitb6271f2d2b3f893ebf80f7ede85b70bd789c1efb (patch)
tree58bbe0200cd810cdffbc61ebc3ebba0ec1133ce5
parent97e9ec688c7ea49c61c803f1c87b183e32b3661c (diff)
downloadcpython-b6271f2d2b3f893ebf80f7ede85b70bd789c1efb.zip
cpython-b6271f2d2b3f893ebf80f7ede85b70bd789c1efb.tar.gz
cpython-b6271f2d2b3f893ebf80f7ede85b70bd789c1efb.tar.bz2
Issue 22465: grammar, number agreement.
-rw-r--r--Doc/reference/datamodel.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst
index d401ee0..e992f11 100644
--- a/Doc/reference/datamodel.rst
+++ b/Doc/reference/datamodel.rst
@@ -222,7 +222,7 @@ Ellipsis
at the mercy of the underlying machine architecture (and C or Java
implementation) for the accepted range and handling of overflow. Python does not
support single-precision floating point numbers; the savings in processor and
- memory usage that are usually the reason for using these is dwarfed by the
+ memory usage that are usually the reason for using these are dwarfed by the
overhead of using objects in Python, so there is no reason to complicate the
language with two kinds of floating point numbers.