[Python-checkins] Docs: Improved phrasing (GH-14069)
webhook-mailer at python.org
Fri Jun 21 00:43:17 EDT 2019
author: Aeros <44193521+aeros167 at users.noreply.github.com>
committer: Carol Willing <carolcode at willingconsulting.com>
Docs: Improved phrasing (GH-14069)
* Docs: Improved phrasing
Removed usage of second person pronouns in the section and made the assumption of "uneasiness" in code style transition more neutral.
* Removed trailing whitespace on line 34
diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index e2d63a0323da..387420c17bd1 100644
@@ -24,14 +24,16 @@ programmers will encounter a fragment of code like this::
Only the ``x++`` statement is executed if the condition is true, but the
-indentation leads you to believe otherwise. Even experienced C programmers will
-sometimes stare at it a long time wondering why ``y`` is being decremented even
+indentation leads many to believe otherwise. Even experienced C programmers will
+sometimes stare at it a long time wondering as to why ``y`` is being decremented even
for ``x > y``.
Because there are no begin/end brackets, Python is much less prone to
coding-style conflicts. In C there are many different ways to place the braces.
-If you're used to reading and writing code that uses one style, you will feel at
-least slightly uneasy when reading (or being required to write) another style.
+After becoming used to reading and writing code using a particular style,
+it is normal to feel somewhat uneasy when reading (or being required to write)
+in a different one.
Many coding styles place begin/end brackets on a line by themselves. This makes
programs considerably longer and wastes valuable screen space, making it harder
More information about the Python-checkins