From: Xtreak Date: Thu, 16 May 2019 04:34:24 +0000 (+0530) Subject: Fix typos in documentation (#13344) X-Git-Tag: v3.8.0b1~351 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9b5a0efcdc5b6d23b6e05bb3d30263983b7da308;p=thirdparty%2FPython%2Fcpython.git Fix typos in documentation (#13344) --- diff --git a/Doc/faq/programming.rst b/Doc/faq/programming.rst index f14e8cc824ef..9660a701427f 100644 --- a/Doc/faq/programming.rst +++ b/Doc/faq/programming.rst @@ -792,7 +792,7 @@ Its documentation looks like this:: invoked using the three argument form. The slash at the end of the parameter list means that all three parameters are -positional-only. Thus, calling :func:`pow` with keyword aguments would lead to +positional-only. Thus, calling :func:`pow` with keyword arguments would lead to an error:: >>> pow(x=3, y=4) diff --git a/Doc/library/pickle.rst b/Doc/library/pickle.rst index 55005f009431..27721e698826 100644 --- a/Doc/library/pickle.rst +++ b/Doc/library/pickle.rst @@ -642,7 +642,7 @@ or both. by other classes as long as they implement :meth:`__setitem__`. * Optionally, a callable with a ``(obj, state)`` signature. This - callable allows the user to programatically control the state-updating + callable allows the user to programmatically control the state-updating behavior of a specific object, instead of using ``obj``'s static :meth:`__setstate__` method. If not ``None``, this callable will have priority over ``obj``'s :meth:`__setstate__`.