Merge pull request #300680 from roygara/fixName

prmerger-automator[bot] · web-flow · commit 8155373e3f07 · 2025-06-02T21:47:55.000Z
Fixing service name
diff --git a/articles/storage/elastic-san/elastic-san-connect-aks.md b/articles/storage/elastic-san/elastic-san-connect-aks.md
@@ -10,7 +10,7 @@ ms.author: rogarana
 
 # Connect Azure Elastic SAN volumes to an Azure Kubernetes Service cluster
 
-This article explains how to connect an Azure Elastic storage area network (SAN) volume from an Azure Kubernetes Service (AKS) cluster. To make this connection, enable the [Kubernetes iSCSI CSI driver](https://github.com/kubernetes-csi/csi-driver-iscsi) on your cluster. With this driver, you can access volumes on your Elastic SAN by creating persistent volumes on your AKS cluster, and then attaching the Elastic SAN volumes to the persistent volumes. 
+This article explains how to connect an Azure Elastic SAN volume from an Azure Kubernetes Service (AKS) cluster. To make this connection, enable the [Kubernetes iSCSI CSI driver](https://github.com/kubernetes-csi/csi-driver-iscsi) on your cluster. With this driver, you can access volumes on your Elastic SAN by creating persistent volumes on your AKS cluster, and then attaching the Elastic SAN volumes to the persistent volumes. 
 
 ## About the driver
 
diff --git a/articles/storage/elastic-san/elastic-san-connect-linux.md b/articles/storage/elastic-san/elastic-san-connect-linux.md
@@ -11,7 +11,7 @@ ms.custom: references_regions, linux-related-content
 
 # Connect to Elastic SAN volumes - Linux
 
-This article explains how to connect to an Elastic storage area network (SAN) volume from an individual Linux client. For details on connecting from a Windows client, see [Connect to Elastic SAN volumes - Windows](elastic-san-connect-windows.md).
+This article explains how to connect to an Elastic SAN volume from an individual Linux client. For details on connecting from a Windows client, see [Connect to Elastic SAN volumes - Windows](elastic-san-connect-windows.md).
 
 In this article, you'll add the Storage service endpoint to an Azure virtual network's subnet, then you'll configure your volume group to allow connections from your subnet. Finally, you'll configure your client environment to connect to an Elastic SAN volume and establish a connection.
 
diff --git a/articles/storage/elastic-san/elastic-san-connect-windows.md b/articles/storage/elastic-san/elastic-san-connect-windows.md
@@ -11,7 +11,7 @@ ms.custom: references_regions
 
 # Connect to Elastic SAN volumes - Windows
 
-This article explains how to connect to an Elastic storage area network (SAN) volume from an individual Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN volumes - Linux](elastic-san-connect-linux.md).
+This article explains how to connect to an Elastic SAN volume from an individual Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN volumes - Linux](elastic-san-connect-linux.md).
 
 In this article, you add the Storage service endpoint to an Azure virtual network's subnet, then you configure your volume group to allow connections from your subnet. Finally, you configure your client environment to connect to an Elastic SAN volume and establish a connection. For best performance, ensure that your VM and your Elastic SAN are in the same zone.
 
diff --git a/articles/storage/elastic-san/elastic-san-create.md b/articles/storage/elastic-san/elastic-san-create.md
@@ -11,7 +11,7 @@ ms.custom: references_regions, devx-track-azurepowershell, devx-track-azurecli
 
 # Deploy an Elastic SAN
 
-This article explains how to deploy and configure an elastic storage area network (SAN).
+This article explains how to deploy and configure an Elastic SAN.
 
 ## Prerequisites
 
diff --git a/articles/storage/elastic-san/elastic-san-delete.md b/articles/storage/elastic-san/elastic-san-delete.md
@@ -11,7 +11,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
 
 # Delete an Elastic SAN
 
-Your Elastic storage area network (SAN) resources can be deleted at different resource levels. This article covers the overall deletion process, starting from disconnecting iSCSI connections to volumes, deleting the volumes themselves, deleting a volume group, and deleting an elastic SAN itself. Before you delete your elastic SAN, make sure it's not being used in any running workloads.
+Your Elastic SAN resources can be deleted at different resource levels. This article covers the overall deletion process, starting from disconnecting iSCSI connections to volumes, deleting the volumes themselves, deleting a volume group, and deleting an elastic SAN itself. Before you delete your elastic SAN, make sure it's not being used in any running workloads.
 
 ## Disconnect volumes from clients
 
