summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-04-13 00:53:42 (GMT)
committerFred Drake <fdrake@acm.org>1998-04-13 00:53:42 (GMT)
commit003d8da7799d88f42655ac7afdf5dc3010f75854 (patch)
tree2a09261843ec39d683f12c1db95ab020629dfb1e
parentb85fbec83ba3f423e6675ceb3b0630634ba9411e (diff)
downloadcpython-003d8da7799d88f42655ac7afdf5dc3010f75854.zip
cpython-003d8da7799d88f42655ac7afdf5dc3010f75854.tar.gz
cpython-003d8da7799d88f42655ac7afdf5dc3010f75854.tar.bz2
Typo: (and often severly limited) -- severely
Typo: (but not to the tuple or list into which the item it put!) -- is put Thanks, AMK!
-rw-r--r--Doc/api.tex4
-rw-r--r--Doc/api/api.tex4
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/api.tex b/Doc/api.tex
index ad54ec7..6039121 100644
--- a/Doc/api.tex
+++ b/Doc/api.tex
@@ -115,7 +115,7 @@ true iff the object pointed to by \var{a} is a Python list.
\label{refcounts}
The reference count is important because today's computers have a
-finite (and often severly limited) memory size; it counts how many
+finite (and often severely limited) memory size; it counts how many
different places there are that have a reference to an object. Such a
place could be another object, or a global (or static) \C{} variable, or
a local variable in some \C{} function. When an object's reference count
@@ -192,7 +192,7 @@ reference to the object, or it does not. Few functions steal
references; the two notable exceptions are
\cfunction{PyList_SetItem()} and \cfunction{PyTuple_SetItem()}, which
steal a reference to the item (but not to the tuple or list into which
-the item it put!). These functions were designed to steal a reference
+the item is put!). These functions were designed to steal a reference
because of a common idiom for populating a tuple or list with newly
created objects; for example, the code to create the tuple \code{(1,
2, "three")} could look like this (forgetting about error handling for
diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index ad54ec7..6039121 100644
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -115,7 +115,7 @@ true iff the object pointed to by \var{a} is a Python list.
\label{refcounts}
The reference count is important because today's computers have a
-finite (and often severly limited) memory size; it counts how many
+finite (and often severely limited) memory size; it counts how many
different places there are that have a reference to an object. Such a
place could be another object, or a global (or static) \C{} variable, or
a local variable in some \C{} function. When an object's reference count
@@ -192,7 +192,7 @@ reference to the object, or it does not. Few functions steal
references; the two notable exceptions are
\cfunction{PyList_SetItem()} and \cfunction{PyTuple_SetItem()}, which
steal a reference to the item (but not to the tuple or list into which
-the item it put!). These functions were designed to steal a reference
+the item is put!). These functions were designed to steal a reference
because of a common idiom for populating a tuple or list with newly
created objects; for example, the code to create the tuple \code{(1,
2, "three")} could look like this (forgetting about error handling for