aboutsummaryrefslogtreecommitdiff
path: root/doc/manual.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2019-11-12 09:44:10 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2019-11-12 09:44:10 +0200
commit02a9dc14e805b2d305248c090ff4c9894bbb4cb3 (patch)
treef1ac9e70f226836d40fc72a18055f912aded4753 /doc/manual.cli
parent22ff13f5ef5b1a57794a88f8a89d62b97d708ef7 (diff)
Minor manual tweak
Diffstat (limited to 'doc/manual.cli')
-rw-r--r--doc/manual.cli8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index b04ad55..65e96c4 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -58,10 +58,10 @@ If the package is a library then it is strongly recommended that you start its
package name with the \c{lib} prefix, for example, \c{libfoo}. Some package
repositories may make this a requirement as part of their submission policy.
-If a package (normally a library) supports usage of multiple major versions
-in the same project, then it is recommended to append the major version
-number to the package name starting from version \c{2.0.0}, for example,
-\c{libfoo} (before \c{2.0.0}), \c{libfoo2}, \c{libfoo3} (\c{3.Y.Z}), etc.
+If a package (normally a library) supports usage of multiple major versions in
+the same project, then it is recommended to append the major version number to
+the package name starting from version \c{2.0.0}, for example, \c{libfoo}
+(before \c{2.0.0}), \c{libfoo2} (\c{2.Y.Z}), \c{libfoo3} (\c{3.Y.Z}), etc.
\h1#package-version|Package Version|