@@ -17,9 +17,9 @@ \section{\module{asyncore} ---
1717`` more than one thing at a time.'' Multi-threaded programming is the
1818simplest and most popular way to do it, but there is another very
1919different technique, that lets youhave nearly all the advantages of
20- multi-threading, without actually using multiple threads. it 's really
20+ multi-threading, without actually using multiple threads. It 's really
2121only practical if your program is largely I/O bound. If your program
22- is CPU bound, then pre-emtpive scheduled threads are probably what
22+ is CPU bound, then pre-emptive scheduled threads are probably what
2323you really need. Network servers are rarely CPU-bound, however.
2424
2525If your operating system supports the \cfunction {select()} system call
@@ -28,7 +28,7 @@ \section{\module{asyncore} ---
2828I/O is taking place in the `` background.'' Although this strategy can
2929seem strange and complex, especially at first, it is in many ways
3030easier to understand and control than multi-threaded programming.
31- The module documented here solves manyof the difficult problems for
31+ The module documented here solves many of the difficult problems for
3232you, making the task of building sophisticated high-performance
3333network servers and clients a snap.
3434
@@ -115,16 +115,17 @@ \section{\module{asyncore} ---
115115In addition, there are the basic methods needed to construct and
116116manipulate `` channels,'' which are what we will call the socket
117117connections in this context. Note that most of these are nearly
118- identical to their \class { socket} partners.
118+ identical to their socket partners.
119119
120120\begin {methoddesc }{create_socket}{family, type}
121121 This is identical to the creation of a normal socket, and
122- will use the same options for creation. This means you will
123- need to reference the \refmodule {socket} module.
122+ will use the same options for creation. Refer to the
123+ \refmodule {socket} documentation for information on creating
124+ sockets.
124125\end {methoddesc }
125126
126127\begin {methoddesc }{connect}{address}
127- As with the normal \class { socket} object, \var {address} is a
128+ As with the normal socket object, \var {address} is a
128129 tuple with the first element the host to connect to, and the
129130 second the port.
130131\end {methoddesc }
0 commit comments