Apply suggestions from PR review

Author: Court72

articles/logic-apps/biztalk-server-migration-approaches.md

@@ -82,7 +82,7 @@ Under this framework, BizTalk migrations are [mission-critical workloads](/azure
 
 To complete the architecture design for your BizTalk migration, follow [Design methodology for mission-critical workloads on Azure](/azure/well-architected/mission-critical/mission-critical-design-methodology). For an initial architecture and topology, review and use the reference architecture described in [Basic enterprise integration on Azure](/azure/architecture/reference-architectures/enterprise-integration/basic-enterprise-integration) in the [Azure Architecture Center](/azure/architecture/browse/).
 
-To set up your initial environment, use the [Azure Integration Services Landing Zone Accelerator](/Azure/Integration-Services-Landing-Zone-Accelerator), which is targeted for building and deploying an integration platform using a typical enterprise landing zone design.
+To set up your initial environment, use the [Azure Integration Services Landing Zone Accelerator](https://github.com/Azure/Integration-Services-Landing-Zone-Accelerator), which is targeted for building and deploying an integration platform using a typical enterprise landing zone design.
 
 #### Minimum viable project (MVP) definition
 
@@ -166,7 +166,7 @@ The following diagram shows the events that should happen during migration waves
 | Step | Description | 
 |------|--------------|
 | 1 | Discover existing BizTalk apps and interfaces. Although introduced in Sprint 0, this activity should happen when each wave starts. Customers might continue making changes in your BizTalk environment. <br><br>Resources: <br>- [BizTalk Migration tool](https://github.com/Azure/aimtool) <br>- [BizTalk Documenter tool](https://github.com/mbrimble/biztalkdocumenter) |
-| 2 | Set up your initial migration environment. You can use the [Azure Integration Services Landing Zone Accelerator](/Azure/Integration-Services-Landing-Zone-Accelerator), which is a cloud adoption framework for building and deploying an integration platform that has a typical enterprise landing zone design. As the workload owner, you can confidently achieve your target technical state by using the provided [architectural guidance and BizTalk migration resources](https://techcommunity.microsoft.com/blog/integrationsonazureblog/biztalk-server-migration-to-azure-integration-services-resources/3733464). <br><br>For an example architecture, see [Example migration environment](#initial-migration-environment). |
+| 2 | Set up your initial migration environment. You can use the [Azure Integration Services Landing Zone Accelerator](https://github.com/Azure/Integration-Services-Landing-Zone-Accelerator), which is a cloud adoption framework for building and deploying an integration platform that has a typical enterprise landing zone design. As the workload owner, you can confidently achieve your target technical state by using the provided [architectural guidance and BizTalk migration resources](https://techcommunity.microsoft.com/blog/integrationsonazureblog/biztalk-server-migration-to-azure-integration-services-resources/3733464). <br><br>For an example architecture, see [Example migration environment](#initial-migration-environment). |
 | 3 | Create and test Standard logic app workflows that run in single-tenant Azure Logic Apps using either the Azure portal or Visual Studio Code with the Azure Logic Apps (Standard) extension. With Visual Studio Code, you can locally develop, test, and store your logic app project using any source control system. <br><br>For more information, see the following documentation: <br><br>- [Create an example Standard logic app workflow using the Azure portal](/azure/logic-apps/create-single-tenant-workflows-azure-portal) <br>- [Create an example Standard logic app workflow using Visual Studio Code](/azure/logic-apps/create-single-tenant-workflows-visual-studio-code) <br><br>For a diagram that shows an example logic app and connections, see [Example migration environment](#initial-migration-environment). |
 | 4 | To get the full benefits from easily and consistently deploying your Standard logic app workflows across different environments and platforms, you must also automate your build and deployment process. The Azure Logic Apps (Standard) extension for Visual Studio Code provides tools for you to create and maintain automated build and deployment processes using Azure DevOps. <br><br>For more information, see [Automate build and deployment for Standard logic app workflows with Azure DevOps](/azure/logic-apps/automate-build-deployment-standard). | 
 | 5 | To deploy mission-critical Standard logic apps that are always available and responsive, even during updates or maintenance, enable zero downtime deployment by creating and using deployment slots. Zero downtime means that when you deploy new versions of your app, end users shouldn't experience disruption or downtime. <br><br>For more information, see [Set up deployment slots to enable zero downtime deployment in Azure Logic Apps](/azure/logic-apps/set-up-deployment-slots). | 

articles/logic-apps/create-standard-workflows-hybrid-deployment.md

@@ -236,7 +236,7 @@ After you finish building your workflow, you can deploy your logic app to your A
 > If your changes still haven't appeared in the workflow, you can check whether the revision exists:
 >
 > 1. In the [Azure portal](https://portal.azure.com), open your resource. On the resource menu, 
->    under **Revisions**, and select **Revisions and replicas**.
+>    under **Revisions**, select **Revisions and replicas**.
 >
 > 1. On the **Revisions and replicas** page, on the **Active revisions** tab, check whether 
 >    a new revision appears on the list.