From: Ezio Melotti <ezio.melotti@gmail.com>
Date: Sat, 29 Oct 2011 07:40:20 +0000 (+0300)
Subject: #13289: fix typo.
X-Git-Tag: v2.7.3rc1~360
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d;p=python

#13289: fix typo.
---

diff --git a/Lib/SocketServer.py b/Lib/SocketServer.py
index f1fd78b86b..71b9caa973 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