@@ -1413,18 +1413,18 @@ format. Each of the three numbers has a specific meaning:
14131413 compatible with other v1.x releases.
14141414
14151415 * Minor: The minor number is the second integer in the version
1416- string (e.g., v2.5.3). Changes in the minor number indicate a
1417- user-observable change in the code base and/or end-user
1418- functionality. Backwards compatibility will still be preserved
1419- with prior releases that have the same major version number (e.g.,
1420- v2.5.3 is backwards compatible with v2.3.1).
1416+ string. Changes in the minor number indicate a user-observable
1417+ change in the code base and/or end-user functionality. Backwards
1418+ compatibility will still be preserved with prior releases that
1419+ have the same major version number (e.g., v2.5.3 is backwards
1420+ compatible with v2.3.1).
14211421
14221422 * Release: The release number is the third integer in the version
1423- string (e.g., v4.3.0). Changes in the release number typically
1424- indicate a bug fix in the code base and/or end-user functionality.
1425- For example, if there is a release that only contains bug fixes
1426- and no other user-observable changes or new features, only the
1427- third integer will be increased (e.g., from v4.3.0 to v4.3.1).
1423+ string. Changes in the release number typically indicate a bug
1424+ fix in the code base and/or end-user functionality. For example,
1425+ if there is a release that only contains bug fixes and no other
1426+ user-observable changes or new features, only the third integer
1427+ will be increased (e.g., from v4.3.0 to v4.3.1).
14281428
14291429 * Quantifier: Open MPI version numbers sometimes have an arbitrary
14301430 string affixed to the end of the version number. Common strings
0 commit comments