Documentation: Update versioning.md

Author: SPMcentral

docs/development/versioning.md

@@ -1,17 +1,15 @@
 # SPM version numbers
-SPM has a **version** and a **release**. At the time of writing, the version is **SPM12** and the release is **dev**. 
+SPM has a **version** and a **release**. For example, the version may be **SPM25** and the release may be **25.01**. 
 
 Other toolboxes that depend on SPM use this information to check whether a compatible SPM version is installed. A common pattern is to split the version string into two parts, e.g. SPM12 becomes **SPM** and **12**, and then the latter part is compared to the desired version number.
 
-## Transition to calendar versioning
-SPM is moving towards [calendar versioning](https://calver.org/). 
+## Calendar versioning
+With the introduction of SPM25, SPM moved to [calendar versioning](https://calver.org/). The format is **YY.0M[.MICRO]**, where YY is the short year (e.g. 25 for the year 2025), 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 are set 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
+-	**Version**: SPMYY, where YY is the year of the most recent release, e.g. SPM25
+-	**Release**: either 00.00 for the development version on Github or for a release: YY.0M[.MICRO], e.g. 25.07 for July 2025
 
 ## Where the SPM version number is stored
 The SPM version is stored on the second line of the file Contents.m in the root directory, or Contents.txt when SPM is in deployed mode (i.e., compiled).