Merge pull request #249321 from roygara/fixingConcepts

Fixing concepts

Author: prmerger-automator[bot]

articles/storage/elastic-san/elastic-san-networking-concepts.md

@@ -40,7 +40,7 @@ After configuring endpoints, you can configure network rules to further control
 ## Private endpoints
 
 > [!IMPORTANT]
-> Private endpoints for Elastic SAN Preview are supported in all regions that Elastic SAN is available in if you deploy with [locally-redundant storage (LRS)](elastic-san-planning.md#redundancy) as their redundancy option. Private endpoints aren't currently supported Elastic SANs deployed using [zone-redundant storage (ZRS)](elastic-san-planning.md#redundancy) as their redundancy option.
+> For Elastic SANs using [locally-redundant storage (LRS)](elastic-san-planning.md#redundancy) as their redundancy option, private endpoints are supported in all regions that Elastic SAN is available. Private endpoints aren't currently supported for elastic SANs using [zone-redundant storage (ZRS)](elastic-san-planning.md#redundancy) as their redundancy option.
 
 Azure [Private Link](../../private-link/private-link-overview.md) enables you to access an Elastic SAN volume group securely over a [private endpoint](../../private-link/private-endpoint-overview.md) from a virtual network subnet. Traffic between your virtual network and the service traverses the Microsoft backbone network, eliminating the risk of exposing your service to the public internet. An Elastic SAN private endpoint uses a set of IP addresses from the subnet address space for each volume group. The maximum number used per endpoint is 20.