[Python-checkins] python/dist/src/Doc/api intro.tex, 1.6, 1.7 memory.tex, 1.2, 1.3

[rhettinger at users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/api
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3901/Doc/api

Modified Files:
	intro.tex memory.tex 
Log Message:
SF Patch #1093896:  miscellaneous doc typos



Index: intro.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/intro.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- intro.tex	31 Mar 2004 07:45:46 -0000	1.6
+++ intro.tex	1 Jan 2005 00:28:28 -0000	1.7
@@ -277,7 +277,7 @@
 The situation is slightly different for function return values.  
 While passing a reference to most functions does not change your 
 ownership responsibilities for that reference, many functions that 
-return a referece to an object give you ownership of the reference.
+return a reference to an object give you ownership of the reference.
 The reason is simple: in many cases, the returned object is created 
 on the fly, and the reference you get is the only reference to the 
 object.  Therefore, the generic functions that return object 

Index: memory.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/memory.tex,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- memory.tex	6 Apr 2002 09:14:33 -0000	1.2
+++ memory.tex	1 Jan 2005 00:28:28 -0000	1.3
@@ -134,7 +134,7 @@
 In addition, the following macro sets are provided for calling the
 Python memory allocator directly, without involving the C API functions
 listed above. However, note that their use does not preserve binary
-compatibility accross Python versions and is therefore deprecated in
+compatibility across Python versions and is therefore deprecated in
 extension modules.
 
 \cfunction{PyMem_MALLOC()}, \cfunction{PyMem_REALLOC()}, \cfunction{PyMem_FREE()}.