Merge pull request #1275 from DimitriPapadopoulos/codespell

Author: webknjaz

source/contribute.rst

@@ -63,7 +63,7 @@ document <discussions/install-requires-vs-requirements>`.
 Specifications
 --------------
 
-Specifications are reference documention focused on comprehensively documenting
+Specifications are reference documentation focused on comprehensively documenting
 an agreed-upon interface for interoperability between packaging tools.
 :doc:`example specification-style document <specifications/core-metadata>`.
 

source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

@@ -103,8 +103,8 @@ use ``build`` package.
    You can use any other method for building distributions as long as
    it produces ready-to-upload artifacts saved into the
    ``dist/`` folder. You can even use ``actions/upload-artifact`` and
-   ``actions/download-artifact`` to tranfer files between jobs or make them
-   accessable for download from the web CI interface.
+   ``actions/download-artifact`` to transfer files between jobs or make them
+   accessible for download from the web CI interface.
 
 So add this to the steps list:
 

source/key_projects.rst

@@ -184,7 +184,7 @@ check for CVEs in `Pipfile` using `safety <https://pyup.io/safety>`_.
 
 Pipenv aims to help users manage environments, dependencies, and
 imported packages on the command line. It also works well on Windows
-(which other tools often underserve), makes and checkes file hashes,
+(which other tools often underserve), makes and checks file hashes,
 to ensure compliance with hash-locked dependency specifiers, and eases
 uninstallation of packages and dependencies.
 

source/news.rst

@@ -118,7 +118,7 @@ March 2018
 - Updated "installing scientific packages". (:pr:`455`)
 - Added :file:`long_description_content_type` to follow PEP 556. (:pr:`457`)
 - Clarified a long description classifier on pypi.org. (:pr:`456`)
-- Updated Core Metadata spec to follw PEP 556. (:pr:`412`)
+- Updated Core Metadata spec to follow PEP 556. (:pr:`412`)
 
 February 2018
 -------------
@@ -214,7 +214,7 @@ April 2017
 - Added documentation explaining prominently how to install ``pip`` in ``/usr/local``. (:pr:`230`)
 - Updated development mode documentation to mention that order of local packages matters. (:pr:`208`)
 - Convert readthedocs link for their ``.org`` -> ``.io`` migration for hosted projects (:pr:`239`)
-- Swaped order of :file:`setup.py` arguments for the upload command, as order
+- Swapped order of :file:`setup.py` arguments for the upload command, as order
   is significant. (:pr:`260`)
 - Explained how to install from unsupported sources using a helper application. (:pr:`289`)
 

source/specifications/recording-installed-packages.rst

@@ -59,14 +59,14 @@ encouraged to start normalizing those fields.
 
 .. note::
 
-    The ``.dist-info`` directory's name is formatted to unambigiously represent
+    The ``.dist-info`` directory's name is formatted to unambiguously represent
     a distribution as a filesystem path. Tools presenting a distribution name
     to a user should avoid using the normalized name, and instead present the
     specified name (when needed prior to resolution to an installed package),
     or read the respective fields in Core Metadata, since values listed there
     are unescaped and accurately reflect the distribution. Libraries should
     provide API for such tools to consume, so tools can have access to the
-    unnormalized name when displaying distrubution information.
+    unnormalized name when displaying distribution information.
 
 This ``.dist-info`` directory may contain the following files, described in
 detail below:
@@ -234,7 +234,7 @@ packages into a Python environment to ensure that other tools are not used to
 uninstall or otherwise modify that installed package, as doing so may cause
 compatibility problems with the wider environment.
 
-To achieve this, affected tools should take the folllowing steps:
+To achieve this, affected tools should take the following steps:
 
 * Rename or remove the ``RECORD`` file to prevent changes via other tools (e.g.
   appending a suffix to create a non-standard ``RECORD.tool`` file if the tool
@@ -251,4 +251,4 @@ ensuring both locations appear on the default Python import path).
 
 In some circumstances, it may be desirable to block even installation of
 additional packages via Python-specific tools. For these cases refer to
-:ref:`externally-managed-environments`
+:ref:`externally-managed-environments`

source/specifications/virtual-environments.rst

@@ -19,7 +19,7 @@ Runtime detection of virtual environments
 
 At runtime, virtual environments can be identified by virtue of ``sys.prefix``
 (the filesystem location of the running interpreter) having a different value
-from ``sys.base_prefix`` (the default filesytem location of the standard library
+from ``sys.base_prefix`` (the default filesystem location of the standard library
 directories).
 
 :ref:`venv-explanation` in the Python standard library documentation for the