very minor typo

diff --git a/Doc/lib/libsocket.tex b/Doc/lib/libsocket.tex
index 3743100c54455737c6fea68489db87facc8b49c5..618c523df0eeb247a9d2f503ae9c02647c79a42a 100644 (file)
--- a/Doc/lib/libsocket.tex
+++ b/Doc/lib/libsocket.tex
@@ -17,7 +17,7 @@ The Python interface is a straightforward transliteration of the
 \UNIX{} system call and library interface for sockets to Python's
 object-oriented style: the \code{socket()} function returns a
 \dfn{socket object} whose methods implement the various socket system
-calls.  Parameter types are somewhat higer-level than in the C
+calls.  Parameter types are somewhat higher-level than in the C
 interface: as with \code{read()} and \code{write()} operations on Python
 files, buffer allocation on receive operations is automatic, and
 buffer length is implicit on send operations.

diff --git a/Doc/libsocket.tex b/Doc/libsocket.tex
index 3743100c54455737c6fea68489db87facc8b49c5..618c523df0eeb247a9d2f503ae9c02647c79a42a 100644 (file)
--- a/Doc/libsocket.tex
+++ b/Doc/libsocket.tex
@@ -17,7 +17,7 @@ The Python interface is a straightforward transliteration of the
 \UNIX{} system call and library interface for sockets to Python's
 object-oriented style: the \code{socket()} function returns a
 \dfn{socket object} whose methods implement the various socket system
-calls.  Parameter types are somewhat higer-level than in the C
+calls.  Parameter types are somewhat higher-level than in the C
 interface: as with \code{read()} and \code{write()} operations on Python
 files, buffer allocation on receive operations is automatic, and
 buffer length is implicit on send operations.