links and redirect

Author: IngridAtMicrosoft

.openpublishing.redirection.media-services.json

@@ -679,7 +679,12 @@
             "source_path_from_root": "/articles/media-services/latest/transform-generate-thumbnails-rest-how-to.md",
             "redirect_url": "/azure/media-services/latest/transform-generate-thumbnails-how-to",
             "redirect_document_id": false
-          },   
+          },
+          {
+            "source_path_from_root": "/articles/media-services/latest/media-reserved-units-cli-how-to.md",
+            "redirect_url": "/azure/media-services/latest/media-reserved-units-how-to",
+            "redirect_document_id": false
+          },
         {
             "source_path_from_root": "/articles/media-services/latest/latest/asset-publish-cli-how-to.md",
             "redirect_url": "/azure/media-services/latest/video-on-demand-simple-portal-quickstart",

articles/media-services/latest/concept-media-reserved-units.md

@@ -32,4 +32,4 @@ For accounts created in with the **2020-05-01** version of the API (i.e. the v3
 ## See also
 
 * [Migrate from Media Services v2 to v3](migrate-v-2-v-3-migration-introduction.md)
-* [Scale Media Reserved Units with CLI](media-reserved-units-cli-how-to.md)
+* [Scale Media Reserved Units with CLI](media-reserved-units-how-to.md)

articles/media-services/latest/encode-concept.md

@@ -141,7 +141,7 @@ In Media Services v3, presets are strongly typed entities in the API itself. You
 
 ## Scaling encoding in v3
 
-To scale media processing, see [Scale with CLI](media-reserved-units-cli-how-to.md).
+To scale media processing, see [Scale with CLI](media-reserved-units-how-to.md).
 For accounts created with the **2020-05-01** or later version of the API or through the Azure portal, scaling and media reserved units are no longer required. Scaling will be automatic and handled by the service internally.
 
 ## Billing

articles/media-services/latest/migrate-v-2-v-3-migration-scenario-based-media-reserved-units.md

@@ -35,7 +35,7 @@ Please migrate your MRUs based on the following scenarios:
 * If you are an existing V2 customer, you need to create a new V3 account to support your existing application prior to the completion of  migration. 
 * Indexer V1 or other media processors that are not fully deprecated yet may need to be enabled again. 
 
-For more information about MRUs, see [Media Reserved Units](concept-media-reserved-units.md) and [How to scale media reserved units](media-reserved-units-cli-how-to.md).
+For more information about MRUs, see [Media Reserved Units](concept-media-reserved-units.md) and [How to scale media reserved units](media-reserved-units-how-to.md).
 
 ## MRU concepts, tutorials and how to guides
 
@@ -45,7 +45,7 @@ For more information about MRUs, see [Media Reserved Units](concept-media-reserv
 
 ### How to guides
 
-[How to scale media reserved units](media-reserved-units-cli-how-to.md)
+[How to scale media reserved units](media-reserved-units-how-to.md)
 
 ## Samples
 

articles/media-services/latest/release-notes.md

@@ -545,7 +545,7 @@ The CLI 2.0 module is now available for [Azure Media Services v3 GA](/cli/azure/
 - [az ams live-output](/cli/azure/ams/live-output)
 - [az ams streaming-endpoint](/cli/azure/ams/streaming-endpoint)
 - [az ams streaming-locator](/cli/azure/ams/streaming-locator)
-- [az ams account mru](/cli/azure/ams/account/mru) - enables you to manage Media Reserved Units. For more information, see [Scale Media Reserved Units](media-reserved-units-cli-how-to.md).
+- [az ams account mru](/cli/azure/ams/account/mru) - enables you to manage Media Reserved Units. For more information, see [Scale Media Reserved Units](media-reserved-units-how-to.md).
 
 ### New features and breaking changes