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

[george.yoshida]

Author: george.yoshida
Date: Fri May 18 03:30:16 2007
New Revision: 55424

Modified:
   peps/trunk/pep-3113.txt
Log:
fix typos


Modified: peps/trunk/pep-3113.txt
==============================================================================
--- peps/trunk/pep-3113.txt	(original)
+++ peps/trunk/pep-3113.txt	Fri May 18 03:30:16 2007
@@ -87,7 +87,7 @@
 
 As mentioned in `Introspection Issues`_, to handle tuple parameters
 the function's bytecode starts with the bytecode required to unpack
-the argument into the proper parameter names.  This means that their
+the argument into the proper parameter names.  This means that there
 is no special support required to implement tuple parameters and thus
 there is no loss of abilities if they were to be removed, only a
 possible convenience (which is addressed in
@@ -170,7 +170,7 @@
 -------------
 
 In certain instances tuple parameters can be useful.  A common example
-is code that expect a two-item tuple that reperesents a Cartesian
+is code that expect 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