edit pass: four-azure-application-consistent-snapshot-articles

Author: ShawnJackson

articles/azure-netapp-files/azacsnap-cmd-ref-configure.md

@@ -115,15 +115,15 @@ Editing the configuration as described sets the `autoDisableEnableBackint` value
 
 # [Oracle](#tab/oracle)
 
-When you add an *Oracle database* to the configuration, the following values are required:
+When you add an Oracle database to the configuration, the following values are required:
 
 - `Oracle DB Server's Address`: The database server's host name or IP address.
 - `SID`: The database system ID.
 - `Oracle Connect String`: The string that `sqlplus` uses to connect to Oracle and enable or disable backup mode.
 
 # [IBM Db2](#tab/db2)
 
-When you add a *Db2 database* to the configuration, the following values are required:
+When you add a Db2 database to the configuration, the following values are required:
 
 - `Db2 Server's Address`: The database server's host name or IP address.
 
@@ -138,9 +138,9 @@ When you add a *Db2 database* to the configuration, the following values are req
 
 ---
 
-# [Azure Large Instance (bare metal)](#tab/azure-large-instance)
+# [Azure Large Instances (bare metal)](#tab/azure-large-instance)
 
-When you add HANA Large Instances storage to a database section, the following values are required:
+When you add Azure Large Instances storage to a database section, the following values are required:
 
 - `Storage User Name`: The user name for establishing the SSH connection to the storage.
 - `Storage IP Address`: The IP address of the storage system.
@@ -159,7 +159,7 @@ When you add HANA Large Instances storage to a database section, the following v
 
 # [Azure NetApp Files (with a virtual machine)](#tab/azure-netapp-files)
 
-When you add *Azure NetApp Files storage* to a database section, the following values are required:
+When you add Azure NetApp Files storage to a database section, the following values are required:
 
 - `Service Principal Authentication filename` (JSON field: `authFile`):
   - To use a system-managed identity, leave this field empty with no value, and then select the Enter key to go to the next field.

articles/azure-netapp-files/azacsnap-installation.md

@@ -55,13 +55,13 @@ Follow the guidelines to set up and run the snapshots and disaster-recovery comm
 
    ---
 
