Skip to content

Commit a248d90

Browse files
Merge pull request #218751 from roygara/fixGrammer
Fixing grammar
2 parents 18e6712 + e535817 commit a248d90

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/storage/elastic-san/elastic-san-introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: An overview of Azure Elastic SAN (preview), a service that enables
44
author: roygara
55
ms.service: storage
66
ms.topic: overview
7-
ms.date: 10/12/2022
7+
ms.date: 11/17/2022
88
ms.author: rogarana
99
ms.subservice: elastic-san
1010
ms.custom: ignite-2022
@@ -28,7 +28,7 @@ Elastic SAN simplifies deploying and managing storage at scale through grouping
2828

2929
### Performance
3030

31-
With an Elastic SAN, it's possible to scale your performance up to millions of IOPS, with double-digit GB/s throughput, and have single-digit millisecond latency. The performance of a SAN is shared across all of its volumes, as long as the SAN's caps aren't exceeded and the volumes are large enough, each volume can scale up to 64,000 IOPs. Elastic SAN volumes connect to your clients using the [iSCSI](https://en.wikipedia.org/wiki/ISCSI) protocol, which allows them to bypass the IOPS limit of an Azure VM and offers high throughput limits.
31+
With an Elastic SAN, it's possible to scale your performance up to millions of IOPS, with double-digit GB/s throughput, and have single-digit millisecond latency. The performance of a SAN is shared across all of its volumes. As long as the SAN's caps aren't exceeded and the volumes are large enough, each volume can scale up to 64,000 IOPs. Elastic SAN volumes connect to your clients using the [iSCSI](https://en.wikipedia.org/wiki/ISCSI) protocol, which allows them to bypass the IOPS limit of an Azure VM and offers high throughput limits.
3232

3333
### Cost optimization and consolidation
3434

articles/storage/elastic-san/elastic-san-planning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Understand planning for an Azure Elastic SAN deployment. Learn abou
44
author: roygara
55
ms.service: storage
66
ms.topic: conceptual
7-
ms.date: 10/12/2022
7+
ms.date: 11/17/2022
88
ms.author: rogarana
99
ms.subservice: elastic-san
1010
ms.custom: ignite-2022
@@ -40,7 +40,7 @@ Using the same example of a 100 TiB SAN that has 250,000 IOPS and 4,000 MB/s. Sa
4040

4141
## Networking
4242

43-
In Preview, Elastic SAN supports public endpoint from selected virtual network, restricting access to specified virtual networks. You configure volume groups to allow network access only from specific vnet subnets. Once a volume group is configured to allow access from a subnet, this configuration is inherited by all volumes belonging to the volume group. You can then mount volumes from any clients in the subnet, with the [internet Small Computer Systems Interface](https://en.wikipedia.org/wiki/ISCSI) (iSCSI) protocol. Note that you need to first enable [service point for Azure Storage] (../../virtual-network/virtual-network-service-endpoints-overview.md) in your virtual network before setting up the network rule on volume group.
43+
In Preview, Elastic SAN supports public endpoint from selected virtual network, restricting access to specified virtual networks. You configure volume groups to allow network access only from specific vnet subnets. Once a volume group is configured to allow access from a subnet, this configuration is inherited by all volumes belonging to the volume group. You can then mount volumes from any clients in the subnet, with the [internet Small Computer Systems Interface](https://en.wikipedia.org/wiki/ISCSI) (iSCSI) protocol. You must enable [service endpoint for Azure Storage](../../virtual-network/virtual-network-service-endpoints-overview.md) in your virtual network before setting up the network rule on volume group.
4444

4545
## Redundancy
4646

0 commit comments

Comments
 (0)