"ZeroDevisionError" --> "ZeroDivisionError"

Thanks, AMK!

diff --git a/Doc/ext.tex b/Doc/ext.tex
index fc56a80323d4decfb66743aec616efd03f8acafc..01d2428a35c4f15e058fad590010d4f4b752f14d 100644 (file)
--- 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 fc56a80323d4decfb66743aec616efd03f8acafc..01d2428a35c4f15e058fad590010d4f4b752f14d 100644 (file)
--- 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