[Python-checkins] r69840 - in python/trunk/Doc/c-api: intro.rst veryhigh.rst

Sat Feb 21 20:09:40 CET 2009

Author: georg.brandl
Date: Sat Feb 21 20:09:40 2009
New Revision: 69840
Log:
#5338, #5339: two types in the API manual.
Modified:
 python/trunk/Doc/c-api/intro.rst
 python/trunk/Doc/c-api/veryhigh.rst
Modified: python/trunk/Doc/c-api/intro.rst
==============================================================================

--- python/trunk/Doc/c-api/intro.rst	(original)
+++ python/trunk/Doc/c-api/intro.rst	Sat Feb 21 20:09:40 2009
@@ -187,7 +187,7 @@
 the caller is said to *borrow* the reference. Nothing needs to be done for a
 borrowed reference.
 
-Conversely, when a calling function passes it a reference to an object, there
+Conversely, when a calling function passes in a reference to an object, there
 are two possibilities: the function *steals* a reference to the object, or it
 does not. *Stealing a reference* means that when you pass a reference to a
 function, that function assumes that it now owns that reference, and you are not
Modified: python/trunk/Doc/c-api/veryhigh.rst
==============================================================================
--- python/trunk/Doc/c-api/veryhigh.rst	(original)
+++ python/trunk/Doc/c-api/veryhigh.rst	Sat Feb 21 20:09:40 2009
@@ -16,7 +16,7 @@
 :const:`Py_file_input`, and :const:`Py_single_input`. These are described
 following the functions which accept them as parameters.
 
-Note also that several of these functions take :ctype:`FILE\*` parameters. On
+Note also that several of these functions take :ctype:`FILE\*` parameters. One
 particular issue which needs to be handled carefully is that the :ctype:`FILE`
 structure for different C libraries can be different and incompatible. Under
 Windows (at least), it is possible for dynamically linked extensions to actually
