From: Barry Warsaw <barry@python.org>
Date: Fri, 3 Jan 1997 20:19:05 +0000 (+0000)
Subject: very minor typo
X-Git-Tag: v1.5a1~594
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d44be3fdb77f5486a3eb0d886327718624495f0f;p=thirdparty%2FPython%2Fcpython.git

very minor typo
---

diff --git a/Doc/lib/libsocket.tex b/Doc/lib/libsocket.tex
index 3743100c5445..618c523df0ee 100644
--- 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 3743100c5445..618c523df0ee 100644
--- 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.