summaryrefslogtreecommitdiffstats
path: root/Doc/distutils
diff options
context:
space:
mode:
authorAndrés Delfino <adelfino@gmail.com>2018-06-18 04:34:30 (GMT)
committerINADA Naoki <methane@users.noreply.github.com>2018-06-18 04:34:30 (GMT)
commit5092439c2cb32112a5869b138011d38491db90a9 (patch)
treee3e51df527dff887f1bf15d00d0286b655b2634e /Doc/distutils
parent9d49f85064c388e2dddb9f8cb4ae1f486bc8d357 (diff)
downloadcpython-5092439c2cb32112a5869b138011d38491db90a9.zip
cpython-5092439c2cb32112a5869b138011d38491db90a9.tar.gz
cpython-5092439c2cb32112a5869b138011d38491db90a9.tar.bz2
bpo-33892: Doc: Use gender neutral words (GH-7770)
Diffstat (limited to 'Doc/distutils')
-rw-r--r--Doc/distutils/builtdist.rst2
-rw-r--r--Doc/distutils/introduction.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/distutils/builtdist.rst b/Doc/distutils/builtdist.rst
index f523a67..758bd14 100644
--- a/Doc/distutils/builtdist.rst
+++ b/Doc/distutils/builtdist.rst
@@ -21,7 +21,7 @@ specialty---writing code and creating source distributions---while an
intermediary species called *packagers* springs up to turn source distributions
into built distributions for as many platforms as there are packagers.
-Of course, the module developer could be his own packager; or the packager could
+Of course, the module developer could be their own packager; or the packager could
be a volunteer "out there" somewhere who has access to a platform which the
original developer does not; or it could be software periodically grabbing new
source distributions and turning them into built distributions for as many
diff --git a/Doc/distutils/introduction.rst b/Doc/distutils/introduction.rst
index a385559..7721484 100644
--- a/Doc/distutils/introduction.rst
+++ b/Doc/distutils/introduction.rst
@@ -94,7 +94,7 @@ containing your setup script :file:`setup.py`, and your module :file:`foo.py`.
The archive file will be named :file:`foo-1.0.tar.gz` (or :file:`.zip`), and
will unpack into a directory :file:`foo-1.0`.
-If an end-user wishes to install your :mod:`foo` module, all she has to do is
+If an end-user wishes to install your :mod:`foo` module, all they have to do is
download :file:`foo-1.0.tar.gz` (or :file:`.zip`), unpack it, and---from the
:file:`foo-1.0` directory---run ::