Clarify the description of the creation of an owned reference from an API

function.
This closes SF bug #486657.

diff --git a/Doc/ext/extending.tex b/Doc/ext/extending.tex
index 6cd1137fd9657018ecac3b45fc74554777dd2ff7..e78e1d1f4b2c6a233e8bfaf076c8ed0ffcfadb8c 100644 (file)
--- a/Doc/ext/extending.tex
+++ b/Doc/ext/extending.tex
@@ -1291,11 +1291,11 @@ transferred with the reference or not.
 Most functions that return a reference to an object pass on ownership
 with the reference.  In particular, all functions whose function it is
 to create a new object, such as \cfunction{PyInt_FromLong()} and
-\cfunction{Py_BuildValue()}, pass ownership to the receiver.  Even if in
-fact, in some cases, you don't receive a reference to a brand new
-object, you still receive ownership of the reference.  For instance,
-\cfunction{PyInt_FromLong()} maintains a cache of popular values and can
-return a reference to a cached item.
+\cfunction{Py_BuildValue()}, pass ownership to the receiver.  Even if
+the object is not actually new, you still receive ownership of a new
+reference to that object.  For instance, \cfunction{PyInt_FromLong()}
+maintains a cache of popular values and can return a reference to a
+cached item.
 
 Many functions that extract objects from other objects also transfer
 ownership with the reference, for instance