Merge branch 'main' into aca/v-jaswel_work_item_185409_20250225

Author: v-jaswel

articles/dev-box/how-to-generate-visual-studio-caches.md

@@ -11,7 +11,7 @@ ms.author: rosemalcolm
 ms.date: 02/23/2025
 ms.topic: how-to
 
-#customer intent: As a platfrom engineer, I want to learn how to precache Visual Studio solutions for Microsoft Dev Boxes, so that developers can get strated on VS solutions more quickly.
+#customer intent: As a platform engineer, I want to learn how to precache Visual Studio solutions for Microsoft Dev Boxes, so that developers can get strated on VS solutions more quickly.
 ---
 
 # Optimize the Visual Studio experience on Microsoft Dev Box

articles/dev-box/how-to-manage-dev-box-definitions.md

@@ -80,7 +80,7 @@ The following steps show you how to create a dev box definition by using an exis
    | **Name** | Enter a descriptive name for your dev box definition. | You can't change the dev box definition name after creation. |
    | **Image** | Select the base operating system for the dev box. You can select an image from Azure Marketplace or from Azure Compute Gallery. </br> If you're creating a dev box definition for testing purposes, consider using the **Visual Studio 2022 Enterprise on Windows 11 Enterprise + Microsoft 365 Apps 22H2** image or **Visual Studio 2022 Pro on Windows 11 Enterprise + Microsoft 365 Apps 22H2** image. | To access custom images when you create a dev box definition, you can use Azure Compute Gallery. For more information, see [Configure Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md). |
    | **Image version** | Select a specific, numbered version to ensure that all the dev boxes in the pool always use the same version of the image. Select **Latest** to ensure that new dev boxes use the latest image available. | Selecting the **Latest** image version enables the dev box pool to use the most recent version of your chosen image from the gallery. This approach ensures the created dev boxes stay up to date with the latest tools and code for your image. Existing dev boxes aren't modified when an image version is updated. |
-   | **Compute** | Select the compute combination for your dev box definition. | Dev boxes use Azure vitual machines for compute. |
+   | **Compute** | Select the compute combination for your dev box definition. | Dev boxes use Azure virtual machines for compute. |
    | **Storage** | Select the amount of storage for your dev box definition. | Dev boxes use Azure Premium SSDs for storage. |
    | **Enable hibernation**| Leave this checkbox unselected. | |
 

articles/logic-apps/logic-apps-examples-and-scenarios.md

@@ -168,7 +168,7 @@ You can fully develop and deploy logic app resources with Azure DevOps or any ot
 ##### Monitor Standard workflows
 
 * [Monitor health for Standard workflows in Azure Logic Apps with Health Check](monitor-health-standard-workflows.md)
-* [Enable and view enhanced telemetry in Application Insights for Standard worklfows](enable-enhanced-telemetry-standard-workflows.md)
+* [Enable and view enhanced telemetry in Application Insights for Standard workflows](enable-enhanced-telemetry-standard-workflows.md)
 * [Monitor and track B2B transactions in Standard workflows](monitor-track-b2b-transactions-standard.md)
 
 ## Other integrations and capabilities

articles/logic-apps/power-automate-migration.md

@@ -177,7 +177,7 @@ This migration tool converts a Power Automate flow into the equivalent Standard
 
 However, due to security constraints, the migration tool can't automatically transfer the connections used by the Power Automate flow. While the tool automates most of the flow conversion, you must manually recreate the connections in the logic app workflow. This manual step is necessary to fully meet the security protocols and compliance standards for Azure Logic Apps.
 
-Despite this requirement, the migration tool offers significant time and resource savings by eliminating the need to manually recreate entire workflows. The tool's automated process drastically reduces any other necessary manual effort and shortens the overall migration timeline. With this automation, your team can focus energy on setting up and optmizing connections, not on rebuilding workflows.
+Despite this requirement, the migration tool offers significant time and resource savings by eliminating the need to manually recreate entire workflows. The tool's automated process drastically reduces any other necessary manual effort and shortens the overall migration timeline. With this automation, your team can focus energy on setting up and optimizing connections, not on rebuilding workflows.
 -->
 
 ### Migration testing and validation