summaryrefslogtreecommitdiffstats
path: root/Doc/ext/newtypes.tex
diff options
context:
space:
mode:
authorGreg Ward <gward@python.net>2003-01-03 21:09:57 (GMT)
committerGreg Ward <gward@python.net>2003-01-03 21:09:57 (GMT)
commitfdf65d91060b727fa258205ac45b9dcd827e83f4 (patch)
treeec1375b810a2758862b6122e9e1d24b23274cb6b /Doc/ext/newtypes.tex
parent8fa8972d80b767306ff56f8108859d40a97b6228 (diff)
downloadcpython-fdf65d91060b727fa258205ac45b9dcd827e83f4.zip
cpython-fdf65d91060b727fa258205ac45b9dcd827e83f4.tar.gz
cpython-fdf65d91060b727fa258205ac45b9dcd827e83f4.tar.bz2
Grammatical fix: change possessive "it's" to "its".
Diffstat (limited to 'Doc/ext/newtypes.tex')
-rw-r--r--Doc/ext/newtypes.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/ext/newtypes.tex b/Doc/ext/newtypes.tex
index a82cd22..efe1c7b 100644
--- a/Doc/ext/newtypes.tex
+++ b/Doc/ext/newtypes.tex
@@ -198,7 +198,7 @@ oppourtunity --- in \cfunction{initnoddy()}.
0, /* ob_size */
\end{verbatim}
-The \member{ob_size} field of the header is not used; it's presence in
+The \member{ob_size} field of the header is not used; its presence in
the type structure is a historical artifact that is maintained for
binary compatibility with extension modules compiled for older
versions of Python. Always set this field to zero.
@@ -442,7 +442,7 @@ uniquely-identifying value for the object.
The \member{tp_str} handler is to \function{str()} what the
\member{tp_repr} handler described above is to \function{repr()}; that
is, it is called when Python code calls \function{str()} on an
-instance of your object. It's implementation is very similar to the
+instance of your object. Its implementation is very similar to the
\member{tp_repr} function, but the resulting string is intended for
human consumption. If \member{tp_str} is not specified, the
\member{tp_repr} handler is used instead.
@@ -880,7 +880,7 @@ XXX some fields need to be added here...
\end{verbatim}
These functions provide support for the iterator protocol. Any object
-which wishes to support iteration over it's contents (which may be
+which wishes to support iteration over its contents (which may be
generated during iteration) must implement the \code{tp_iter}
handler. Objects which are returned by a \code{tp_iter} handler must
implement both the \code{tp_iter} and \code{tp_iternext} handlers.