Skip to content

Commit 598c569

Browse files
author
kuyan
committed
Correct spelling of 'aforementioned'.
1 parent 7298caa commit 598c569

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/writing/gotchas.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@ Common Gotchas
22
==============
33

44
For the most part, Python aims to be a clean and consistent language that
5-
avoids surprises, but there are a few cases where newcomers to the language
6-
often get tripped up.
5+
avoids surprises. However, there are a few cases that can be confusing to
6+
newcomers.
77

8-
Some of these are intentional but potentially surprising. Some could arguably
9-
be considered language warts. In general though, what follows is a collection
8+
Some of these cases are intentional but can be potentially surprising. Some
9+
could arguably be considered language warts. In general though, what follows is a collection
1010
of potentially tricky behavior that might seem strange at first glance, but is
1111
generally sensible once you're aware of the underlying cause for the surprise.
1212

@@ -157,7 +157,7 @@ What You Should Do Instead
157157
~~~~~~~~~~~~~~~~~~~~~~~~~~
158158

159159
The most general solution is arguably a bit of a hack. Due to Python's
160-
afformentioned behavior concerning evaluating default arguments to functions
160+
aforementioned behavior concerning evaluating default arguments to functions
161161
(see :ref:`default_args`), you can create a closure that binds immediately to
162162
its arguments by using a default arg like so:
163163

0 commit comments

Comments
 (0)