summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRaphaël Barrois <raphael.barrois@polytechnique.org>2019-08-23 20:01:31 +0200
committerRaphaël Barrois <raphael.barrois@polytechnique.org>2019-08-24 15:13:09 +0200
commit0b0f9d3f2f5ffa1afe9452ec55d394d4bb1ba190 (patch)
tree63b450979b4f9dfbd340151b21b6f3d26f6f2661
parentc24f4e2157438be40b44e6ba02d90c6bfa934454 (diff)
downloadsemantic-version-0b0f9d3f2f5ffa1afe9452ec55d394d4bb1ba190.tar.gz
Fix minor docs typo.
-rw-r--r--docs/reference.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/reference.rst b/docs/reference.rst
index a7fce0b..8caa30b 100644
--- a/docs/reference.rst
+++ b/docs/reference.rst
@@ -325,7 +325,7 @@ does not map well onto `SemVer`_ precedence rules:
* A specification of ``<1.3.4`` is not expected to allow ``1.3.4-rc2``, but strict `SemVer`_ comparisons allow it ;
prereleases has the issue of excluding ``1.3.3+build3`` ;
* It may be necessary to exclude either all variations on a patch-level release
- (``!=1.3.3``) or specifically one build-level release (``1.3.3-build.434``).
+ (``!=1.3.3``) or specifically one build-level release (``1.3.3+build.434``).
In order to have version specification behave naturally, the rules are the following:
@@ -374,7 +374,7 @@ rules apply:
* Setting a build metadata separator without build metadata (``<=1.1.1+``)
forces matches "up to the build metadata"; use this to include/exclude a
release lacking build metadata while excluding/including all other builds
- of that release
+ of that release::
>>> Version('1.1.1') in Spec('==1.1.1+')
True