Merge pull request #294916 from b-ahibbard/typo

minor fixes

Author: prmerger-automator[bot]

articles/azure-netapp-files/azure-netapp-files-configure-export-policy.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.author: anfdocs
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 07/28/2021
+ms.date: 01/28/2025
 ---
 # Configure export policy for NFS or dual-protocol volumes
 
@@ -17,7 +17,7 @@ You can create up to five export policy rules.
 Once created, you can modify details of the export policy rule. The modifiable fields are: 
 
 -	IP address (For example, x.x.x.x)
--	CIDR range (A subnet range; for example, 0.0.0.0/0)
+-	Classless Inter-Domain Routing (CIDR) range (A subnet range; for example, 0.0.0.0/0)
 -	IP address comma separated list (For example, x.x.x.x, y.y.y.y)
 - Access level 
 - [Export policy rule order](network-attached-storage-permissions.md#export-policy-rule-ordering)

articles/azure-netapp-files/azure-netapp-files-create-netapp-account.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/04/2021
+ms.date: 02/04/2025
 ms.author: anfdocs
 ---
 
@@ -19,7 +19,7 @@ You must register your subscription for using the NetApp Resource Provider. For
 
 ## Steps
 
-1. Sign in to the Azure portal.
+1. Log into the Azure portal.
 1. Access the Azure NetApp Files pane by using one of the following methods:
    * Search for **Azure NetApp Files** in the Azure portal search box.
    * Select **All services** in the navigation, and then filter to Azure NetApp Files.

articles/azure-netapp-files/azure-netapp-files-manage-snapshots.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/25/2021
+ms.date: 10/25/2024
 ms.author: anfdocs
 ---
 # Create an on-demand snapshot for a volume

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -73,7 +73,7 @@ The following requirements and considerations apply to large volumes. For perfor
 
 ## About 64-bit file IDs
 
-Whereas regular volume use 32-bit file IDs, large volumes employ 64-bit file IDs. File IDs are unique identifiers that allow Azure NetApp Files to keep track of files in the file system. 64-bit IDs are utilized to increase the number of files allowed in a single volume, enabling a large volume able to hold more files than a regular volume. 
+Whereas regular volumes use 32-bit file IDs, large volumes employ 64-bit file IDs. File IDs are unique identifiers that allow Azure NetApp Files to keep track of files in the file system. 64-bit IDs are utilized to increase the number of files allowed in a single volume, enabling a large volume able to hold more files than a regular volume. 
 
 ## Supported regions
 

articles/azure-netapp-files/manage-manual-qos-capacity-pool.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 06/14/2021
+ms.date: 01/14/2025
 ms.author: anfdocs
 ---
 # Manage a manual QoS capacity pool
@@ -40,7 +40,7 @@ You can change a capacity pool that currently uses the auto QoS type to use the
 
 ## Monitor the throughput of a manual QoS capacity pool  
 
-Metrics are available to help you monitor the read and write throughput of a volume.  See [Metrics for Azure NetApp Files](azure-netapp-files-metrics.md).  
+Metrics are available to help you monitor the read and write throughput of a volume. See [Metrics for Azure NetApp Files](azure-netapp-files-metrics.md).  
 
 ## Modify the allotted throughput of a manual QoS volume 
 

articles/azure-netapp-files/performance-linux-concurrency-session-slots.md

@@ -1,14 +1,14 @@
 ---
-title: Azure virtual machine stock-keeping units (SKUs) best practices for Azure NetApp Files | Microsoft Docs
+title: Azure virtual machine stock-keeping unit (SKUs) best practices for Azure NetApp Files | Microsoft Docs
 description: Describes Azure NetApp Files best practices about Azure virtual machine stocking-keeping units (SKUs), including differences within and between SKUs.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 07/02/2021
+ms.date: 10/02/2024
 ms.author: anfdocs
 ---
-# Azure virtual machine stock-keeping unit best practices for Azure NetApp Files
+# Azure virtual machine stock-keeping unit (SKU) best practices for Azure NetApp Files
 
 This article describes Azure NetApp Files best practices about Azure virtual machine stock-keeping units (SKUs), including differences within and between SKUs.  
 

articles/azure-netapp-files/performance-virtual-machine-sku.md

@@ -5,20 +5,20 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 05/19/2021
+ms.date: 01/19/2025
 ms.author: anfdocs
 ---
 #  Benefits of using Azure NetApp Files for SQL Server deployment
 
-Azure NetApp Files reduces SQL Server total cost of ownership (TCO) as compared to block storage solutions.  With block storage, virtual machines have imposed limits on I/O and bandwidth for disk operations. Only network bandwidth limits are applied against Azure NetApp Files, and on egress only at that.  In other words, no VM level I/O limits are applied to Azure NetApp Files. Without these I/O limits, SQL Server running on smaller virtual machines connected to Azure NetApp Files can perform as well as SQL Server running on much larger virtual machines. Sizing instances down as such reduces the compute cost to 25% of the former price tag.  *You can reduce compute costs with Azure NetApp Files.*  
+Azure NetApp Files reduces SQL Server total cost of ownership (TCO) as compared to block storage solutions. With block storage, virtual machines have imposed limits on I/O and bandwidth for disk operations. Only network bandwidth limits are applied against Azure NetApp Files, and on egress only at that. In other words, no VM level I/O limits are applied to Azure NetApp Files. Without these I/O limits, SQL Server running on smaller virtual machines connected to Azure NetApp Files can perform as well as SQL Server running on much larger virtual machines. Sizing instances down as such reduces the compute cost to 25% of the former price tag. *You can reduce compute costs with Azure NetApp Files.*  
 
-Compute costs, however, are small compared to SQL Server license costs.  Microsoft SQL Server [licensing](https://download.microsoft.com/download/B/C/0/BC0B2EA7-D99D-42FB-9439-2C56880CAFF4/SQL_Server_2017_Licensing_Datasheet.pdf) is tied to physical core count. As such, decreasing instance size introduces an even larger cost saving for software licensing. *You can reduce software license costs with Azure NetApp Files.*
+Compute costs, however, are small compared to SQL Server license costs. Microsoft SQL Server [licensing](https://download.microsoft.com/download/B/C/0/BC0B2EA7-D99D-42FB-9439-2C56880CAFF4/SQL_Server_2017_Licensing_Datasheet.pdf) is tied to physical core count. As such, decreasing instance size introduces an even larger cost saving for software licensing. *You can reduce software license costs with Azure NetApp Files.*
 
 This article shows a detailed cost analysis and performance benefits about using Azure NetApp Files for SQL Server deployment. Not only do smaller instances have sufficient CPU to do the database work only possible with block on larger instances, *in many cases, the smaller instances are even more performant than their larger, disk-based counterparts because of Azure NetApp Files.* 
 
 ## Detailed cost analysis 
 
-The two sets of graphics in this section show the TCO example.  The number and type of managed disks, the Azure NetApp Files service level, and the capacity for each scenario have been selected to achieve the best price-capacity-performance.  Each graphic is made up of grouped machines (D16 with Azure NetApp Files, compared to D64 with managed disk by example), and prices are broken down for each machine type.  
+The two sets of graphics in this section show the TCO example. The number and type of managed disks, the Azure NetApp Files service level, and the capacity for each scenario have been selected to achieve the best price-capacity-performance. Each graphic is made up of grouped machines (D16 with Azure NetApp Files, compared to D64 with managed disk by example), and prices are broken down for each machine type. 
 
 The first set of graphic shows the overall cost of the solution using a 1-TiB database size, comparing the D16s_v4 to the D64, the D8 to the D32, and the D4 to the D16. The projected IOPs for each configuration are indicated by a green or yellow line and corresponds to the right-hand side Y axis.
 
@@ -31,13 +31,13 @@ The second set of graphic shows the overall cost using a 50-TiB database. The co
 
 ## Performance, and lots of it  
 
-To deliver on the significant cost reduction assertion requires lots of performance - the largest instances in the general Azure inventory support 80,000 disk IOPS by example. A single Azure NetApp Files volume can achieve 80,000 database IOPS, and instances such as the D16 are able to consume the same. The D16, normally capable of 25,600 disk IOPS, is 25% the size of the D64.  The D64s_v4 is capable of 80,000 disk IOPS, and as such, presents an excellent upper level comparison point.
+To deliver on the significant cost reduction assertion requires lots of performance - the largest instances in the general Azure inventory support 80,000 disk IOPS by example. A single Azure NetApp Files volume can achieve 80,000 database IOPS, and instances such as the D16 are able to consume the same. The D16, normally capable of 25,600 disk IOPS, is 25% the size of the D64. The D64s_v4 is capable of 80,000 disk IOPS, and as such, presents an excellent upper level comparison point.
 
-The D16s_v4 can drive an Azure NetApp Files volume to 80,000 database IOPS. As proven by the SQL Storage Benchmark (SSB) benchmarking tool, the D16 instance achieved a workload 125% greater than that achievable to disk from the D64 instance.  See the [SSB testing tool](#ssb-testing-tool) section for details about the tool.
+The D16s_v4 can drive an Azure NetApp Files volume to 80,000 database IOPS. As proven by the SQL Storage Benchmark (SSB) benchmarking tool, the D16 instance achieved a workload 125% greater than that achievable to disk from the D64 instance. See the [SSB testing tool](#ssb-testing-tool) section for details about the tool.
 
-Using a 1-TiB working set size and an 80% read, 20% update SQL Server workload, performance capabilities of most the instances in the D instance class were measured; most, not all, as the D2 and D64 instances themselves were excluded from testing. The former was left out as it doesn't support accelerated networking, and the latter because it's the comparison point. See the following graph to understand the limits of D4s_v4, D8s_v4, D16s_v4, and D32s_v4, respectively.  Managed disk storage tests are not shown in the graph. Comparison values are drawn directly from the [Azure Virtual Machine limits table](/azure/virtual-machines/dv3-dsv3-series) for the D class instance type.
+Using a 1-TiB working set size and an 80% read, 20% update SQL Server workload, performance capabilities of most the instances in the D instance class were measured; most, not all, as the D2 and D64 instances themselves were excluded from testing. The former was left out as it doesn't support accelerated networking, and the latter because it's the comparison point. See the following graph to understand the limits of D4s_v4, D8s_v4, D16s_v4, and D32s_v4, respectively. Managed disk storage tests are not shown in the graph. Comparison values are drawn directly from the [Azure Virtual Machine limits table](/azure/virtual-machines/dv3-dsv3-series) for the D class instance type.
 
-With Azure NetApp Files, each of the instances in the D class can meet or exceed the disk performance capabilities of instances two times larger.  *You can reduce software license costs significantly with Azure NetApp Files.*  
+With Azure NetApp Files, each of the instances in the D class can meet or exceed the disk performance capabilities of instances two times larger. *You can reduce software license costs significantly with Azure NetApp Files.*  
 
 * The D4 at 75% CPU utilization matched the disk capabilities of the D16.  
     * The D16 is rate limited at 25,600 disk IOPS.  
@@ -54,7 +54,7 @@ The following diagram summarizes the S3B CPU limits test:
 
 ![Diagram that shows average CPU percentage for single-instance SQL Server over Azure NetApp Files.](./media/solutions-benefits-azure-netapp-files-sql-server/solution-sql-server-single-instance-average-cpu.png)
 
-Scalability is only part of the story. The other part is latency.  It’s one thing for smaller virtual machines to have the ability to drive much higher I/O rates, it’s another thing to do so with low single-digit latencies as shown below.  
+Scalability is only part of the story. The other part is latency. It’s one thing for smaller virtual machines to have the ability to drive much higher I/O rates, it’s another thing to do so with low single-digit latencies as shown below.  
 
 * The D4 drove 26,000 IOPS against Azure NetApp Files at 2.3-ms latency.  
 * The D8 drove 51,000 IOPS against Azure NetApp Files at 2.0-ms latency.  
@@ -69,13 +69,13 @@ The following diagram shows the latency for single-instance SQL Server over Azur
 
 ## SSB testing tool 
 
-The [TPC-E](http://www.tpc.org/tpce/) benchmarking tool, by design, stresses *compute* rather than *storage*. The test results shown in this section are based on a stress testing tool named SQL Storage Benchmark (SSB).  The SQL Server Storage Benchmark can drive massive-scale SQL execution against a SQL Server database to simulate an OLTP workload, similar to the [SLOB2 Oracle benchmarking tool](https://kevinclosson.net/slob/). 
+The [TPC-E](http://www.tpc.org/tpce/) benchmarking tool, by design, stresses *compute* rather than *storage*. The test results shown in this section are based on a stress testing tool named SQL Storage Benchmark (SSB). The SQL Server Storage Benchmark can drive massive-scale SQL execution against a SQL Server database to simulate an OLTP workload, similar to the [SLOB2 Oracle benchmarking tool](https://kevinclosson.net/slob/). 
 
-The SSB tool generates a SELECT and UPDATE driven workload issuing the said statements directly to the SQL Server database running within the Azure virtual machine.  For this project, the SSB workloads ramped from 1 to 100 SQL Server users, with 10 or 12 intermediate points at 15 minutes per user count.  All performance metrics from these runs were from the point of view of perfmon, for repeatability SSB ran three times per scenario. 
+The SSB tool generates a SELECT and UPDATE driven workload issuing the said statements directly to the SQL Server database running within the Azure virtual machine. For this project, the SSB workloads ramped from 1 to 100 SQL Server users, with 10 or 12 intermediate points at 15 minutes per user count. All performance metrics from these runs were from the point of view of perfmon, for repeatability SSB ran three times per scenario. 
 
-The tests themselves were configured as 80% SELECT and 20% UPDATE statement, thus 90% random read.  The database itself, which SSB created, was 1000 GB in size. It's comprised of 15 user tables and 9,000,000 rows per user table and 8192 bytes per row. 
+The tests themselves were configured as 80% SELECT and 20% UPDATE statement, thus 90% random read. The database itself, which SSB created, was 1000 GB in size. It's comprised of 15 user tables and 9,000,000 rows per user table and 8192 bytes per row. 
 
-The SSB benchmark is an open-source tool.  It's freely available at the SQL Storage Benchmark GitHub page.
+The SSB benchmark is an open-source tool. It's freely available at the SQL Storage Benchmark GitHub page.
 
 
 ## In summary