summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDiego Ramirez <dr01191115@gmail.com>2021-09-14 10:25:25 -0500
committerGitHub <noreply@github.com>2021-09-14 10:25:25 -0500
commit59ff034a066105826dc677ad27e617e8b56f2ef6 (patch)
tree3fa9906b264e5f1215c02e56b75c2a0e8db11748
parent125fb1d7c93433d1738829ba76580855347141d1 (diff)
downloadpython-setuptools-git-59ff034a066105826dc677ad27e617e8b56f2ef6.tar.gz
Update distribution.rst
Fix some typos.
-rw-r--r--docs/userguide/distribution.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/userguide/distribution.rst b/docs/userguide/distribution.rst
index 5888a819..19bed1f9 100644
--- a/docs/userguide/distribution.rst
+++ b/docs/userguide/distribution.rst
@@ -184,11 +184,11 @@ tag. Pre-release tags make a version be considered *older* than the version
they are appended to. So, revision ``2.4`` is *newer* than revision ``2.4c1``,
which in turn is newer than ``2.4b1`` or ``2.4a1``. Postrelease tags make
a version be considered *newer* than the version they are appended to. So,
-revisions like ``2.4-1`` is newer than ``2.4``, but *older*
+revisions like ``2.4-1`` are newer than ``2.4``, but *older*
than ``2.4.1`` (which has a higher release number).
-In the case of legacy versions (for example, ``2.4pl1``) are always considered
-older than non-legacy versions. Taking that in count, a version ``2.4pl1``
+In the case of legacy versions (for example, ``2.4pl1``), they are considered
+older than non-legacy versions. Taking that in count, a revision ``2.4pl1``
is *older* than ``2.4``
A pre-release tag is a series of letters that are alphabetically before