Skip to content

Commit d006800

Browse files
aeroswillingc
authored andcommitted
Docs: Improved phrasing (pythonGH-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
1 parent b9600b0 commit d006800

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

Doc/faq/design.rst

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,14 +24,16 @@ programmers will encounter a fragment of code like this::
2424
z++;
2525

2626
Only the ``x++`` statement is executed if the condition is true, but the
27-
indentation leads you to believe otherwise. Even experienced C programmers will
28-
sometimes stare at it a long time wondering why ``y`` is being decremented even
27+
indentation leads many to believe otherwise. Even experienced C programmers will
28+
sometimes stare at it a long time wondering as to why ``y`` is being decremented even
2929
for ``x > y``.
3030

3131
Because there are no begin/end brackets, Python is much less prone to
3232
coding-style conflicts. In C there are many different ways to place the braces.
33-
If you're used to reading and writing code that uses one style, you will feel at
34-
least slightly uneasy when reading (or being required to write) another style.
33+
After becoming used to reading and writing code using a particular style,
34+
it is normal to feel somewhat uneasy when reading (or being required to write)
35+
in a different one.
36+
3537

3638
Many coding styles place begin/end brackets on a line by themselves. This makes
3739
programs considerably longer and wastes valuable screen space, making it harder

0 commit comments

Comments
 (0)