add convention to docs

Author: chargome

docs/contributing/platforms/versioning.mdx

@@ -11,15 +11,21 @@ Versioning allows for the maintenance of multiple versions of the same documenta
 To create a versioned page:
 
 1. Ensure the original page already exists.
-2. Create a new file with the same name as the original, but append `__v{VERSION}` to the filename (before the extension).
+2. Create a new file with the same name as the original, but append `__v{VERSION}` (two underscores) to the filename before the extension.
 
-For example, to create version 2.2.0 of `index.mdx`:
+**The version should follow one of these two formats:**
+- Major version only (for general version ranges): `__v{MAJOR}.x`
+- Full semantic version (for specific versions): `__v{MAJOR}.{MINOR}.{PATCH}`
+
+For example:
 
 ```
 index.mdx (original)
-index__v2.0.0.mdx (version 2.0.0)
+index__v7.x.mdx (version 7.x.x)
+index__v7.1.0.mdx (specific version 7.1.0)
 ```
 
+
 ## Versioning Platform Includes
 
 Pages in the `platform-includes` folder can be versioned using the same method. However, the root page referencing these includes must also be versioned.
@@ -30,11 +36,11 @@ Pages in the `platform-includes` folder can be versioned using the same method.
 docs/
 ├── getting-started/
 │   ├── index.mdx
-│   └── index__v2.mdx
+│   └── index__v7.x.mdx
 └── platform-includes/
     └── configuration/
         ├── example.mdx
-        └── example__v2.mdx
+        └── example__v7.x.mdx
 ```
 
 ## Version Selection and User Experience