Fix image-name-incomplete: rename mhsm- prefix to managed-hsm-

Resolves build suggestions for disallowed abbreviation 'mhsm' in image
filenames. All 7 screenshot images renamed from mhsm-* to managed-hsm-*
and article references updated.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: msmbaldwin

articles/key-vault/managed-hsm/backup-restore.md

@@ -72,7 +72,7 @@ While the backup is in progress, the HSM might not operate at full throughput as
 
 1. Select **Start Backup**. Provide the storage account and container details, then initiate the backup.
 
-   :::image type="content" source="media/backup-restore/mhsm-backup-blade.png" alt-text="Screenshot of the Managed HSM Backup blade in the Azure portal.":::
+   :::image type="content" source="media/backup-restore/managed-hsm-backup-blade.png" alt-text="Screenshot of the Managed HSM Backup blade in the Azure portal.":::
 
 # [Azure CLI](#tab/azure-cli)
 

articles/key-vault/managed-hsm/key-management.md

@@ -53,7 +53,7 @@ You also need:
 
 1. Choose the key type (RSA-HSM, EC-HSM, or oct-HSM), set the key size or curve, name, and permitted operations, then select **Create**.
 
-   :::image type="content" source="media/key-management/mhsm-keys-blade.png" alt-text="Screenshot of the Keys blade in the Azure portal for a Managed HSM.":::
+   :::image type="content" source="media/key-management/managed-hsm-keys-blade.png" alt-text="Screenshot of the Keys blade in the Azure portal for a Managed HSM.":::
 
 # [Azure CLI](#tab/azure-cli)
 

…dia/backup-restore/mhsm-backup-blade.png …kup-restore/managed-hsm-backup-blade.pngarticles/key-vault/managed-hsm/media/backup-restore/mhsm-backup-blade.png renamed to articles/key-vault/managed-hsm/media/backup-restore/managed-hsm-backup-blade.png articles/key-vault/managed-hsm/media/backup-restore/mhsm-backup-blade.png renamed to articles/key-vault/managed-hsm/media/backup-restore/managed-hsm-backup-blade.png

@@ -105,7 +105,7 @@ In this diagram, the private endpoint is created in the UK South region only, th
 
 1. Select **Add Region**, choose the target region, and confirm.
 
-   :::image type="content" source="media/multi-region-replication/mhsm-multi-region-replication.png" alt-text="Screenshot of the Multi-Region Replication blade in the Azure portal showing the region map and Add Region option.":::
+   :::image type="content" source="media/multi-region-replication/managed-hsm-multi-region-replication.png" alt-text="Screenshot of the Multi-Region Replication blade in the Azure portal showing the region map and Add Region option.":::
 
 > [!IMPORTANT]
 > After initiating the extension to a new region, do not perform any operations on the primary HSM until the extension region pool is fully provisioned. Verify that the extended region's **Provisioning State** shows **Succeeded** before proceeding.