diff --git a/articles/storage/elastic-san/elastic-san-expand.md b/articles/storage/elastic-san/elastic-san-expand.md
@@ -11,7 +11,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
 
 # Resize an Azure Elastic SAN
 
-This article covers increasing or decreasing the size of an Elastic storage area network (SAN) and an individual volume.
+This article covers increasing or decreasing the size of an Elastic SAN and an individual volume.
 
 ## Resize your SAN
 
diff --git a/articles/storage/elastic-san/elastic-san-networking-concepts.md b/articles/storage/elastic-san/elastic-san-networking-concepts.md
@@ -10,7 +10,7 @@ ms.author: rogarana
 
 # Learn about networking configurations for Elastic SAN
 
-Azure Elastic storage area network (SAN) allows you to secure and control the level of access to your Elastic SAN volumes that your applications and enterprise environments require. This article describes the options for allowing users and applications access to Elastic SAN volumes from an [Azure virtual network infrastructure](../../virtual-network/vnet-integration-for-azure-services.md).
+Azure Elastic SAN allows you to secure and control the level of access to your Elastic SAN volumes that your applications and enterprise environments require. This article describes the options for allowing users and applications access to Elastic SAN volumes from an [Azure virtual network infrastructure](../../virtual-network/vnet-integration-for-azure-services.md).
 
 You can configure Elastic SAN volume groups to only allow access over specific endpoints on specific virtual network subnets. The allowed subnets can belong to a virtual network in the same subscription, or those in a different subscription, including subscriptions belonging to a different Microsoft Entra tenant. Once network access is configured for a volume group, the configuration is inherited by all volumes belonging to the group.
 
diff --git a/articles/storage/elastic-san/elastic-san-networking.md b/articles/storage/elastic-san/elastic-san-networking.md
@@ -11,7 +11,7 @@ ms.custom: references_regions, devx-track-azurecli, devx-track-azurepowershell
 
 # Configure network access for Azure Elastic SAN
 
-You can control access to your Azure Elastic storage area network (SAN) volumes. Controlling access allows you to secure your data and meet the needs of your applications and enterprise environments.
+You can control access to your Elastic SAN volumes. Controlling access allows you to secure your data and meet the needs of your applications and enterprise environments.
 
 This article describes how to configure your Elastic SAN to allow access from your Azure virtual network infrastructure.
 
diff --git a/articles/storage/elastic-san/elastic-san-planning.md b/articles/storage/elastic-san/elastic-san-planning.md
@@ -12,7 +12,7 @@ ms.custom:
 
 # Plan for deploying an Elastic SAN
 
-There are three main aspects to an elastic storage area network (SAN): the SAN itself, volume groups, and volumes. When deploying a SAN, you make selections while configuring the SAN, including the redundancy of the entire SAN, and how much performance and storage the SAN has. Then you create volume groups that are used to manage volumes at scale. Any settings applied to a volume group are inherited by volumes inside that volume group. Finally, you partition the storage capacity that was allocated at the SAN-level into individual volumes.
+There are three main aspects to an Elastic SAN: the SAN itself, volume groups, and volumes. When deploying a SAN, you make selections while configuring the SAN, including the redundancy of the entire SAN, and how much performance and storage the SAN has. Then you create volume groups that are used to manage volumes at scale. Any settings applied to a volume group are inherited by volumes inside that volume group. Finally, you partition the storage capacity that was allocated at the SAN-level into individual volumes.
 
 Before deploying an Elastic SAN, consider the following:
 
diff --git a/articles/storage/elastic-san/elastic-san-scale-targets.md b/articles/storage/elastic-san/elastic-san-scale-targets.md
@@ -11,7 +11,7 @@ ms.custom: references_regions
 
 # Scale targets for Elastic SAN
 
-There are three main components to an elastic storage area network (SAN): the SAN itself, volume groups, and volumes.
+There are three main components to an Elastic SAN: the SAN itself, volume groups, and volumes.
 
 ## The Elastic SAN
 
