summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
Diffstat (limited to 'Doc')
-rw-r--r--Doc/ext.tex2
-rw-r--r--Doc/ext/ext.tex2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/ext.tex b/Doc/ext.tex
index fc56a80..01d2428 100644
--- a/Doc/ext.tex
+++ b/Doc/ext.tex
@@ -240,7 +240,7 @@ you have already created) when you return an error indicator!
The choice of which exception to raise is entirely yours. There are
predeclared \C{} objects corresponding to all built-in Python exceptions,
-e.g. \cdata{PyExc_ZeroDevisionError} which you can use directly. Of
+e.g. \cdata{PyExc_ZeroDivisionError} which you can use directly. Of
course, you should choose exceptions wisely --- don't use
\cdata{PyExc_TypeError} to mean that a file couldn't be opened (that
should probably be \cdata{PyExc_IOError}). If something's wrong with
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index fc56a80..01d2428 100644
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -240,7 +240,7 @@ you have already created) when you return an error indicator!
The choice of which exception to raise is entirely yours. There are
predeclared \C{} objects corresponding to all built-in Python exceptions,
-e.g. \cdata{PyExc_ZeroDevisionError} which you can use directly. Of
+e.g. \cdata{PyExc_ZeroDivisionError} which you can use directly. Of
course, you should choose exceptions wisely --- don't use
\cdata{PyExc_TypeError} to mean that a file couldn't be opened (that
should probably be \cdata{PyExc_IOError}). If something's wrong with