From: Ezio Melotti <ezio.melotti@gmail.com>
Date: Sat, 29 Oct 2011 07:41:51 +0000 (+0300)
Subject: #13289: fix typo.
X-Git-Tag: v3.2.3rc1~460
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f78869e47eb9e4284e7c4d884e3f1f0ad822aef5;p=thirdparty%2FPython%2Fcpython.git

#13289: fix typo.
---

diff --git a/Lib/socketserver.py b/Lib/socketserver.py
index 73896081d1c6..0e2ba83d1d66 100644
--- a/Lib/socketserver.py
+++ b/Lib/socketserver.py
@@ -82,7 +82,7 @@ On the other hand, if you are building e.g. an HTTP server, where all
 data is stored externally (e.g. in the file system), a synchronous
 class will essentially render the service "deaf" while one request is
 being handled -- which may be for a very long time if a client is slow
-to reqd all the data it has requested.  Here a threading or forking
+to read all the data it has requested.  Here a threading or forking
 server is appropriate.
 
 In some cases, it may be appropriate to process part of a request