-1. Enable communication with the database.
+1. Enable communication with the database. For more information, see [Enable communication with the database](#enable-communication-with-the-database) later in this article.
 
    # [SAP HANA](#tab/sap-hana)
 
    Set up an appropriate SAP HANA user by following the instructions in the [Enable communication with the database](#enable-communication-with-the-database) section of this article.
 
-   After setup, you can test the connection from the command line by using the following examples. These examples are for non-SSL communication to SAP HANA.
+   After setup, you can test the connection from the command line by using the following examples. The following examples are for non-SSL communication to SAP HANA.
 
    HANA 1.0:
 
@@ -354,7 +354,7 @@ SSL communication also requires key-store and trust-store files. It's possible f
 
 #### Key-store files
 
-If you're using multiple SIDs with the same key material, it's easier to create links into the `securityPath` location as defined in the AzAcSnap configuration file. Ensure that these values exist for every SID that uses SSL.
+If you're using multiple system identifiers (SIDs) with the same key material, it's easier to create links into the `securityPath` location as defined in the AzAcSnap configuration file. Ensure that these values exist for every SID that uses SSL.
 
 - For `openssl`: `ln $HOME/.ssl/key.pem <securityPath>/<SID>_keystore`
 - For `commoncrypto`: `ln $SECUDIR/sapcli.pse <securityPath>/<SID>_keystore`
@@ -781,7 +781,7 @@ usermod -a -G db2iadm1 azacsnap
 
 ##### azacsnap user profile
 
-The `azacsnap` user needs to be able to run the `db2` command. By default, the `db2` command isn't in the `azacsnap` user's $PATH. 
+The `azacsnap` user needs to be able to run the `db2` command. By default, the `db2` command isn't in the `azacsnap` user's `$PATH` information.
 
 Add the following code to the user's `.bashrc` file. Use your own IBM Db2 installation value for `INSTHOME`.
 
@@ -951,8 +951,7 @@ END   : Test process complete for 'db2'
 
 ## Install the snapshot tools
 
-The downloadable self-installer makes the snapshot tools easy to set up and run with non-root user privileges (for example, `azacsnap`). The installer sets up the user and puts the snapshot tools
-into the users `$HOME/bin` subdirectory. The default is `/home/azacsnap/bin`.
+The downloadable self-installer makes the snapshot tools easy to set up and run with non-root user privileges (for example, `azacsnap`). The installer sets up the user and puts the snapshot tools into the user's `$HOME/bin` subdirectory. The default is `/home/azacsnap/bin`.
 
 The self-installer tries to determine the correct settings and paths for all the files based on the configuration of the user performing the installation (for example, root). If the previous setup steps to enable communication with storage and SAP HANA were run as root, the installation copies the private key and `hdbuserstore` to the backup user's location. A knowledgeable administrator can manually take the steps to enable communication with the storage back end and database after the installation.
 
@@ -1113,7 +1112,7 @@ As the root superuser, you can follow these steps for a manual installation:
     echo "export LD_LIBRARY_PATH=\"\$LD_LIBRARY_PATH:$NEW_LIB_PATH\"" >> /home/azacsnap/.profile
     ```
 
-1. Take the following actions, depending on storage back end:
+1. Take the following actions, depending on the storage back end:
 
     # [Azure NetApp Files (with VM)](#tab/azure-netapp-files)
 

articles/azure-netapp-files/azacsnap-introduction.md

@@ -129,7 +129,7 @@ The command options are as follows. The main bullets are commands, and the inden
   For more information, see the [delete command reference](azacsnap-cmd-ref-delete.md).
 - `-c restore` provides two methods to restore a snapshot to a volume.
   - `--restore snaptovol` creates a new volume based on the latest snapshot on the target volume.
-  - `-c restore --restore revertvolume` reverts the target volume to a prior state based on the most recent snapshot.
+  - `-c restore --restore revertvolume` reverts the target volume to a prior state, based on the most recent snapshot.
 
   For more information, see the [restore command reference](azacsnap-cmd-ref-restore.md).
 - `[--configfile <configfilename>]` is an optional command-line parameter to provide a different file name for the JSON configuration. It's useful for creating a separate configuration file per security ID (for example, `--configfile H80.json`).

articles/azure-netapp-files/azacsnap-preview.md

@@ -73,14 +73,14 @@ Here's the architecture at a high level:
    The configurator has a new option to define the mount point for the logical volume. After you put the database into backup mode and after the I/O cache is flushed (dependent on Linux kernel parameter `fs.xfs.xfssyncd_centisecs`), this parameter is passed to `xfs_freeze` to block the I/O.
 1. Install and configure `xfs_freeze` to be run as a non-privileged user:
 
-   1. Create an executable file called *$HOME/bin/xfs_freeze* with the following content:
+   1. Create an executable file called `$HOME/bin/xfs_freeze` with the following content:
 
       ```bash
       #!/bin/sh
       /usr/bin/sudo /usr/sbin/xfs_freeze $1 $2
       ```
 
-   1. Create a sudoers file called */etc/sudoers.d/azacsnap* to allow the azacsnap user to run `xfs_freeze` with the following content:
+   1. Create a sudoers file called `/etc/sudoers.d/azacsnap` to allow the `azacsnap` user to run `xfs_freeze` with the following content:
 
       ```bash
       #
@@ -93,7 +93,7 @@ Here's the architecture at a high level:
       AZACSNAP ALL=(ALL) NOPASSWD: /usr/sbin/xfs_freeze
       ```
 
-   1. Test that the azacsnap user can freeze and unfreeze I/O to the target mount point by running the following code as the azacsnap user.
+   1. Test that the `azacsnap` user can freeze and unfreeze I/O to the target mount point by running the following code as the `azacsnap` user.
 
       This example runs each command twice to show that it worked the first time, because there's no command to confirm if `xfs_freeze` has frozen I/O.