Use “minor version number”

In the instances example, use “minor version number” instead of
“patch-level”.

PVP mandates at least three components: two major ones (A, B),
and a minor one (C).  “Patch-level” is not defined in the PVP.

Using “minor version numer” in the example is consistent and
clearer.

Author: ffaf1

v1.0/pvp-specification.md

@@ -143,8 +143,8 @@ Now consider this scenario:
     version number bumped, as required by the PVP.
 2.  Package B, which can still work with the old and new version of
     package A, changes its dependency on package A to allow for both
-    versions. Package B only gets a patch-level bump.
-3.  Package C might or might not compile, depending on which patch-level
+    versions. Package B only gets a minor version number bump.
+3.  Package C might or might not compile, depending on which minor
     version of package B is used.
 
 The PVP could require that package B must bump its major version number

v1.1/pvp-specification.md

@@ -146,8 +146,8 @@ Now consider this scenario:
     version number bumped, as required by the PVP.
 2.  Package B, which can still work with the old and new version of
     package A, changes its dependency on package A to allow for both
-    versions. Package B only gets a patch-level bump.
-3.  Package C might or might not compile, depending on which patch-level
+    versions. Package B only gets a minor version number bump.
+3.  Package C might or might not compile, depending on which minor
     version of package B is used.
 
 The PVP could require that package B must bump its major version number