acrolinx tweaks

Author: halkazwini

includes/cdn-app-dev-prep.md

@@ -15,15 +15,15 @@ Before writing CDN management code, you must do some preparation to enable the c
 * Apply permissions to the resource group so that only authorized users from your Microsoft Entra tenant can interact with the CDN profile
 
 ### Creating the resource group
-1. Sign in to the [Azure Portal](https://portal.azure.com).
-2. Click **Create a resource**.
-3. Search for **Resource group** and in the Resource group pane, click **Create**.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+2. Select **Create a resource**.
+3. Search for **Resource group** and in the Resource group pane, select **Create**.
 
     ![Creating a new resource group](./media/cdn-app-dev-prep/cdn-new-rg-1-include.png)
-3. Name your resource group *CdnConsoleTutorial*.  Select your subscription and choose a location near you.  If you wish, you can click the **Pin to dashboard** checkbox to pin the resource group to the dashboard in the portal.  Pinning makes it easier to find later.  After you've made your selections, click **Create**.
+3. Name your resource group *CdnConsoleTutorial*.  Select your subscription and choose a location near you.  If you wish, you can select the **Pin to dashboard** checkbox to pin the resource group to the dashboard in the portal.  Pinning makes it easier to find later.  After you've made your selections, select **Create**.
 
     ![Screenshot of the Resource group dialog box.](./media/cdn-app-dev-prep/cdn-new-rg-2-include.png)
-4. After the resource group is created, if you didn't pin it to your dashboard, you can find it by clicking **Browse**, then **Resource Groups**.  To open it, click the resource group.  Make a note of your **Subscription ID**. We need it later.
+4. After the resource group is created, if you didn't pin it to your dashboard, you can find it by clicking **Browse**, then **Resource Groups**.  To open it, select the resource group.  Make a note of your **Subscription ID**. We need it later.
 
     ![Screenshot of the C D N Console Tutorial section.](./media/cdn-app-dev-prep/cdn-subscription-id-include.png)
 
@@ -41,7 +41,6 @@ Creating a service principal consists of several steps, including creating a Mic
 >
 > When you get to the step [Assign the application to a role](../articles/active-directory/develop/howto-create-service-principal-portal.md#assign-a-role-to-the-application), use the resource group created earlier,  *CdnConsoleTutorial*, but instead of the **Reader** role, assign the **CDN Profile Contributor** role.  After you assign the application the **CDN Profile Contributor** role on your resource group, return to this tutorial. 
 >
->
 
 Once you've created your service principal and assigned the **CDN Profile Contributor** role, the **Users** blade for your resource group should look similar to the following image.
 
@@ -51,15 +50,13 @@ Once you've created your service principal and assigned the **CDN Profile Contri
 If, instead of a service principal, you'd rather have interactive individual user authentication, the process is similar to that for a service principal.  In fact, you need to follow the same procedure, but make a few minor changes.
 
 > [!IMPORTANT]
-> Only follow these next steps if you are choosing to use individual user authentication instead of a service principal.
->
->
+> Only follow these next steps if you're choosing to use individual user authentication instead of a service principal.
 
 1. When creating your application, instead of **Web Application**, choose **Native application**.
 
     ![Native application](./media/cdn-app-dev-prep/cdn-native-application-include.png)
-2. On the next page, you are prompted for a **redirect URI**.  The URI won't be validated, but remember what you entered. You need it later.
-3. There is no need to create a **client authentication key**.
+2. On the next page, you're prompted for a **redirect URI**.  The URI won't be validated, but remember what you entered. You need it later.
+3. There's no need to create a **client authentication key**.
 4. Instead of assigning a service principal to the **CDN Profile Contributor** role, we're going to assign individual users or groups.  In this example, you can see that I've assigned  *CDN Demo User* to the **CDN Profile Contributor** role.  
 
     ![Individual user access](./media/cdn-app-dev-prep/cdn-user-include.png)

includes/cdn-create-profile.md

@@ -38,4 +38,3 @@ A CDN profile is a container for CDN endpoints and specifies a pricing tier.
     :::image type="content" source="./media/cdn-create-profile/cdn-new-profile.png" alt-text="Input variables in Basics tab.":::
 
 1. Select **Review + Create** then **Create** to create the profile.
-

includes/cdn-limits.md

@@ -21,8 +21,6 @@ ms.custom: include file
 | Maximum requests per second per profile | 100,000 |
 | HTTP header size limit (per header) | 32 KB |
 
-*These two limits are only applicable to Azure CDN Standard from Microsoft (classic). If the traffic is not globally distributed and concentrated in one or two regions, or if a higher quota limit is needed, create an [Azure Support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). 
+*These two limits are only applicable to Azure CDN Standard from Microsoft (classic). If the traffic isn't globally distributed and concentrated in one or two regions, or if a higher quota limit is needed, create an [Azure Support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). 
 
 A Content Delivery Network subscription can contain one or more Content Delivery Network profiles. A Content Delivery Network profile can contain one or more Content Delivery Network endpoints. You might want to use multiple profiles to organize your Content Delivery Network endpoints by internet domain, web application, or some other criteria. 
-
-

includes/cdn-premium-feature.md

@@ -8,5 +8,4 @@ ms.custom: include file
 ---
 
 > [!IMPORTANT]
-> This is a feature of **Azure CDN Premium from Edgio** only, to configure rules on **Azure CDN from Microsoft** please use the [Standard rules engine](../articles/cdn/cdn-standard-rules-engine-reference.md). Advanced rules are not available for **Azure CDN from Akamai**. For a full comparison of CDN features, see [Azure CDN product features](../articles/cdn/cdn-features.md). 
-> 
+> This is a feature of **Azure CDN Premium from Edgio** only, to configure rules on **Azure CDN from Microsoft** please use the [Standard rules engine](../articles/cdn/cdn-standard-rules-engine-reference.md). Advanced rules aren't available for **Azure CDN from Akamai**. For a full comparison of CDN features, see [Azure CDN product features](../articles/cdn/cdn-features.md). 

includes/front-door-classic-retirement.md

@@ -7,4 +7,4 @@ ms.date: 03/18/2024
 ms.custom: include file
 ---
 > [!IMPORTANT]
-> Azure Front Door (classic) will be retired on **March 31, 2027**. To avoid any service disruption, it is important that you [**migrate your Azure Front Door (classic) profiles**](../articles/frontdoor/migrate-tier.md) to Azure Front Door Standard or Premium tier by March 2027. For more information, see [**Azure Front Door (classic) retirement**](https://azure.microsoft.com/updates/azure-front-door-classic-will-be-retired-on-31-march-2027/).
+> Azure Front Door (classic) will be retired on **March 31, 2027**. To avoid any service disruption, it's important that you [**migrate your Azure Front Door (classic) profiles**](../articles/frontdoor/migrate-tier.md) to Azure Front Door Standard or Premium tier by March 2027. For more information, see [**Azure Front Door (classic) retirement**](https://azure.microsoft.com/updates/azure-front-door-classic-will-be-retired-on-31-march-2027/).

includes/front-door-edge-locations.md

@@ -9,7 +9,7 @@ ms.custom: include file
 
 | Region | Cities |
 |--|--|
-| North America | Etobicoke, Canada (2)<br />Montreal, Canada<br />Vancouver, Canada (2)<br />Querétaro, Mexico (2)<br />Atlanta, GA, USA (3)<br />Boydton, VA, USA (2)<br />Chaska, MN, USA (2)<br /> Cheyenne, WY, USA (2)<br />Chicago, IL, USA (4)<br /> Dallas, TX, USA (4)<br />Des Moines,IA, USA (3)<br />Detroit, MI, USA<br />Englewood, CO, USA (2)<br />Honolulu, HI, USA<br />Houston, TX, USA (3)<br />Jacksonville, FL, USA (2)<br />Las Vegas, NV, USA (3)<br />Los Angeles, CA, USA (2)<br />Manassas, VA, USA (3)<br />Memphis, TN, USA<br /> Miami, FL, USA (4)<br />Minneapolis, MN, USA (2)<br />Needham Heights, MA, USA (2)<br /> Nashville, TN, USA<br />Newark, NJ, USA<br />New York, NY, USA (2)<br />Philadelphia, PA, USA<br />Phoenix, AZ, USA<br />Plano, TX, USA<br />Portland, OR, USA<br />Quincy, WA, USA (3)<br />San Antonio, TX, USA (4)<br />San Jose, CA, USA (4)<br />Salt Lake City, UT, USA (3)<br />Seattle, WA, USA (2)<br />Secaucus, NJ, USA (2)<br />Southfield, MI, USA<br />Tempe, AZ, USA<br /> |
+| North America | Etobicoke, Canada (2)<br />Montreal, Canada<br />Vancouver, Canada (2)<br />Querétaro, Mexico (2)<br />Atlanta, GA, USA (3)<br />Boydton, VA, USA (2)<br />Chaska, MN, USA (2)<br /> Cheyenne, WY, USA (2)<br />Chicago, IL, USA (4)<br /> Dallas, TX, USA (4)<br />Des Moines, IA, USA (3)<br />Detroit, MI, USA<br />Englewood, CO, USA (2)<br />Honolulu, HI, USA<br />Houston, TX, USA (3)<br />Jacksonville, FL, USA (2)<br />Las Vegas, NV, USA (3)<br />Los Angeles, CA, USA (2)<br />Manassas, VA, USA (3)<br />Memphis, TN, USA<br /> Miami, FL, USA (4)<br />Minneapolis, MN, USA (2)<br />Needham Heights, MA, USA (2)<br /> Nashville, TN, USA<br />Newark, NJ, USA<br />New York, NY, USA (2)<br />Philadelphia, PA, USA<br />Phoenix, AZ, USA<br />Plano, TX, USA<br />Portland, OR, USA<br />Quincy, WA, USA (3)<br />San Antonio, TX, USA (4)<br />San Jose, CA, USA (4)<br />Salt Lake City, UT, USA (3)<br />Seattle, WA, USA (2)<br />Secaucus, NJ, USA (2)<br />Southfield, MI, USA<br />Tempe, AZ, USA<br /> |
 | South America | Buenos Aires, Argentina<br />Campinas, Brazil (2)<br />Rio de Janeiro, Brazil (3)<br />Sao Paulo, Brazil (2)<br />Bogota, Colombia |
 | Europe | Zaventem, Belgium (2)<br />Sofia, Bulgaria (2)<br />Prague, Czech Republic<br />Ballerup, Denmark<br /> Vantaa, Finland<br />Les Ulis, France (3)<br />Paris, France<br />Saint Denis, France (2)<br />Berlin, Germany<br />Duesseldorf, Germany<br />Frankfurt, Germany (2)<br />Munich, Germany<br />Russelsheim, Germany (2)<br />Athens, Greece<br />Budapest, Hungary<br />Dublin, Ireland (2)<br />Milan, Italy<br />Rome, Italy (2)<br />Amsterdam, Netherlands<br />Oslo, Norway<br />Stavanger, Norway<br />Warsaw, Poland<br />Lisbon, Portugal<br />Bucharest, Romania<br />Barcelona, Spain<br />Madrid, Spain<br />Bromma, Sweden (2)<br />Zurich, Switzerland (2)<br />London, United Kingdom (5)<br />Manchester, United Kingdom |
 | Africa | Cairo, Egypt (2)<br />Nairobi, Kenya<br />Rabat, Morocco<br />Lagos, Nigeria<br />Cape Town, South Africa<br />Isando, South Africa (3) |

includes/front-door-limits.md

@@ -7,7 +7,7 @@ ms.date: 06/19/2023
 ms.custom: include file
 ---
 
-* In addition to the following limits, there are [composite limit on the number of routing rules, front-end domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
+- In addition to the following limits, there are [composite limit on the number of routing rules, front-end domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
 
 | Resource | Classic tier limit |
 | --- | --- |
@@ -44,8 +44,8 @@ ms.custom: include file
 
 ### Azure Front Door Standard and Premium service limits
 
-* Maximum of **500** total Standard and Premium profiles per subscription.
-* In addition to the following limits, there are [composite limit on the number of routes, domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
+- Maximum of **500** total Standard and Premium profiles per subscription.
+- In addition to the following limits, there are [composite limit on the number of routes, domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
 
 | Resource | Standard tier limit | Premium tier limit |
 | --- | --- | --- |
@@ -90,16 +90,16 @@ ms.custom: include file
 
 ##### From Client to Front Door
 
-* Header timeout - After establishing TCP/TLS connection, Front Door has a 5-second timeout for receiving all headers from the client. The connection is terminated if the client doesn't send headers within 5 seconds. You can't configure this timeout value.
-* HTTP keep-alive timeout - Front Door has a 90-second HTTP keep-alive timeout. The connection is terminated if the client doesn't send data for 90 seconds. You can't configure this timeout value.
+- Header timeout - After establishing TCP/TLS connection, Front Door has a 5-second timeout for receiving all headers from the client. The connection is terminated if the client doesn't send headers within 5 seconds. You can't configure this timeout value.
+- HTTP keep-alive timeout - Front Door has a 90-second HTTP keep-alive timeout. The connection is terminated if the client doesn't send data for 90 seconds. You can't configure this timeout value.
 
 ##### Front Door to application back-end
 
-* After the HTTP request gets forwarded to the back end, Azure Front Door waits for 60 seconds (Standard and Premium) or 30 seconds (classic) for the first packet from the back end. Then it returns a 503 error to the client, or 504 for a cached request. You can configure this value using the *originResponseTimeoutSeconds* field in Azure Front Door Standard and Premium API, or the sendRecvTimeoutSeconds field in the Azure Front Door (classic) API.
+- After the HTTP request gets forwarded to the back end, Azure Front Door waits for 60 seconds (Standard and Premium) or 30 seconds (classic) for the first packet from the back end. Then it returns a 503 error to the client, or 504 for a cached request. You can configure this value using the *originResponseTimeoutSeconds* field in Azure Front Door Standard and Premium API, or the sendRecvTimeoutSeconds field in the Azure Front Door (classic) API.
 
-* After the back end receives the first packet, if the origin pauses for any reason in the middle of the response body beyond the originResponseTimeoutSeconds or sendRecvTimeoutSeconds, the response is canceled.
+- After the back end receives the first packet, if the origin pauses for any reason in the middle of the response body beyond the originResponseTimeoutSeconds or sendRecvTimeoutSeconds, the response is canceled.
 
-* Front Door takes advantage of HTTP keep-alive to keep connections open for reuse from previous requests. These connections have an idle timeout of 90 seconds. Azure Front Door would disconnect idle connections after reaching the 90-second idle timeout. This timeout value can't be configured.
+- Front Door takes advantage of HTTP keep-alive to keep connections open for reuse from previous requests. These connections have an idle timeout of 90 seconds. Azure Front Door would disconnect idle connections after reaching the 90-second idle timeout. This timeout value can't be configured.
 
 #### Upload and download data limit
 
@@ -109,12 +109,12 @@ ms.custom: include file
 | **Upload** |    There's no limit as long as each CTE upload is less than 2 GB. | The size can't be larger than 2 GB. |
 
 #### Other limits
-* Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)
-* Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.
-* Maximum HTTP response header size from health probe URL - 4,096 bytes - Specified the maximum length of all the response headers of health probes. 
-* Maximum rules engine action header value character: 640 characters.
-* Maximum rules engine condition header value character: 256 characters.
-* Maximum ETag header size: 128 bytes
-* Maximum endpoint name for Standard and Premium: 46 characters.
+- Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)
+- Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.
+- Maximum HTTP response header size from health probe URL - 4,096 bytes - Specified the maximum length of all the response headers of health probes. 
+- Maximum rules engine action header value character: 640 characters.
+- Maximum rules engine condition header value character: 256 characters.
+- Maximum ETag header size: 128 bytes
+- Maximum endpoint name for Standard and Premium: 46 characters.
 
 For more information about limits that apply to Rules Engine configurations, see [rules engine terminology](../articles/frontdoor/front-door-rules-engine.md#terminology)