summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorMartin Panter <vadmium+py@gmail.com>2016-05-08 13:48:10 (GMT)
committerMartin Panter <vadmium+py@gmail.com>2016-05-08 13:48:10 (GMT)
commitf0564164bab43f078c9f84f334d72ddb0e69110c (patch)
treec932a0e51179ab15c414b95f280815f0901ac71a /Doc
parent129fe04d4deec15f9ca0ee79776e0c4335fc12e7 (diff)
downloadcpython-f0564164bab43f078c9f84f334d72ddb0e69110c.zip
cpython-f0564164bab43f078c9f84f334d72ddb0e69110c.tar.gz
cpython-f0564164bab43f078c9f84f334d72ddb0e69110c.tar.bz2
Fix typos in comments, documentation and test method names
Diffstat (limited to 'Doc')
-rw-r--r--Doc/howto/logging-cookbook.rst2
-rw-r--r--Doc/reference/simple_stmts.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst
index 57b4333..e784acc 100644
--- a/Doc/howto/logging-cookbook.rst
+++ b/Doc/howto/logging-cookbook.rst
@@ -2231,7 +2231,7 @@ flushing behavior.
The example script has a simple function, ``foo``, which just cycles through
all the logging levels, writing to ``sys.stderr`` to say what level it's about
-to log at, and then actually logging a message that that level. You can pass a
+to log at, and then actually logging a message at that level. You can pass a
parameter to ``foo`` which, if true, will log at ERROR and CRITICAL levels -
otherwise, it only logs at DEBUG, INFO and WARNING levels.
diff --git a/Doc/reference/simple_stmts.rst b/Doc/reference/simple_stmts.rst
index 5f60540..79a46e2 100644
--- a/Doc/reference/simple_stmts.rst
+++ b/Doc/reference/simple_stmts.rst
@@ -237,7 +237,7 @@ Assignment of an object to a single target is recursively defined as follows.
phase, causing less detailed error messages.
Although the definition of assignment implies that overlaps between the
-left-hand side and the right-hand side are 'simultanenous' (for example ``a, b =
+left-hand side and the right-hand side are 'simultaneous' (for example ``a, b =
b, a`` swaps two variables), overlaps *within* the collection of assigned-to
variables occur left-to-right, sometimes resulting in confusion. For instance,
the following program prints ``[0, 2]``::