[Python-checkins] r61042 - peps/trunk/pep-3113.txt

[brett.cannon]

Author: brett.cannon
Date: Sun Feb 24 05:25:44 2008
New Revision: 61042

Modified:
   peps/trunk/pep-3113.txt
Log:
Minor typo.


Modified: peps/trunk/pep-3113.txt
==============================================================================
--- peps/trunk/pep-3113.txt	(original)
+++ peps/trunk/pep-3113.txt	Sun Feb 24 05:25:44 2008
@@ -47,7 +47,7 @@
 ``func_code`` attribute).
 
 But there is great difficulty when it comes to tuple parameters.  The
-existence of a tuple parameter is denoted by it name being made of a
+existence of a tuple parameter is denoted by its name being made of a
 ``.`` and a number in the ``co_varnames`` attribute of the function's
 code object.  This allows the tuple argument to be bound to a name
 that only the bytecode is aware of and cannot be typed in Python
@@ -171,7 +171,7 @@
 -------------
 
 In certain instances tuple parameters can be useful.  A common example
-is code that expect a two-item tuple that represents a Cartesian
+is code that expects a two-item tuple that represents a Cartesian
 point.  While true it is nice to be able to have the unpacking of the
 x and y coordinates for you, the argument is that this small amount of
 practical usefulness is heavily outweighed by other issues pertaining