Skip to content

Commit 0977d84

Browse files
authored
Update README.rst
Minor editorial updates
1 parent 6955566 commit 0977d84

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
univers: mostly universal version and version ranges comparison and conversion
1+
univers: mostly universal version and version range comparison and conversion
22
===============================================================================
33

44
|Build Status| |License| |Python 3.6+|
@@ -62,16 +62,16 @@ For each scheme, **univers** provides an implementation for:
6262
- converting a range back to its scheme-native range syntax and to the
6363
``vers`` syntax.
6464

65-
**univers** implements ``vers``, an experimental unified and mostly universal
65+
**univers** implements VERS, an experimental unified and mostly universal
6666
version range syntax. It can parse and convert an existing native version range
67-
strings to this unified syntax. For example, this means:
67+
string to this unified syntax. For example, this means:
6868

6969
- converting ">=1.2.3" as used in a Python package into ``vers:pypi/>=1.2.3``,
7070

7171
- or converting "^1.0.2" as used in an npm package dependency declaration into
7272
``vers:npm/>=1.0.2|<2.0.0``
7373

74-
The supported package ecosystems versioning schemes and underlying libraries
74+
The supported package ecosystem versioning schemes and underlying libraries
7575
include:
7676

7777
- npm that use the "node-semver" ranges notation and the semver versions syntax
@@ -124,7 +124,7 @@ Alternative
124124
Rather than using ecosystem-specific version schemes and code, another approach
125125
is to use a single procedure for all the versions as implemented in `libversion
126126
<https://github.com/repology/libversion>`_. ``libversion`` works in the most
127-
common case but may not work correctly when a task that demand precise version
127+
common cases but may not work correctly when a task that demand precise version
128128
comparisons such as for dependency resolution and vulnerability lookup where
129129
a "good enough" comparison accuracy is not acceptable. ``libversion`` does not
130130
handle version range notations.

0 commit comments

Comments
 (0)