summaryrefslogtreecommitdiffstats
path: root/Doc/api/api.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2001-05-21 15:03:35 (GMT)
committerFred Drake <fdrake@acm.org>2001-05-21 15:03:35 (GMT)
commitfc43d00c17ed016337fbac46a532c809321d6a3c (patch)
tree97a5f27a3878674a572b99261c6601039dfbd1b5 /Doc/api/api.tex
parent3c6b148a676f95e074b5cf6b5c7c060f65d0a16d (diff)
downloadcpython-fc43d00c17ed016337fbac46a532c809321d6a3c.zip
cpython-fc43d00c17ed016337fbac46a532c809321d6a3c.tar.gz
cpython-fc43d00c17ed016337fbac46a532c809321d6a3c.tar.bz2
Typo: "that" --> "than"
This closes SF bug #425320.
Diffstat (limited to 'Doc/api/api.tex')
-rw-r--r--Doc/api/api.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index e7ba299..9d3eb3e 100644
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -55,7 +55,7 @@ Writing an extension module is a relatively well-understood process,
where a ``cookbook'' approach works well. There are several tools
that automate the process to some extent. While people have embedded
Python in other applications since its early existence, the process of
-embedding Python is less straightforward that writing an extension.
+embedding Python is less straightforward than writing an extension.
Many API functions are useful independent of whether you're embedding
or extending Python; moreover, most applications that embed Python