Fix build warnings

Author: pjw711

articles/operator-nexus/TOC.yml

@@ -17,7 +17,7 @@
         - name: Storage overview
           href: concepts-storage.md
         - name: Multiple storage appliances
-          href: concepts-multiple-storage-appliances.md
+          href: concepts-storage-multiple-appliances.md
         - name: Storage for Nexus Kubernetes
           href: concepts-storage-kubernetes.md
         - name: Storage for Nexus Virtual Machines

articles/operator-nexus/azure-operator-nexus-faq.md

@@ -40,7 +40,7 @@ Updates of Management bundle may cause interruptions to provisioning activities
 On the other hand, Runtime bundle upgrades deals with the components that require updates to the OS (Operating System) and/or workload supporting components. The update of the runtime bundle is entirely under the control of the customer and APIs can be used to perform these updates. You might observe some workload impacts during this upgrade.
 
 ### Is the storage appliance a must required device?
-For near-edge SKUs, Storage appliance is a part of the Hardware infrastructure that Operator needs to procure. You can optionally choose to deploy a second storage appliance in an Azure Operator Nexus instance. For more information, see [Multiple storage appliances](/concepts-storage-multiple-appliances.md).
+For near-edge SKUs, Storage appliance is a part of the Hardware infrastructure that Operator needs to procure. You can optionally choose to deploy a second storage appliance in an Azure Operator Nexus instance. For more information, see [Multiple storage appliances](./concepts-storage-multiple-appliances.md).
 
 ### Does Operator Nexus provide best practices or blueprints for deploying network functions on Operator Nexus?
 Yes, Operator Nexus comes with Nexus Ready program. With this program, Microsoft is working with industry leading Network Function partners to validate that their network functions to ensure they can run on Nexus platform. We validate these network functions on regular intervals to ensure that they stay compliant with newer versions of Nexus. Operators can now get consistent and scalable deployment of multi-vendor network functions with the Nexus Ready program.

articles/operator-nexus/concepts-storage-kubernetes.md

