From: Greg Ward <gward@python.net>
Date: Wed, 8 Jan 2003 03:02:26 +0000 (+0000)
Subject: Rewrite awkward/ungrammatical sentence.
X-Git-Tag: v2.3c1~2533
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d4fee28717379b071d5db894d0fd7599dde1fcc6;p=python

Rewrite awkward/ungrammatical sentence.
Typo fix.
---

diff --git a/Doc/ext/newtypes.tex b/Doc/ext/newtypes.tex
index efe1c7b86c..631a37a64c 100644
--- a/Doc/ext/newtypes.tex
+++ b/Doc/ext/newtypes.tex
@@ -52,8 +52,8 @@ typedef struct {
 } noddy_NoddyObject;
 \end{verbatim}
 
-This is what a Noddy object will contain.  In this case nothing more
-than every Python object contains - a refcount and a pointer to a type
+This is what a Noddy object will contain---in this case, nothing more
+than every Python object contains, namely a refcount and a pointer to a type
 object.  These are the fields the \code{PyObject_HEAD} macro brings
 in.  The reason for the macro is to standardize the layout and to
 enable special debugging fields in debug builds.  Note that there is
@@ -61,7 +61,7 @@ no semicolon after the \code{PyObject_HEAD} macro; one is included in
 the macro definition.  Be wary of adding one by accident; it's easy to
 do from habit, and your compiler might not complain, but someone
 else's probably will!  (On Windows, MSVC is known to call this an
-error and refuse to produce compiled code.)
+error and refuse to compile the code.)
 
 For contrast, let's take a look at the corresponding definition for
 standard Python integers: