summaryrefslogtreecommitdiffstats
path: root/Doc/ref/ref3.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2001-07-14 02:12:27 (GMT)
committerFred Drake <fdrake@acm.org>2001-07-14 02:12:27 (GMT)
commit6e5e1d924cb58be4b1922f0087e3528517f161c1 (patch)
tree62146bca93958e5336e873505c0c9710e98a1617 /Doc/ref/ref3.tex
parent8da359bdc08cf97cf4820b0789c8ad8cfec36556 (diff)
downloadcpython-6e5e1d924cb58be4b1922f0087e3528517f161c1.zip
cpython-6e5e1d924cb58be4b1922f0087e3528517f161c1.tar.gz
cpython-6e5e1d924cb58be4b1922f0087e3528517f161c1.tar.bz2
Minor change to match the style guide.
Diffstat (limited to 'Doc/ref/ref3.tex')
-rw-r--r--Doc/ref/ref3.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ref/ref3.tex b/Doc/ref/ref3.tex
index 06155c0..9074a0b 100644
--- a/Doc/ref/ref3.tex
+++ b/Doc/ref/ref3.tex
@@ -210,7 +210,7 @@ These represent machine-level double precision floating point numbers.
You are at the mercy of the underlying machine architecture and
\C{} implementation for the accepted range and handling of overflow.
Python does not support single-precision floating point numbers; the
-savings in CPU and memory usage that are usually the reason for using
+savings in processor and memory usage that are usually the reason for using
these is 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.