Merge pull request #14966 from LizCasey1/496156-aac-qual-remove-direct-2

AAC quality check Acrolinx clarity fixes - Remove direction words.

Author: Stacyrch140

docs/example-scenario/apps/scalable-apps-performance-modeling-site-reliability-content.md

@@ -54,11 +54,11 @@ Another important term to note is *service level indicator* (service-level indic
 
 SLOs and SLIs always go hand in hand, and are usually defined in an iterative manner. SLOs are driven by key business objectives, whereas SLIs are driven by what's possible to be measured while implementing the service.
 
-The relationship between the monitored metric, the SLI, and the SLO is depicted below:
+The following image shows the relationship between the monitored metric, the SLI, and the SLO:
 
-:::image type="content" source="media/scalable-apps-performance-modeling-site-reliability-slo.png" alt-text="Identify the right metric for reliability, define how to calculate its SLI, set a target SLO." :::
+:::image type="content" source="media/scalable-apps-performance-modeling-site-reliability-slo.png" alt-text="Diagram that shows how to identify the right metric for reliability, define how to calculate its SLI, and set a target SLO." :::
 
-This is explained in more detail in [Define SLI metrics to calculate SLOs](#define-sli-metrics-to-calculate-slos).
+For more information on this process, see [Define SLI metrics to calculate SLOs](#define-sli-metrics-to-calculate-slos).
 
 ## Modeling scale and performance expectations
 
@@ -149,7 +149,7 @@ The performance of an API must be managed from its inception until it's deprecat
 
 Here are the elements of performance governance:
 
-:::image type="content" source="media/scalable-apps-performance-modeling-site-reliability-lifecycle.png" alt-text="The seven elements of performance governance, as described below." :::
+:::image type="content" source="media/scalable-apps-performance-modeling-site-reliability-lifecycle.png" alt-text="Diagram that shows the seven elements of performance governance, as described in the following section." :::
 
 - **Performance Objectives:** Define the aspirational performance SLOs for the business scenarios.
 - **Performance Modeling:** Identify business-critical workflows and transactions, and conduct modeling to understand the performance-related implications. Capture this information at a granular level for more accurate predictions.

docs/example-scenario/azure-virtual-desktop/azure-virtual-desktop-multi-region-bcdr-content.md

@@ -148,7 +148,7 @@ However, using a single log destination can cause problems if the entire primary
     :::image type="content" source="images/azure-compute-gallery-hires.png" alt-text="Diagram that shows Azure Compute Gallery and Image replicas." lightbox="images/azure-compute-gallery-hires.png":::
 
 - The Azure Compute Gallery isn't a global resource. It's recommended to have at least a secondary gallery in the secondary region. In your primary region, create a gallery, a VM image definition and a VM image version. Then, create the same objects also in the secondary region. When creating the VM image version, there's the possibility to copy the VM image version created in the primary region by specifying the gallery, VM image definition and VM image version used in the primary region. Azure copies the image and creates a local VM image version.
-It's possible to execute this operation using the Azure portal or the Azure CLI command as outlined below:
+It's possible to run this operation by using the Azure portal or the Azure CLI command as outlined in the following articles:
 
   [Create an image definition and an image version](/azure/virtual-machines/image-version)
 
@@ -238,7 +238,7 @@ The following example shows a Cloud Cache configuration and related registry key
     :::image type="content" source="images/fslogix-cloud-cache-registry-keys-office-hires.png" alt-text="Screenshot that shows the Cloud Cache registry keys for Office Container." lightbox="images/fslogix-cloud-cache-registry-keys-office-hires.png":::
 
 > [!NOTE]
-> In the screenshots above, not all the recommended registry keys for FSLogix and Cloud Cache are reported, for brevity and simplicity. For more information, see [FSLogix configuration examples](/fslogix/concepts-configuration-examples).
+> In the previous screenshots, not all the recommended registry keys for FSLogix and Cloud Cache are reported, for brevity and simplicity. For more information, see [FSLogix configuration examples](/fslogix/concepts-configuration-examples).
 
 **Secondary Region = West Europe**
 
@@ -299,9 +299,9 @@ Hybrid Identity Administrator](/entra/identity/role-based-access-control/permiss
 
 | Design area | Description |
 |----------|----------|
-| A    | One of the most important dependencies for Azure Virtual Desktop is the availability of user identity. To access full remote virtual desktops and remote apps from your session hosts, your users need to be able to authenticate. Review the Identity option above.    |
+| A    | One of the most important dependencies for Azure Virtual Desktop is the availability of user identity. To access full remote virtual desktops and remote apps from your session hosts, your users need to be able to authenticate. Review the Identity option.    |
 | B    | If Azure Virtual Desktop users need access to on-premises resources, it's critical that you consider high availability in the network infrastructure that's required to connect to the resources. Assess and evaluate the resiliency of your authentication infrastructure, and consider BCDR aspects for dependent applications and other resources. These considerations will help ensure availability in the secondary disaster recovery location.  |
-| C    | Depending on the size of your deployment and organization structure ensure all subscriptions have enough quota to run Azure Virtual Desktop workloads in different regions and that you have the right Azure role-based access control (Azure RBAC) roles assigned.    |
+| C    | Depending on the size of your deployment and organization structure ensure all subscriptions have enough quota to run Azure Virtual Desktop workloads in different regions and that you have the correct Azure role-based access control (Azure RBAC) roles assigned.    |
 | D    | For the deployment of both host pools in the primary and secondary disaster recovery regions, you should spread your session host VM fleet across multiple availability zones. If availability zones aren't available in the local region, you can use an availability set to make your solution more resilient than with a default deployment.  |
 | E    | The golden image that you use for host pool deployment in the secondary disaster recovery region should be the same you use for the primary. You should store images in the Azure Compute Gallery and configure multiple image replicas in both the primary and the secondary locations.  |
 | F    | You can use [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) or a secondary host pool (hot standby) to maintain a backup environment.   |
@@ -315,9 +315,9 @@ Hybrid Identity Administrator](/entra/identity/role-based-access-control/permiss
 
 | Design area | Description |
 |----------|----------|
-| A    | One of the most important dependencies for Azure Virtual Desktop is the availability of user identity. To access full Azure Virtual Desktops and remote apps from your session hosts, your users need to be able to authenticate. Review the Identity option above.  |
+| A    | One of the most important dependencies for Azure Virtual Desktop is the availability of user identity. To access full Azure Virtual Desktops and remote apps from your session hosts, your users need to be able to authenticate. Review the Identity option.  |
 | B    | If Azure Virtual Desktop users need access to on-premises resources, it's critical that you consider high availability in the network infrastructure that's required to connect to the resources. Assess and evaluate the resiliency of your authentication infrastructure, and consider BCDR aspects for dependent applications and other resources. These considerations will help ensure availability in the secondary disaster recovery location.  |
-| C    | Depending on the size of your deployment and organization structure ensure all subscriptions have enough quota to run Azure Virtual Desktop workloads in different regions and that you have the right Azure RBAC roles assigned.  |
+| C    | Depending on the size of your deployment and organization structure ensure all subscriptions have enough quota to run Azure Virtual Desktop workloads in different regions and that you have the correct Azure RBAC roles assigned.  |
 | D    | Through [availability zones](/azure/reliability/availability-zones-overview), VMs in the host pool are distributed across different datacenters. VMs are still in the same region, and they have higher resiliency and a higher formal 99.99 percent high-availability [SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines). Your capacity planning should include sufficient extra compute capacity to ensure that Azure Virtual Desktop continues to operate, even if a single availability zone is lost.   |
 | E    | Use FSLogix Cloud Cache to build profile resiliency for your users. FSLogix Cloud Cache does affect the sign-on and sign out experience when using poor performing storage. It's common for environments using Cloud Cache to have slightly slower sign-on and sign out times, relative to using traditional VHDLocations, using the same storage. Review the [FSLogix Cloud Cache documentation for recommendations](/fslogix/cloud-cache-resiliency-availability-cncpt) regarding local cache storage.  |
 | F    | Azure NetApp Files for enterprises offer the most value to customers. The Azure services simplify management for Azure Virtual Desktop and are the preferred storage solutions for this workload.  |

docs/example-scenario/dataplate2e/data-platform-end-to-end-content.md

@@ -153,7 +153,7 @@ The analytics use cases covered by the architecture are illustrated by the diffe
 
 1. Within the Raw data lake layer, [organize your data lake](/azure/cloud-adoption-framework/scenarios/data-management/best-practices/data-lake-services) following the best practices around which layers to create, what folder structures to use in each layer and what files format to use for each analytics scenario.
 
-1. Configure [Event Hubs Capture](/azure/event-hubs/event-hubs-capture-overview) or [IoT Hub Storage Endpoints](/azure/iot-hub/iot-hub-devguide-messages-d2c#azure-blob-storage) to save a copy of the events into the [Raw layer](https://techcommunity.microsoft.com/t5/data-architecture-blog/how-to-organize-your-data-lake/ba-p/1182562) of your [Data Lake Storage](/azure/storage/blobs/data-lake-storage-introduction) data lake. This feature implements the "Cold Path" of the [Lambda architecture pattern](/azure/architecture/data-guide/big-data/#lambda-architecture) and allows you to perform historical and trend analysis on the stream data saved in your data lake using [SQL Serverless queries](/azure/synapse-analytics/sql/on-demand-workspace-overview) or [Spark notebooks](/azure/synapse-analytics/spark/apache-spark-development-using-notebooks?tabs=classical) following the pattern for semi-structured data sources described above.
+1. Configure [Event Hubs Capture](/azure/event-hubs/event-hubs-capture-overview) or [IoT Hub Storage Endpoints](/azure/iot-hub/iot-hub-devguide-messages-d2c#azure-blob-storage) to save a copy of the events into the [Raw layer](https://techcommunity.microsoft.com/t5/data-architecture-blog/how-to-organize-your-data-lake/ba-p/1182562) of your [Data Lake Storage](/azure/storage/blobs/data-lake-storage-introduction) data lake. This feature implements the "Cold Path" of the [Lambda architecture pattern](/azure/architecture/data-guide/big-data/#lambda-architecture) and allows you to perform historical and trend analysis on the stream data saved in your data lake using [SQL Serverless queries](/azure/synapse-analytics/sql/on-demand-workspace-overview) or [Spark notebooks](/azure/synapse-analytics/spark/apache-spark-development-using-notebooks?tabs=classical) following the pattern for semi-structured data sources described previously.
 
 ##### Process
 
@@ -205,13 +205,13 @@ The analytics use cases covered by the architecture are illustrated by the diffe
 
 ### Alternatives
 
-- In the architecture above, Azure Synapse pipelines are responsible for data pipeline orchestration. [Azure Data Factory](https://azure.microsoft.com/services/data-factory) pipelines also provide the same capabilities as described in this article.
+- In the preceding architecture, Azure Synapse pipelines are responsible for data pipeline orchestration. [Azure Data Factory](https://azure.microsoft.com/services/data-factory) pipelines also provide the same capabilities as described in this article.
 
 - [Azure Databricks](https://azure.microsoft.com/services/databricks) can also be used as the compute engine used to process structured and unstructured data directly on the data lake.
 
   When using Azure Databricks, you can connect your Power Apps serving layer directly to Delta Lake tables in Azure Databricks without exporting data. Consider this path when business teams need near real-time reads from curated lakehouse tables.
 
-- In the architecture above, Azure Stream Analytics is the service responsible for processing streaming data. Azure Synapse Spark pools and Azure Databricks can also be used to perform the same role through the execution of notebooks.
+- In the preceding architecture, Azure Stream Analytics is the service responsible for processing streaming data. Azure Synapse Spark pools and Azure Databricks can also be used to perform the same role through the execution of notebooks.
 
 - [Azure HDInsight Kafka](https://azure.microsoft.com/services/hdinsight) clusters can also be used to ingest streaming data and provide the right level of performance and scalability required by large streaming workloads.
 
@@ -267,7 +267,7 @@ Data governance is a common challenge in large enterprise environments. On one h
 
 In order to improve the quality of your Azure solutions, follow the recommendations and guidelines defined in the [Azure Well-Architected Framework](/azure/well-architected/) five pillars of architecture excellence: Cost Optimization, Operational Excellence, Performance Efficiency, Reliability, and Security.
 
-Following these recommendations, the services below should be considered as part of the design:
+As you use these recommendations, consider the following services as part of the design:
 
 1. [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory): identity services, single sign-on and multifactor authentication across Azure workloads.
 1. [Microsoft Cost Management](https://azure.microsoft.com/services/cost-management): financial governance over your Azure workloads.
@@ -285,7 +285,7 @@ These considerations implement the pillars of the Azure Well-Architected Framewo
 
 Cost Optimization focuses on ways to reduce unnecessary expenses and improve operational efficiencies. For more information, see [Design review checklist for Cost Optimization](/azure/well-architected/cost-optimization/checklist).
 
-In general, use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator) to estimate costs. The ideal individual pricing tier and the total overall cost of each service included in the architecture is dependent on the amount of data to be processed and stored and the acceptable performance level expected. Use the guide below to learn more about how each service is priced:
+In general, use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator) to estimate costs. The ideal individual pricing tier and the total overall cost of each service included in the architecture is dependent on the amount of data to be processed and stored and the acceptable performance level expected. Use the following links to learn more about how each service is priced:
 
 - [Azure Synapse Analytics](https://azure.microsoft.com/pricing/details/synapse-analytics) serverless architecture allows you to scale your compute and storage levels independently. Compute resources are charged based on usage, and you can scale or pause these resources on demand. Storage resources are billed per terabyte, so your costs increase as you ingest more data.
 
@@ -301,7 +301,7 @@ In general, use the [Azure pricing calculator](https://azure.microsoft.com/prici
 
 - [Azure Stream Analytics](https://azure.microsoft.com/pricing/details/stream-analytics) is charged based on the amount of compute power required to process your stream queries.
 
-- [Power BI](https://powerbi.microsoft.com/pricing) has different product options for different requirements. [Power BI Embedded](https://azure.microsoft.com/pricing/details/power-bi-embedded) provides an Azure-based option for embedding Power BI functionality inside your applications. A Power BI Embedded instance is included in the pricing sample above.
+- [Power BI](https://powerbi.microsoft.com/pricing) has different product options for different requirements. [Power BI Embedded](https://azure.microsoft.com/pricing/details/power-bi-embedded) provides an Azure-based option for embedding Power BI functionality inside your applications.
 
 - [Azure Cosmos DB](https://azure.microsoft.com/pricing/details/cosmos-db) is priced based on the amount of storage and compute resources required by your databases.
 

docs/example-scenario/integration/app-gateway-internal-api-management-function-content.md

@@ -8,7 +8,7 @@ Azure Application Gateway serves as a security checkpoint for APIs. Instead of a
 ## Architecture
 
 :::image type="complex" border="false" source="./media/app-gateway-internal-api-management-function.svg" lightbox="./media/app-gateway-internal-api-management-function.svg" alt-text="The diagram shows a secure baseline architecture for API Management.":::
-   A key icon at the top left represents the Azure subscription. A network interface icon labeled Public IP addresses connects with a rightward arrow to an icon that has two opposing arrows labeled Application Gateway. This gateway sits inside a rectangular area labeled Application Gateway subnet. A brick wall with a globe icon labeled Web Application Firewall policies connects to Application Gateway, which indicates integrated traffic inspection. Below the Application Gateway subnet, there are three icons: Log Analytics workspaces, Application Insights, and azure-api.net. A rightward arrow from Application Gateway leads to a cloud icon labeled API Management Premium, which sits inside a separate rectangular area labeled API Management subnet. A private endpoint is inside a third rectangular area labeled Private endpoint subnet. A downward arrow from the private endpoint leads to a key-in-circle icon labeled Key vaults. Directional arrows throughout the diagram indicate the flow of traffic and secure connectivity between components.
+   A key icon at the top left represents the Azure subscription. A network interface icon labeled Public IP addresses connects with a right-facing arrow to an icon that has two opposing arrows labeled Application Gateway. This gateway sits inside a rectangular area labeled Application Gateway subnet. A brick wall with a globe icon labeled Web Application Firewall policies connects to Application Gateway, which indicates integrated traffic inspection. Under the Application Gateway subnet, there are three icons: Log Analytics workspaces, Application Insights, and azure-api.net. A right-facing arrow from Application Gateway leads to a cloud icon labeled API Management Premium, which sits inside a separate rectangular area labeled API Management subnet. A private endpoint is inside a third rectangular area labeled Private endpoint subnet. A downward arrow from the private endpoint leads to a key-in-circle icon labeled Key vaults. Directional arrows throughout the diagram indicate the flow of traffic and secure connectivity between components.
 :::image-end:::
 
 *Download a [Visio file](https://arch-center.azureedge.net/app-gateway-internal-api-management-function.vsdx) of this architecture.*