resolve warnings

Author: b-ahibbard

articles/azure-netapp-files/TOC.yml

@@ -315,7 +315,7 @@
           href: application-volume-group-add-volume-secondary.md
         - name: Add volumes for an SAP HANA system as a DR system
           href: application-volume-group-disaster-recovery.md
-        - name: Manage volumes in an application volume group for SAP NANA
+        - name: Manage volumes in an application volume group for SAP HANA
           href: application-volume-group-manage-volumes.md
         - name: Configure application volume groups for SAP HANA using REST API
           href: configure-application-volume-group-sap-hana-api.md
@@ -327,7 +327,7 @@
           href: application-volume-group-manage-volumes-oracle.md
         - name: Configure application volume group for Oracle using REST API
           href: configure-application-volume-oracle-api.md 
-        - name: Deploy application volume group for Oracle using ARM
+        - name: Deploy application volume group for Oracle using Azure Resource Manager
           href: configure-application-volume-oracle-azure-resource-manager.md 
       - name: Delete an application volume group
         href: application-volume-group-delete.md

articles/azure-netapp-files/application-volume-group-oracle-deploy-volumes.md

@@ -183,7 +183,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
     [ ![Screenshot that shows the Deployment in Progress window for Oracle.](./media/volume-hard-quota-guidelines/application-deployment-in-progress-oracle.png) ](./media/volume-hard-quota-guidelines/application-deployment-in-progress-oracle.png#lightbox)
 
-    Creating a volume group is an "all-or-none" operation. If one volume can't be created, the operation is cancelled, and all remaining volumes will be removed also.
+    Creating a volume group is an "all-or-none" operation. If one volume can't be created, the operation is canceled, and all remaining volumes will be removed also.
 
     [ ![Screenshot that shows the new volume group for Oracle.](./media/volume-hard-quota-guidelines/application-new-volume-group-oracle.png) ](./media/volume-hard-quota-guidelines/application-new-volume-group-oracle.png#lightbox)
 

articles/azure-netapp-files/configure-application-volume-oracle-api.md

@@ -88,7 +88,7 @@ In the following examples, selected placeholders are specified. You should repla
 * `<CapacityPoolResourceId>`:  
     Capacity pool resource ID. Example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/SH9_Pool `
 
-## Creating application volume groups for Oracle using curl
+## Create application volume groups for Oracle using curl
 
 Oracle volume groups for the following examples can be created using a sample shell script that calls the API using curl:
 

articles/azure-netapp-files/faq-application-volume-group.md

@@ -165,7 +165,7 @@ The deployment workflow ensures that all volumes are placed in the availability
 
 For optimal sizing, it's important to size for the complete database landscape including HA, snapshots, and backup. Decide your volume layout for production, HA and data protection, and perform your sizing according to [Run Your Most Demanding Oracle Workloads in Azure without Sacrificing Performance or Scalability](https://techcommunity.microsoft.com/t5/azure-architecture-blog/run-your-most-demanding-oracle-workloads-in-azure-without/ba-p/3264545) and [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183). You can also use the [SAP on Azure NetApp Files Sizing Estimator](https://aka.ms/anfsapcalc) by using the **Add Single Volume** input option.
 
-Important information you need to provide for sizing each of the volumes include the following items: SID, role (production, Dev, pre-prod/QA), snapshot reserve in percentage, number of days for local snapshot retention, number of file-based backups, single-host/multiple-host with the number of hosts, and Data Guard requirements (primary, secondary). Contact an Oracle on Azure NetApp Files sizing expert to help you plan the overall Oracle system sizing. 
+Important information you need to provide for sizing each of the volumes includes: SID, role (production, Dev, pre-prod/QA), snapshot reserve in percentage, number of days for local snapshot retention, number of file-based backups, single-host/multiple-host with the number of hosts, and Data Guard requirements (primary, secondary). Contact an Oracle on Azure NetApp Files sizing expert to help you plan the overall Oracle system sizing. 
 
 ### The mount instructions of a volume include a list of IP addresses. Which IP address should I use for Oracle?