Merge pull request #802 from scop/spelling

Spelling fixes

Author: di

source/guides/installing-using-linux-tools.rst

@@ -98,7 +98,7 @@ To install pip, wheel, and setuptools, in a parallel, non-system environment
 (using yum) then there are two options:
 
 
-1. Use the "Sofware Collections" feature to enable a parallel collection that
+1. Use the "Software Collections" feature to enable a parallel collection that
    includes pip, setuptools, and wheel.
 
    * For Redhat, see here:

source/guides/installing-using-pip-and-virtual-environments.rst

@@ -7,7 +7,7 @@ for Python 2. These are the lowest-level tools for managing Python
 packages and are recommended if higher-level tools do not suit your needs.
 
 .. note:: This doc uses the term **package** to refer to a
-    :term:`Distribution Package`  which is different from a :term:`Import
+    :term:`Distribution Package`  which is different from an :term:`Import
     Package` that which is used to import modules in your Python source code.
 
 

source/guides/multi-version-installs.rst

@@ -32,7 +32,7 @@ This can be worked around by setting all dependencies in
 ``__main__.__requires__`` before importing ``pkg_resources`` for the first
 time, but that approach does mean that standard command line invocations of
 the affected tools can't be used - it's necessary to write a custom
-wrapper script or use ``python -c '<commmand>'`` to invoke the application's
+wrapper script or use ``python -c '<command>'`` to invoke the application's
 main entry point directly.
 
 Refer to the `pkg_resources documentation

source/guides/packaging-binary-extensions.rst

@@ -112,7 +112,7 @@ profiling has identified the code where the speed increase is worth
 additional maintenance effort), a number of other alternatives should
 also be considered:
 
-* look for existing optimised alternatives. The CPython standard libary
+* look for existing optimised alternatives. The CPython standard library
   includes a number of optimised data structures and algorithms (especially
   in the builtins and the ``collections`` and ``itertools`` modules). The
   Python Package Index also offers additional alternatives. Sometimes, the

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

@@ -38,7 +38,7 @@ Let's begin! 🚀
    tab of your target repository and then click on `Secrets`_
    in the left sidebar.
 3. Create a new secret called ``PYPI_API_TOKEN`` and copy-paste
-   the token from the fist step.
+   the token from the first step.
 4. Now, go to https://test.pypi.org/manage/account/#api-tokens
    and repeat the steps. Save that TestPyPI token on GitHub
    as ``TEST_PYPI_API_TOKEN``.

source/overview.rst

@@ -416,7 +416,7 @@ virtualenv
 
 `Virtualenvs
 <http://python-guide.readthedocs.io/en/latest/dev/virtualenvs/>`_ have
-been an indispensible tool for multiple generations of Python
+been an indispensable tool for multiple generations of Python
 developer, but are slowly fading from view, as they are being wrapped
 by higher-level tools. With packaging in particular, virtualenvs are
 used as a primitive in `the dh-virtualenv tool

source/specifications/declaring-project-metadata.rst

@@ -20,7 +20,7 @@ The fields defined in this specification MUST be in a table named
 table which are not defined by this specification. For tools wishing
 to store their own settings in ``pyproject.toml``, they may use the
 ``[tool]`` table as defined in the
-:ref:`build dependency decleration specification <declaring-build-dependencies>`.
+:ref:`build dependency declaration specification <declaring-build-dependencies>`.
 The lack of a ``[project]`` table implicitly means the build back-end
 will dynamically provide all fields.
 

source/specifications/recording-installed-packages.rst

@@ -21,7 +21,7 @@ History and change workflow
 ===========================
 
 The metadata described here was first specified in :pep:`376`, and later
-ammended in :pep:`627`.
+amended in :pep:`627`.
 It was formerly known as *Database of Installed Python Distributions*.
 Further amendments (except trivial language or typography fixes) must be made
 through the PEP process (see :pep:`1`).