Skip to content

Commit 6faee4e

Browse files
committed
python#9911: doc copyedits.
1 parent af38dc5 commit 6faee4e

31 files changed

+38
-38
lines changed

Doc/c-api/arg.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Unless otherwise stated, buffers are not NUL-terminated.
6565
.. note::
6666
This format does not accept bytes-like objects. If you want to accept
6767
filesystem paths and convert them to C character strings, it is
68-
preferrable to use the ``O&`` format with :cfunc:`PyUnicode_FSConverter`
68+
preferable to use the ``O&`` format with :cfunc:`PyUnicode_FSConverter`
6969
as *converter*.
7070

7171
``s*`` (:class:`str`, :class:`bytes`, :class:`bytearray` or buffer compatible object) [Py_buffer]

Doc/c-api/unicode.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -385,7 +385,7 @@ To encode and decode file names and other environment strings,
385385
:cdata:`Py_FileSystemEncoding` should be used as the encoding, and
386386
``"surrogateescape"`` should be used as the error handler (:pep:`383`). To
387387
encode file names during argument parsing, the ``"O&"`` converter should be
388-
used, passsing :cfunc:`PyUnicode_FSConverter` as the conversion function:
388+
used, passing :cfunc:`PyUnicode_FSConverter` as the conversion function:
389389

390390
.. cfunction:: int PyUnicode_FSConverter(PyObject* obj, void* result)
391391

@@ -398,7 +398,7 @@ used, passsing :cfunc:`PyUnicode_FSConverter` as the conversion function:
398398

399399

400400
To decode file names during argument parsing, the ``"O&"`` converter should be
401-
used, passsing :cfunc:`PyUnicode_FSDecoder` as the conversion function:
401+
used, passing :cfunc:`PyUnicode_FSDecoder` as the conversion function:
402402

403403
.. cfunction:: int PyUnicode_FSDecoder(PyObject* obj, void* result)
404404

Doc/distutils/builtdist.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -357,7 +357,7 @@ would create a 64bit installation executable on your 32bit version of Windows.
357357

358358
To cross-compile, you must download the Python source code and cross-compile
359359
Python itself for the platform you are targetting - it is not possible from a
360-
binary installtion of Python (as the .lib etc file for other platforms are
360+
binary installation of Python (as the .lib etc file for other platforms are
361361
not included.) In practice, this means the user of a 32 bit operating
362362
system will need to use Visual Studio 2008 to open the
363363
:file:`PCBuild/PCbuild.sln` solution in the Python source tree and build the

Doc/extending/newtypes.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1249,7 +1249,7 @@ This function is called with two Python objects and the operator as arguments,
12491249
where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, ``Py_GT``,
12501250
``Py_LT`` or ``Py_GT``. It should compare the two objects with respect to the
12511251
specified operator and return ``Py_True`` or ``Py_False`` if the comparison is
1252-
successfull, ``Py_NotImplemented`` to indicate that comparison is not
1252+
successful, ``Py_NotImplemented`` to indicate that comparison is not
12531253
implemented and the other object's comparison method should be tried, or *NULL*
12541254
if an exception was set.
12551255

Doc/faq/design.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ coding-style conflicts. In C there are many different ways to place the braces.
2828
If you're used to reading and writing code that uses one style, you will feel at
2929
least slightly uneasy when reading (or being required to write) another style.
3030

31-
Many coding styles place begin/end brackets on a line by themself. This makes
31+
Many coding styles place begin/end brackets on a line by themselves. This makes
3232
programs considerably longer and wastes valuable screen space, making it harder
3333
to get a good overview of a program. Ideally, a function should fit on one
3434
screen (say, 20-30 lines). 20 lines of Python can do a lot more work than 20

Doc/faq/programming.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -953,7 +953,7 @@ Is there an equivalent to Perl's chomp() for removing trailing newlines from str
953953
-------------------------------------------------------------------------------------
954954

955955
Starting with Python 2.2, you can use ``S.rstrip("\r\n")`` to remove all
956-
occurences of any line terminator from the end of the string ``S`` without
956+
occurrences of any line terminator from the end of the string ``S`` without
957957
removing other trailing whitespace. If the string ``S`` represents more than
958958
one line, with several empty lines at the end, the line terminators for all the
959959
blank lines will be removed::

Doc/glossary.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Glossary
1919

2020
2to3
2121
A tool that tries to convert Python 2.x code to Python 3.x code by
22-
handling most of the incompatibilites which can be detected by parsing the
22+
handling most of the incompatibilities which can be detected by parsing the
2323
source and traversing the parse tree.
2424

2525
2to3 is available in the standard library as :mod:`lib2to3`; a standalone

Doc/howto/descriptor.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -296,7 +296,7 @@ Running the interpreter shows how the function descriptor works in practice::
296296
<bound method D.f of <__main__.D object at 0x00B18C90>>
297297

298298
The output suggests that bound and unbound methods are two different types.
299-
While they could have been implemented that way, the actual C implemention of
299+
While they could have been implemented that way, the actual C implementation of
300300
:ctype:`PyMethod_Type` in
301301
`Objects/classobject.c <http://svn.python.org/view/python/trunk/Objects/classobject.c?view=markup>`_
302302
is a single object with two different representations depending on whether the

Doc/howto/sockets.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -313,7 +313,7 @@ process is likely to be screwed up.
313313
Non-blocking Sockets
314314
====================
315315

316-
If you've understood the preceeding, you already know most of what you need to
316+
If you've understood the preceding, you already know most of what you need to
317317
know about the mechanics of using sockets. You'll still use the same calls, in
318318
much the same ways. It's just that, if you do it right, your app will be almost
319319
inside-out.

Doc/library/2to3.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ process.
8989
Since some print statements can be parsed as function calls or statements, 2to3
9090
cannot always read files containing the print function. When 2to3 detects the
9191
presence of the ``from __future__ import print_function`` compiler directive, it
92-
modifies its internal grammar to interpert :func:`print` as a function. This
92+
modifies its internal grammar to interpret :func:`print` as a function. This
9393
change can also be enabled manually with the :option:`-p` flag. Use
9494
:option:`-p` to run fixers on code that already has had its print statements
9595
converted.

0 commit comments

Comments
 (0)