Merge pull request #14987 from MicrosoftDocs/bulk-ai-typofix

[Bulk] AI suggested typo corrections and one URL edit

Author: JamesJBarnett

docs/antipatterns/busy-database/index.md

@@ -84,7 +84,7 @@ ORDER BY soh.[TotalDue] DESC
 FOR XML PATH ('Order'), ROOT('Orders')
 ```
 
-Clearly, this is complex query. As we'll see later, it turns out to use significant processing resources on the database server.
+Clearly, this is a complex query. As we'll see later, it turns out to use significant processing resources on the database server.
 
 ## How to fix the problem
 
@@ -269,4 +269,4 @@ CPU and DTU utilization shows that the system took longer to reach saturation, d
 - [Extraneous Fetching antipattern][ExtraneousFetching]
 
 [dtu]: /azure/sql-database/sql-database-service-tiers-dtu
-[ExtraneousFetching]: ../extraneous-fetching/index.md
+[ExtraneousFetching]: ../extraneous-fetching/index.md

docs/data-guide/disaster-recovery/dr-for-azure-data-platform-scenario-details-content.md

@@ -105,7 +105,7 @@ The following sections present a breakdown of Contoso activity necessary across
         - Availability Zone failure: Contoso would need to validate availability and redeploy if necessary.
         - Azure regional failure: Contoso would need to redeploy the Foundation Azure Firewalls into the secondary region.
     - Notes
-        - Azure Firewall can be created with [Availability Zones](/en-au/azure/firewall/deploy-availability-zone-powershell) for increased availability.
+        - Azure Firewall can be created with [Availability Zones](/azure/firewall/deploy-availability-zone-powershell) for increased availability.
         - A "Warm Spare" strategy would mitigate this activity.
 
 - **Azure DDoS**

docs/example-scenario/integration/sma-opcon-azure-content.md

@@ -116,7 +116,7 @@ The diagram has two main sections: the on-premises network and Azure. The enviro
      - OpCon administration 
      - OpCon MFT administration
      - OpCon workflow development, implementation, and monitoring  
-     - OfCon Self Service
+     - OpCon Self Service
      - OpCon Vision (task dashboard)
      - OpCon MFT central application (dashboard and query application)
 
@@ -332,4 +332,4 @@ For more information about this solution:
 ## Related resources
 
 - [Unisys ClearPath Forward OS 2200 enterprise server virtualization on Azure](../../mainframe/virtualization-of-unisys-clearpath-forward-os-2200-enterprise-server-on-azure.yml)
-- [Unisys ClearPath Forward MCP mainframe rehost to Azure by using Unisys virtualization](../../example-scenario/mainframe/unisys-clearpath-forward-mainframe-rehost.yml)
+- [Unisys ClearPath Forward MCP mainframe rehost to Azure by using Unisys virtualization](../../example-scenario/mainframe/unisys-clearpath-forward-mainframe-rehost.yml)

docs/guide/architecture-styles/n-tier.md

@@ -74,7 +74,7 @@ Implement N-tier architectures effectively by using managed services that provid
 This section describes an N-tier architecture that runs on VMs.
 
 > [!NOTE]
-> Use VMs to host an N-teir architecture if you plan to migrate an existing application to Azure with minimal refactoring. Otherwise, consider using [managed services to implement the architecture](/azure/app-service/tutorial-secure-ntier-app), such as Azure App Service or Azure Container Apps.
+> Use VMs to host an N-tier architecture if you plan to migrate an existing application to Azure with minimal refactoring. Otherwise, consider using [managed services to implement the architecture](/azure/app-service/tutorial-secure-ntier-app), such as Azure App Service or Azure Container Apps.
 
 :::image type="complex" source="./images/n-tier-physical-bastion.png" border="false" lightbox="./images/n-tier-physical-bastion.png" alt-text="Diagram that shows an N-tier architecture.":::
 The flow begins with the internet, which connects to a load balancer that routes incoming traffic to two network virtual appliances (NVAs) located in the perimeter network. Traffic then passes through another load balancer to reach multiple VMs in the web tier. A third load balancer forwards traffic from the web tier to the business tier, which includes multiple VMs. The business tier connects through a fourth load balancer to the data tier, which includes a primary and secondary SQL Server. For secure administrative access, DevOps personnel use the Azure portal to connect to an Azure Bastion host located in the AzureBastionSubnet. The perimeter network, all tiers, and the AzureBastionSubnet reside in a virtual network.
@@ -121,4 +121,4 @@ Network security groups restrict access to each tier. For example, the database
 [caching]: ../../best-practices/caching.yml
 [ha-nva]: ../../networking/guide/network-virtual-appliance-high-availability.md
 [hybrid-network]: ../../reference-architectures/hybrid-networking/index.yml
-[sql-always-on]: /sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server
+[sql-always-on]: /sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server

docs/guide/devops/deployment-scripts-property-check-content.md

@@ -6,7 +6,7 @@ This article uses an Azure Virtual WAN scenario to illustrate the technique. The
 > - [`azResourceStateCheck.bicep`](https://github.com/Azure/CAE-Bits/blob/main/infra/samples/deployment-scripts-property-check/modules/azResourceStateCheck.bicep)
 > - [Invoke-AzResourceStateCheck.ps1](https://github.com/Azure/CAE-Bits/blob/main/infra/samples/deployment-scripts-property-check/scripts/Invoke-AzResourceStateCheck.ps1)
 
-You can adapt the files for your deployment. The azResourceStateCheck.bicep module is parameterized for ease of reuse. Be sure to note how the **dependsOn** property is used in orchestration.bicep to make the vwanvhcs.bicep module deployment depend on the azResourceStateCheck.bicep nodule deployment.
+You can adapt the files for your deployment. The azResourceStateCheck.bicep module is parameterized for ease of reuse. Be sure to note how the **dependsOn** property is used in orchestration.bicep to make the vwanvhcs.bicep module deployment depend on the azResourceStateCheck.bicep module deployment.
 
 ## Architecture
 
@@ -226,4 +226,4 @@ Other contributor:
 
 - [Hub-spoke network topology with Azure Virtual WAN](../../networking/architecture/hub-spoke-virtual-wan-architecture.yml)
 - [Architectural approaches for the deployment and configuration of multitenant solutions](../multitenant/approaches/deployment-configuration.md)
-- [DevSecOps for infrastructure as code (IaC)](../../solution-ideas/articles/devsecops-infrastructure-as-code.yml)
+- [DevSecOps for infrastructure as code (IaC)](../../solution-ideas/articles/devsecops-infrastructure-as-code.yml)

docs/guide/technology-choices/service-for-java-comparison-content.md

@@ -137,16 +137,16 @@ The MicroProfile project provides a collection of specifications designed to hel
 
 The following table provides build or migration information by application type and Azure service.
 
-|                              | Type             | Java SE  | MicroProfile | JarkartaSE |
-|------------------------------|------------------|----------|--------------|------------|
-| **Virtual Machine**          | IaaS             | ✔ | ✔     | ✔   |
-| **VMware Tanzu**             | IaaS             | ✔ |              |            |
-| **Azure Kubernetes Service** | Container        | ✔ | ✔     | ✔   |
-| **Red Hat OpenShift**        | Container        | ✔ | ✔     | ✔   |
-| **Azure Container App**      | PaaS             | ✔ | ✔     |            |
-| **JBoss EAP**                | PaaS App Service | ✔ |              | ✔   |
-| **Apache Tomcat**            | PaaS App Service | ✔ |              |            |
-| **Java SE**                  | PaaS App Service | ✔ | ✔     |            |
+|                              | Type             | Java SE  | MicroProfile | JakartaSE |
+|------------------------------|------------------|----------|--------------|-----------|
+| **Virtual Machine**          | IaaS             | ✔ | ✔     | ✔  |
+| **VMware Tanzu**             | IaaS             | ✔ |              |           |
+| **Azure Kubernetes Service** | Container        | ✔ | ✔     | ✔  |
+| **Red Hat OpenShift**        | Container        | ✔ | ✔     | ✔  |
+| **Azure Container App**      | PaaS             | ✔ | ✔     |           |
+| **JBoss EAP**                | PaaS App Service | ✔ |              | ✔  |
+| **Apache Tomcat**            | PaaS App Service | ✔ |              |           |
+| **Java SE**                  | PaaS App Service | ✔ | ✔     |           |
 
 
 ## Contributors
@@ -179,4 +179,4 @@ Principal authors:
 [4]: https://azure.microsoft.com/global-infrastructure/services/?products=virtual-machines
 [5]: /azure/devops/pipelines/?view=azure-devops
 [6]: /azure/developer/jenkins
-[7]: /azure/hdinsight/kafka/apache-kafka-introduction
+[7]: /azure/hdinsight/kafka/apache-kafka-introduction

docs/hybrid/hybrid-perf-monitoring-content.md

@@ -28,7 +28,7 @@ This reference architecture shows how to use Azure Monitor to monitor the perfor
 - **Azure Monitor - Visualizations**. Azure Monitor uses visualization tools to review application and infrastructure components and communications between services in Azure Monitor. Visualization tools include **Application Map in Azure Application Insight**, **the Map feature of Azure Monitor for VMs**, **Azure Monitor Workbooks**, and various dashboard views available within Azure Monitor. For more information, see [Use the Map feature of Azure Monitor for VMs to understand application components][service-map], [Create and share dashboards of Log Analytics data][share-dashboards], and [Azure Monitor Workbooks][monitor-workbooks].
 - **Azure Monitor - Integrations**. Azure Monitor integrates with a range of partner and third-party tools and extensions. These tools and extensions enhance and build upon existing Azure Monitor functionality, such as analysis and visualizations.
 - **Azure Monitor - Actions - Alerts**. Variations in metric and log data can indicate the occurrence of events. Rules define the data variations that trigger alerts, provide notifications, and initiate remediation responses. In this architecture, when an alert is triggered, automation runbooks automatically remediate the on-premises VMs and Azure VMs. Webhook actions, Service Management integration, and other action types are also available. For more information, see [Create, view, and manage metric alerts using Azure Monitor][manage-metrics-alerts] and [Create, view, and manage log alerts using Azure Monitor][manage-log-alerts].
-- **Azure Monitor - Actions - Autoscale**. Autoscale adds or removes VM instances according to deman, which maintains performance and increases cost effectiveness. In this architecture, Autoscale has conditions defined around average CPU load (in percentage). When conditions are met, Azure Monitor Autoscale will adjust the scale set according to demand. For more information, see [Overview of autoscale in Microsoft Azure][autoscale-overview].
+- **Azure Monitor - Actions - Autoscale**. Autoscale adds or removes VM instances according to demand, which maintains performance and increases cost effectiveness. In this architecture, Autoscale has conditions defined around average CPU load (in percentage). When conditions are met, Azure Monitor Autoscale will adjust the scale set according to demand. For more information, see [Overview of autoscale in Microsoft Azure][autoscale-overview].
 
 ### Components
 
@@ -233,4 +233,4 @@ Learn more about the component technologies:
 [itsm]: /azure/azure-monitor/platform/itsmc-overview
 [monitor-pricing]: https://azure.microsoft.com/pricing/details/monitor/
 [pricing-calculator]: https://azure.microsoft.com/pricing/calculator/?service=monitor
-[azmon-for-vms]: /azure/azure-monitor/insights/vminsights-overview
+[azmon-for-vms]: /azure/azure-monitor/insights/vminsights-overview