Move ARM/versioning.md to Versioning/06-evolving-apis.md and update all references

Agent-Logs-Url: https://github.com/Azure/typespec-azure/sessions/5ae43f24-5a9b-4ac4-9c08-9ef4240f81c4

Co-authored-by: markcowl <1054056+markcowl@users.noreply.github.com>

Author: Copilot

website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md

@@ -5,7 +5,7 @@ llmstxt: true
 
 See [`@typespec/versioning` documentation](https://typespec.io/docs/libraries/versioning/guide) for the general versioning concept. This guide expands on how Azure Services should define and manage API versions.
 
-See [Common Versioning Scenarios](../ARM/versioning.md) for how to make specific kinds of common API changes in your specs.
+See [Evolving APIs using the Versioning Library](./06-evolving-apis.md) for how to make specific kinds of common API changes in your specs.
 
 ## How Versioning Works in TypeSpec
 

website/src/content/docs/docs/howtos/Versioning/04-preview-after-stable.md

@@ -3,7 +3,7 @@ title: Adding a Preview Version when the Last Version was Stable
 llmstxt: true
 ---
 
-When the latest api-version in your TypeSpec spec is a stable version, adding a new preview version is simply adding any new types and operations in the new preview and marking them with the appropriate versioning decoration, as described in [Common Versioning Scenarios](../ARM/versioning.md).
+When the latest api-version in your TypeSpec spec is a stable version, adding a new preview version is simply adding any new types and operations in the new preview and marking them with the appropriate versioning decoration, as described in [Evolving APIs using the Versioning Library](./06-evolving-apis.md).
 
 ## Making Changes to your TypeSpec spec
 

website/src/content/docs/docs/howtos/Versioning/05-stable-after-stable.md

@@ -3,7 +3,7 @@ title: Adding a Stable Version when the Last Version was Stable
 llmstxt: true
 ---
 
-When the latest api-version in your TypeSpec spec is a stable version, adding a new stable version is simply adding any new types and operations in the new stable and marking them with the appropriate versioning decoration, as described in [Common Versioning Scenarios](../ARM/versioning.md).
+When the latest api-version in your TypeSpec spec is a stable version, adding a new stable version is simply adding any new types and operations in the new stable and marking them with the appropriate versioning decoration, as described in [Evolving APIs using the Versioning Library](./06-evolving-apis.md).
 
 ## Making Changes to your TypeSpec spec
 

…ntent/docs/docs/howtos/ARM/versioning.md …cs/howtos/Versioning/06-evolving-apis.mdwebsite/src/content/docs/docs/howtos/ARM/versioning.md renamed to website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md website/src/content/docs/docs/howtos/ARM/versioning.md renamed to website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md

@@ -1,10 +1,10 @@
 ---
-title: Versioning
-description: Managing versioning for ARM services
+title: Evolving APIs using the Versioning Library
+description: How to add, remove, or modify resources, operations, and properties across API versions
 llmstxt: true
 ---
 
-This document explains how to manage versioning in TypeSpec projects, including how to add, remove, or modify resources, operations, and properties across API versions.
+This document explains how to evolve your API across versions in TypeSpec projects, including how to add, remove, or modify resources, operations, and properties using versioning decorators.
 
 ## Introduction
 

website/src/content/docs/docs/howtos/Versioning/uncommon-scenarios/02-perpetual-preview.md

@@ -80,7 +80,7 @@ For some Resource Providers, whenever a new stable version is released, a new pr
     newName: int32;
   ```
 
-- Add any new type changes to stable version (A + 1) and decorate appropriately, as shown in the [versioning guide](../../ARM/versioning.md). Note that these changes should also appear in the new preview (A + 2)
+- Add any new type changes to stable version (A + 1) and decorate appropriately, as shown in the [versioning guide](../06-evolving-apis.md). Note that these changes should also appear in the new preview (A + 2)
 - Remove version `A` from the versions enumeration
 
   ```diff lang=tsp
@@ -213,7 +213,7 @@ For some Resource Providers, whenever a new stable version is released, a new pr
 
 - Do the following with the Original
   - Follow the instructions for normalizing decoration in the [converting specifications](./01-converting-specs.md#normalizing-version-decoration-optional) document. This will remove any redundant decoration between the new stable and preview versions (`A + 1` and `A + 2`).
-  - Add any type changes that are introduced in the new preview and decorate appropriately, following the [versioning guide](../../ARM/versioning.md)
+  - Add any type changes that are introduced in the new preview and decorate appropriately, following the [versioning guide](../06-evolving-apis.md)
   - Add a new example folder for the new preview version and populate with appropriate examples.
   - Compile the spec to produce artifacts (especially the new stable and preview version (`A + 1` and `A + 2`) APIs).
   - Copy the README.md from copy 1 and add the new preview version to the file.