From: Fred Drake <fdrake@acm.org>
Date: Fri, 3 Apr 1998 05:02:28 +0000 (+0000)
Subject: Capitalize "Python" for consistency.
X-Git-Tag: v1.5.1~247
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7e9d3148d124a14395378f3ee16b773e50da53e0;p=python

Capitalize "Python" for consistency.
---

diff --git a/Doc/api.tex b/Doc/api.tex
index 942c30a5c5..e0c3ad2a5b 100644
--- a/Doc/api.tex
+++ b/Doc/api.tex
@@ -2014,7 +2014,7 @@ The current implementation keeps an array of integer objects for all
 integers between \code{-1} and \code{100}, when you create an int in
 that range you actually just get back a reference to the existing
 object. So it should be possible to change the value of \code{1}. I
-suspect the behaviour of python in this case is undefined. :-)
+suspect the behaviour of Python in this case is undefined. :-)
 \end{cfuncdesc}
 
 \begin{cfuncdesc}{long}{PyInt_AS_LONG}{PyIntObject *io}
diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index 942c30a5c5..e0c3ad2a5b 100644
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -2014,7 +2014,7 @@ The current implementation keeps an array of integer objects for all
 integers between \code{-1} and \code{100}, when you create an int in
 that range you actually just get back a reference to the existing
 object. So it should be possible to change the value of \code{1}. I
-suspect the behaviour of python in this case is undefined. :-)
+suspect the behaviour of Python in this case is undefined. :-)
 \end{cfuncdesc}
 
 \begin{cfuncdesc}{long}{PyInt_AS_LONG}{PyIntObject *io}