updating acrolinux

Author: jeffwmartinez

articles/app-service/configure-error-pages.md

@@ -13,14 +13,14 @@ ms.author: jefmarti
 This article explains how to configure custom error pages on your web app. You can configure an error page for specific errors that will be presented to users instead of the default error page. 
 
 ### Prerequisite
-In this tutorial, we'll be adding a custom 403 error page to our web app hosted on App Service and test it with an IP restriction. To do so, you'll need the following:
+In this tutorial, we're adding a custom 403 error page to our web app hosted on App Service and test it with an IP restriction. To do so, you need the following:
 - a web app hosted on App Service w/ a Premium SKU
-- an html file under 10kb in size
+- an html file under 10 kb in size
 
 ## Upload an error page
-For this example, we are uploading and testing a 403 error page to present to the user. Name your html file to match the error code (e.g. `403.hmtl`). Once you have your html file prepared you can upload it to your web app. In the configuration blade, you should see an **Error pages (preview)** tab. Click on this tab to view the error page options. If the options are greyed out, you'll need to upgrade to at least a Premium SKU to use this feature.
+For this example, we're uploading and testing a 403 error page to present to the user. Name your html file to match the error code (for example, `403.hmtl`). Once you have your html file prepared, you can upload it to your web app. In the configuration blade, you should see an **Error pages (preview)** tab. Click on this tab to view the error page options. If the options are greyed out, you need to upgrade to at least a Premium SKU to use this feature.
 
-Select the error code that you'd like to upload an error page for and click **Edit**. On the next screen, click the folder icon to select your html file. The file must be in html format and within the 10kb size limit. Find your .html file and click on the **Upload** button at the bottom of the screen. You'll notice the Status in the table will update from Not Configured to Configured. Then click **Save** to complete the upload. 
+Select the error code that you'd like to upload an error page for and click **Edit**. On the next screen, click the folder icon to select your html file. The file must be in html format and within the 10 kb size limit. Find your .html file and click on the **Upload** button at the bottom of the screen. Notice the Status in the table updates from Not Configured to Configured. Then click **Save** to complete the upload. 
 
 ## Confirm error page
 Once the custom error page is uploaded and saved, we can trigger and view the page. In this example, we can trigger the 403 error by using an IP restriction.
@@ -29,14 +29,14 @@ To set an IP restriction, go to the **Networking** blade and click the **Enabled
 
 Under the **Site access and rules** section, select the **+Add** button to create an IP restriction.
 
-In the form that follows, you'll need to change the Action to **Deny** and fill out the **Priority** and **IP Address Block**. In this example, we use the **Inbound address** found on the Networking blade and we're setting it to /0 (e.g. `12.123.12.123/0`). This will disable all public access when visiting the site.
+In the form that follows, you need to change the Action to **Deny** and fill out the **Priority** and **IP Address Block**. In this example, we use the **Inbound address** found on the Networking blade and we're setting it to /0 (for example, `12.123.12.123/0`). This disables all public access when visiting the site.
 
 Once the Add rule form is filled out, select the **Add rule** button. Then click **Save**.
 
-Once saved, you'll need to restart the site for the changes to take affect. Go to your overview page and select **browse**. You should now see your custom error page load.
+Once saved, you need to restart the site for the changes to take effect. Go to your overview page and select **browse**. You should now see your custom error page load.
 
 ## Error codes
-App Service currently supports 3 types of error codes that are available to customize:
+App Service currently supports three types of error codes that are available to customize:
 
 | Error code  | description |
 | ------------- | ------------- |
@@ -51,4 +51,4 @@ Currently, error pages are only triggered when the error is coming from the fron
 
 2. Why is the error page feature greyed out?
 
-Error pages is currently a Premium feature. You need to use at least a Premium SKU to enable the feature. 
+Error pages are currently a Premium feature. You need to use at least a Premium SKU to enable the feature. 

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md

@@ -75,7 +75,7 @@ For OpenAI, see this [documentation](https://platform.openai.com/docs/api-refere
 - `apiKey`
 - `modelId`
 
-Since we are deploying to App Service, we can secure these secrets in **Azure Key Vault** for protection. Follow the [Quickstart](/azure/key-vault/secrets/quick-create-cli#create-a-key-vault) to set up your Key Vault and add the secrets you saved from earlier.
+Since we're deploying to App Service, we can secure these secrets in **Azure Key Vault** for protection. Follow the [Quickstart](/azure/key-vault/secrets/quick-create-cli#create-a-key-vault) to set up your Key Vault and add the secrets you saved from earlier.
 Next, we can use Key Vault references as app settings in our App Service resource to reference in our application. Follow the instructions in the [documentation](../../app-service-key-vault-references.md?source=recommendations&tabs=azure-cli) to grant your app access to your Key Vault and to set up Key Vault references.
 Then, go to the portal Environment Variables blade in your resource and add the following app settings: