Minor clarification

Author: SPMcentral

docs/development/versioning.md

@@ -6,9 +6,9 @@ Other toolboxes that depend on SPM use this information to check whether a compa
 ## Transition to calendar versioning
 SPM is moving towards [calendar versioning](https://calver.org/). 
 
-The new format is **YY.0M[.MICRO]**, where YY is the short year (e.g. 24 for the year 2024), 0M is the zero padded month (e.g. 06 for June or 12 for December) and .MICRO is an optional integer for patches.
+The proposed new format is **YY.0M[.MICRO]**, where YY is the short year (e.g. 24 for the year 2024), 0M is the zero padded month (e.g. 06 for June or 12 for December) and .MICRO is an optional integer for patches.
 
-For backward compatibility, the version and release will operate as follows:
+For backward compatibility, the proposal is to set the version and release as follows:
 
 -	**Version**: SPMYY, where YY is the year of the most recent release, e.g. SPM24 
 -	**Release**: either 00.00 for the development version on Github or for a release: YY.0M[.MICRO], e.g. 24.07 for July 2024