@@ -454,7 +454,7 @@ There are two factors that produce this result:
454454 (the list), and both ``x `` and ``y `` refer to it.
4554552) Lists are :term: `mutable `, which means that you can change their content.
456456
457- After the call to :meth: `~list. append
457+ After the call to :meth: `! append
458458changed from ``[] `` to ``[10] ``. Since both the variables refer to the same
459459object, using either name accesses the modified value ``[10] ``.
460460
@@ -1397,7 +1397,7 @@ To see why this happens, you need to know that (a) if an object implements an
13971397:meth: `~object.__iadd__ ` magic method, it gets called when the ``+= `` augmented
13981398assignment
13991399is executed, and its return value is what gets used in the assignment statement;
1400- and (b) for lists, :meth: `!__iadd__ ` is equivalent to calling :meth: `~list. extend
1400+ and (b) for lists, :meth: `!__iadd__ ` is equivalent to calling :meth: `! extend
14011401and returning the list. That's why we say that for lists, ``+= `` is a
14021402"shorthand" for :meth: `!list.extend `::
14031403
@@ -1903,7 +1903,7 @@ identity tests. This prevents the code from being confused by objects such as
19031903``float('NaN') `` that are not equal to themselves.
19041904
19051905For example, here is the implementation of
1906- :meth: `collections.abc.Sequence.__contains__ `::
1906+ :meth: `! collections.abc.Sequence.__contains__
19071907
19081908 def __contains__(self, value):
19091909 for v in self:
0 commit comments