From d073e5cde9dd02fba54b26565871fb1baad5bb59 Mon Sep 17 00:00:00 2001 From: vaitkus Date: Tue, 19 Sep 2023 10:58:59 +0300 Subject: [PATCH 1/2] Change "overkill" to "an overkill". --- semver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/semver.md b/semver.md index 22c9573..9bf17ce 100644 --- a/semver.md +++ b/semver.md @@ -322,7 +322,7 @@ that users can smoothly transition to the new API. ### Does SemVer have a size limit on the version string? -No, but use good judgment. A 255 character version string is probably overkill, +No, but use good judgment. A 255 character version string is probably an overkill, for example. Also, specific systems may impose their own limits on the size of the string. From ee4f1d2657fa0e75a28f28f3d5aa24d7d58a0d45 Mon Sep 17 00:00:00 2001 From: vaitkus Date: Tue, 19 Sep 2023 11:01:34 +0300 Subject: [PATCH 2/2] Change capitalisation of some words to match usage elsewhere in the text. --- semver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/semver.md b/semver.md index 9bf17ce..cf2c838 100644 --- a/semver.md +++ b/semver.md @@ -112,11 +112,11 @@ have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1. Precedence refers to how versions are compared to each other when ordered. 1. Precedence MUST be calculated by separating the version into major, - minor, patch and pre-release identifiers in that order (Build metadata + minor, patch and pre-release identifiers in that order (build metadata does not figure into precedence). 1. Precedence is determined by the first difference when comparing each of - these identifiers from left to right as follows: Major, minor, and patch + these identifiers from left to right as follows: major, minor, and patch versions are always compared numerically. Example: 1.0.0 < 2.0.0 < 2.1.0 < 2.1.1.