summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorÉric Araujo <merwok@netwok.org>2011-05-25 18:13:29 +0200
committerÉric Araujo <merwok@netwok.org>2011-05-25 18:13:29 +0200
commit0a33d0b00566fef50ab14a03f787cbb9a563e406 (patch)
tree2647a77fd7f226559b03d79fa8f7dac2ad181240
parent5d617bf53b001ecd607e889e25b57423765a587c (diff)
downloadcpython-0a33d0b00566fef50ab14a03f787cbb9a563e406.tar.gz
Fix two typos
-rw-r--r--Doc/documenting/style.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/documenting/style.rst b/Doc/documenting/style.rst
index ade845c740..2548cb0a6c 100644
--- a/Doc/documenting/style.rst
+++ b/Doc/documenting/style.rst
@@ -135,7 +135,7 @@ Good example (establishing confident knowledge in the effective use of the langu
Economy of Expression
---------------------
-More documentation is not necessarily better documentation. Error on the side
+More documentation is not necessarily better documentation. Err on the side
of being succinct.
It is an unfortunate fact that making documentation longer can be an impediment
@@ -197,7 +197,7 @@ Audience
The tone of the tutorial (and all the docs) needs to be respectful of the
reader's intelligence. Don't presume that the readers are stupid. Lay out the
relevant information, show motivating use cases, provide glossary links, and do
-our best to connect-the-dots, but don't talk down to them or waste their time.
+your best to connect-the-dots, but don't talk down to them or waste their time.
The tutorial is meant for newcomers, many of whom will be using the tutorial to
evaluate the language as a whole. The experience needs to be positive and not