@@ -45,7 +45,7 @@ status:
   phase: Bound
 ```
 
-Some Azure Operator Nexus deployments may have two storage appliances installed. Persistent volume claims (PVCs) using the *nexus-volume* storage class can place the associated persistent volumes onto a specific storage appliance by using the *storageApplianceName* annotation. More information is available in [this document](/concepts-storage-multiple-appliances.md).
+Some Azure Operator Nexus deployments may have two storage appliances installed. Persistent volume claims (PVCs) using the *nexus-volume* storage class can place the associated persistent volumes onto a specific storage appliance by using the *storageApplianceName* annotation. More information is available in [this document](./concepts-storage-multiple-appliances.md).
 
 ### StorageClass: nexus-shared
 

articles/operator-nexus/concepts-storage-multiple-appliances.md

@@ -2,7 +2,7 @@
 title: Azure Operator Nexus multiple storage appliances
 description: Lean about Azure Operator Nexus support for multiple storage appliances.
 author: pjw711
-ms.author: speterwhiting
+ms.author: peterwhiting
 ms.service: azure-operator-nexus
 ms.topic: conceptual
 ms.date: 03/12/2025
@@ -26,12 +26,12 @@ Azure Operator Nexus only supports a second storage appliance for instances that
 - The instance hardware matches the 2.0.x or later bills of material (BOMs).
 - All Pure storage appliances have R4 controllers.
 
-The Azure Operator Nexus SKUs that support a second storage appliance are documented in the [supported SKUs documentation](/reference-operator-nexus-skus.md). The storage appliances don't have to have the same capacity configurations. All supported capacity configurations are listed in the [supported storage appliances](/reference-near-edge-storage.md) documentation.
+The Azure Operator Nexus SKUs that support a second storage appliance are documented in the [supported SKUs documentation](./reference-operator-nexus-skus.md). The storage appliances don't have to have the same capacity configurations. All supported capacity configurations are listed in the [supported storage appliances](./reference-near-edge-storage.md) documentation.
 
 ## Supported deployment models
 
 >[!IMPORTANT]
->Deployment of a Nexus instance with two storage appliances requires a manual step after [Network Fabric creation](/howto-configure-network-fabric.md#create-a-network-fabric) and before [Network Fabric provisioning](/howto-configure-network-fabric.md#provision-a-network-fabric). The network fabric requires manual enablement of the ports that connect to the second storage device. This step can only be performed by Microsoft support; users should [raise a support ticket to request assistance](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
+>Deployment of a Nexus instance with two storage appliances requires a manual step after [Network Fabric creation](./howto-configure-network-fabric.md#create-a-network-fabric) and before [Network Fabric provisioning](./howto-configure-network-fabric.md#provision-a-network-fabric). The network fabric requires manual enablement of the ports that connect to the second storage device. This step can only be performed by Microsoft support; users should [raise a support ticket to request assistance](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 
 Azure Operator Nexus only supports deploying a second storage appliance at initial Nexus instance install time. There's no support for adding a second storage appliance to an existing Nexus instance. Any existing instance that requires a second storage appliance must be reinstalled.
 
@@ -87,18 +87,18 @@ You can create the shared storage service on either storage appliance when the C
 
 If no storage appliance configuration is provided at CSN creation time, the shared storage service uses the first storage appliance. If the configuration is present but doesn't match a storage appliance then the CSN creation will fail.
 
-See [Prerequisites for deploying tenant workloads](/quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
+See [Prerequisites for deploying tenant workloads](./quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
 
 #### Nexus-shared limitations
 
 - Azure Operator Nexus doesn't support moving the shared storage service from one storage appliance to another. Attempts to change the storage appliance backing the shared storage service have no effect.
 
 ### Persistent storage for virtual machines
 
-Nexus VMs support persistent OS disks and data disks backed by the storage appliance. There's no support for placing these disks on the second storage appliance. All VM disks are placed on the storage appliance in rack slot 1. For more information, see [Azure Operator Nexus storage for virtual machines](/concepts-storage-virtual-machine.md).
+Nexus VMs support persistent OS disks and data disks backed by the storage appliance. There's no support for placing these disks on the second storage appliance. All VM disks are placed on the storage appliance in rack slot 1. For more information, see [Azure Operator Nexus storage for virtual machines](./concepts-storage-virtual-machine.md).
 
 ### Metrics, logs, and monitoring
 
-The second storage appliance appears as an independent resource in Azure, of type NetworkCloud/storageAppliance. A Nexus instance with two storage appliances have two Storage Appliance Azure Resources. These resources are functionally identical: they share an API definition; and all supported metrics, documented in [List of Metrics Collected in Azure Operator Nexus](/list-of-metrics-collected.md), function identically on both storage appliances.
+The second storage appliance appears as an independent resource in Azure, of type NetworkCloud/storageAppliance. A Nexus instance with two storage appliances have two Storage Appliance Azure Resources. These resources are functionally identical: they share an API definition; and all supported metrics, documented in [List of Metrics Collected in Azure Operator Nexus](./list-of-metrics-collected.md), function identically on both storage appliances.
 
-Nexus also makes [storage appliance logs available](/list-logs-available.md#storage-appliance). Audit and alert logs are streamed on a per-resource basis. System logs are delivered in a combined stream that includes logs from both storage appliances.
+Nexus also makes [storage appliance logs available](./list-logs-available.md#storage-appliance). Audit and alert logs are streamed on a per-resource basis. System logs are delivered in a combined stream that includes logs from both storage appliances.

articles/operator-nexus/concepts-storage.md

@@ -15,7 +15,7 @@ Azure Operator Nexus is built on basic constructs like compute servers, storage
 
 Each storage appliance contains multiple storage devices, which are aggregated to provide a single storage pool. This storage pool is then carved out into multiple volumes, which are presented to the compute servers as block storage devices. The compute servers can use these block storage devices as persistent storage for their workloads. Each Azure Operator Nexus cluster is provisioned with a single storage appliance that's shared across all the tenant workloads.
 
-Azure Operator Nexus supports a maximum of two storage appliances. Detailed information on multiple storage appliance support is available in [this document](/concepts-storage-multiple-appliances.md). The storage appliances in an Azure Operator Nexus instance are represented as Azure resources. Each storage appliance is represented by a single instance of the Storage Appliance (Operator Nexus) resource. Operators get access to view its attributes like any other Azure resource.
+Azure Operator Nexus supports a maximum of two storage appliances. Detailed information on multiple storage appliance support is available in [this document](./concepts-storage-multiple-appliances.md). The storage appliances in an Azure Operator Nexus instance are represented as Azure resources. Each storage appliance is represented by a single instance of the Storage Appliance (Operator Nexus) resource. Operators get access to view its attributes like any other Azure resource.
 
 ## Storage appliance status
 

articles/operator-nexus/howto-platform-prerequisites.md

@@ -535,7 +535,7 @@ Interface:    net1, via: LLDP, RID: 1, Time: 0 day, 20:28:36
 ## [Optional] Set up second storage array
 
 >[!NOTE]
-> This section is optional. You only need to execute it if you are deploying an Azure Operator Nexus instance with two storage appliances. For more information, including restrictions on supported hardware, see [Azure Operator Nexus multiple storage appliances](/concepts-storage-multiple-appliances.md).
+> This section is optional. You only need to execute it if you are deploying an Azure Operator Nexus instance with two storage appliances. For more information, including restrictions on supported hardware, see [Azure Operator Nexus multiple storage appliances](./concepts-storage-multiple-appliances.md).
 
 1. Operator needs to install the storage array hardware as specified by the BOM and rack elevation
    within the Aggregation Rack. The hardware must go in the second storage appliance rack slot in the aggregator rack.

articles/operator-nexus/troubleshoot-multiple-storage-appliances.md

@@ -17,15 +17,15 @@ This guide documents common issues encountered in Azure Operator Nexus environme
 
 There are several common misconfigurations that prevent the second storage appliance from deploying successfully. Symptoms include:
 
-- The [cluster creation](/howto-configure-cluster.md#create-a-cluster) step failing.
+- The [cluster creation](./howto-configure-cluster.md#create-a-cluster) step failing.
 - The cluster creation step succeeding, but only creating a single storage appliance resource.
 
 If you see these issues, perform these checks:
 
 - Confirm that you correctly configured the prerequisites for both storage appliances. The initial IP address configuration is different for each storage appliance. See [the platform prerequisites](./howto-platform-prerequisites.md) for the correct configuration.
 - Confirm that Network Fabric Controller and Network Fabric are successfully provisioned.
 - Confirm that you have opened a support ticket to enable Network Fabric support for the second storage appliance. Confirm the ticket has been closed.
-- Check that the Azure CLI command you ran included the configuration for the second storage appliance and specified an aggregator rack SKU that supports a second storage appliance. See [cluster creation with multiple storage appliances](/howto-configure-cluster.md#create-the-cluster-using-azure-cli---multiple-storage-appliances) for details.
+- Check that the Azure CLI command you ran included the configuration for the second storage appliance and specified an aggregator rack SKU that supports a second storage appliance. See [cluster creation with multiple storage appliances](./howto-configure-cluster.md#create-the-cluster-using-azure-cli---multiple-storage-appliances) for details.
 
 If any of the configurations was incorrect: