[Python-checkins] r62228 - peps/trunk/pep-3116.txt

[andrew.kuchling]

Author: andrew.kuchling
Date: Tue Apr  8 23:24:20 2008
New Revision: 62228

Modified:
   peps/trunk/pep-3116.txt
Log:
Typo fix

Modified: peps/trunk/pep-3116.txt
==============================================================================
--- peps/trunk/pep-3116.txt	(original)
+++ peps/trunk/pep-3116.txt	Tue Apr  8 23:24:20 2008
@@ -252,7 +252,7 @@
 future reads are forced to go back to the disk).
 
 *Q: Do we want to mandate in the specification that switching between
-reading to writing on a read-write object implies a .flush()?  Or is
+reading and writing on a read-write object implies a .flush()?  Or is
 that an implementation convenience that users should not rely on?*
 
 For a read-only ``BufferedRandom`` object, ``.writable()`` returns