Fix Acrolinx issues

Author: ecfan

articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md

@@ -64,9 +64,9 @@ This deployment method requires temporary public access to your storage account.
 
    1. On the logic app resource menu, under **Settings**, select **Environment variables**.
 
-   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exist, and set the value to **1**.
+   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exists, and set the value to **1**.
 
-   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exist, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
+   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exists, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
 
 1. After you apply these app settings, you can remove public access from your storage account.
 

articles/logic-apps/view-workflow-status-run-history.md

@@ -165,7 +165,7 @@ Each time that a trigger successfully fires, Azure Logic Apps creates a workflow
    | **Skipped** | ![Skipped icon][skipped-icon] | The action was skipped because its **runAfter** conditions weren't met, for example, a preceding action failed. Each action has a `runAfter` object where you can set up conditions that must be met before the current action can run. |
    | **Succeeded** | ![Succeeded icon][succeeded-icon] | The action succeeded. |
    | **Succeeded with retries** | ![Succeeded-with-retries-icon][succeeded-with-retries-icon] | The action succeeded but only after a single or multiple retries. To review the retry history, on the run history page, select that action so that you can view the inputs and outputs. |
-   | **Timed out** | ![Timed-out icon][timed-out-icon] | The action stopped due to the time-out limit specified by that action's settings. |
+   | **Timed out** | ![Timed-out icon][timed-out-icon] | The action stopped due to the time out limit specified by that action's settings. |
    | **Waiting** | ![Waiting icon][waiting-icon] | Applies to a webhook action that is waiting for an inbound request from a caller. |
 
    [aborted-icon]: media/view-workflow-status-run-history/aborted.png
@@ -257,7 +257,7 @@ You can view run history only for stateful workflows, not stateless workflows. T
    | **Skipped** | ![Skipped icon][skipped-icon] | The action was skipped because its **runAfter** conditions weren't met, for example, a preceding action failed. Each action has a `runAfter` object where you can set up conditions that must be met before the current action can run. |
    | **Succeeded** | ![Succeeded icon][succeeded-icon] | The action succeeded. |
    | **Succeeded with retries** | ![Succeeded-with-retries-icon][succeeded-with-retries-icon] | The action succeeded but only after a single or multiple retries. To review the retry history, on the run history page, select that action so that you can view the inputs and outputs. |
-   | **Timed out** | ![Timed-out icon][timed-out-icon] | The action stopped due to the time-out limit specified by that action's settings. |
+   | **Timed out** | ![Timed-out icon][timed-out-icon] | The action stopped due to the timeout limit specified by that action's settings. |
    | **Waiting** | ![Waiting icon][waiting-icon] | Applies to a webhook action that is waiting for an inbound request from a caller. |
 
    [aborted-icon]: media/view-workflow-status-run-history/aborted.png
@@ -288,7 +288,7 @@ You can view run history only for stateful workflows, not stateless workflows. T
    > are decrypted only when a user requests to view that data. You can 
    > [hide inputs and outputs in the workflow run history](logic-apps-securing-a-logic-app.md#obfuscate)
    > or control user access to this information by using
-   > [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md).
+   > [Azure role-based access control (RBAC)](../role-based-access-control/overview.md).
 
 ---