summaryrefslogtreecommitdiff
path: root/Doc/howto
diff options
context:
space:
mode:
authordelirious-lettuce <delirious.lettuce@gmail.com>2017-05-19 14:37:57 -0600
committerSerhiy Storchaka <storchaka@gmail.com>2017-05-19 23:37:57 +0300
commit3378b2062c7fbb77a9b5e6d315d6b94160fac69a (patch)
tree7cfeb0047ea14f4a77c4fb5a6fd4a233120c96e0 /Doc/howto
parenta632d00a1cbb6f4f8978cb45dd9789658cceb7c8 (diff)
downloadcpython-git-3378b2062c7fbb77a9b5e6d315d6b94160fac69a.tar.gz
Fix typos in multiple `.rst` files (#1668)
Diffstat (limited to 'Doc/howto')
-rw-r--r--Doc/howto/logging-cookbook.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst
index bb79bb1748..6498ea5695 100644
--- a/Doc/howto/logging-cookbook.rst
+++ b/Doc/howto/logging-cookbook.rst
@@ -1683,7 +1683,7 @@ Implementing structured logging
-------------------------------
Although most logging messages are intended for reading by humans, and thus not
-readily machine-parseable, there might be cirumstances where you want to output
+readily machine-parseable, there might be circumstances where you want to output
messages in a structured format which *is* capable of being parsed by a program
(without needing complex regular expressions to parse the log message). This is
straightforward to achieve using the logging package. There are a number of