Typo: propogate -> propagate

Thomas Heller · Thomas Heller · commit ead60e5d1c24 · 2002-12-06T22:42:13.000Z
Bugfix candidate.
diff --git a/Doc/api/exceptions.tex b/Doc/api/exceptions.tex
@@ -19,7 +19,7 @@ \chapter{Exception Handling \label{exceptionHandling}}
 \emph{not} continue normally if it is not prepared to handle the
 error.  If returning due to an error, it is important to indicate to
 the caller that an error has been set.  If the error is not handled or
-carefully propogated, additional calls into the Python/C API may not
+carefully propagated, additional calls into the Python/C API may not
 behave as intended and may fail in mysterious ways.
 
 The error indicator consists of three Python objects corresponding to
diff --git a/Doc/api/init.tex b/Doc/api/init.tex
@@ -657,7 +657,7 @@ \section{Thread State and the Global Interpreter Lock
   state information.  Each extension should use a unique key to use to
   store state in the dictionary.  If this function returns \NULL, an
   exception has been raised and the caller should allow it to
-  propogate.
+  propagate.
 \end{cfuncdesc}
 
 
@@ -715,7 +715,7 @@ \section{Profiling and Tracing \label{profiling}}
   processed after which the exception becomes set within the frame
   being executed.  The effect of this is that as exception propogation
   causes the Python stack to unwind, the callback is called upon
-  return to each frame as the exception propogates.  Only trace
+  return to each frame as the exception propagates.  Only trace
   functions receives these events; they are not needed by the
   profiler.
 \end{cvardesc}
