Merge pull request #284578 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/expressroute/expressroute-circuit-peerings.md

@@ -51,9 +51,9 @@ Default quotas and limits apply for every ExpressRoute circuit. Refer to the [Az
 
 ## <a name="routingdomains"></a>ExpressRoute peering
 
-An ExpressRoute circuit has multiple routing domains/peerings associated with it: Azure public, Azure private, and Microsoft. Each peering is configured identically on a pair of routers (in active-active or load sharing configuration) for high availability. Azure services are categorized as *Azure public* and *Azure private* to represent the IP addressing schemes.
+An ExpressRoute circuit has two routing domains/peerings associated with it: Azure Private and Microsoft. Each peering is configured identically on a pair of routers (in active-active or load sharing configuration) for high availability. Azure services are categorized as *Azure public* and *Azure private* to represent the IP addressing schemes.
 
-![Diagram showing how Azure public, Azure private, and Microsoft peerings are configured in an ExpressRoute circuit.](./media/expressroute-circuit-peerings/expressroute-peerings.png)
+![Diagram showing how Azure Private and Microsoft peerings are configured in an ExpressRoute circuit.](./media/expressroute-circuit-peerings/expressroute-peerings.png)
 
 ### <a name="privatepeering"></a>Azure private peering
 
@@ -74,7 +74,7 @@ For more information on services supported, costs, and configuration details, se
 
 ## <a name="peeringcompare"></a>Peering comparison
 
-The following table compares the three peerings:
+The following table compares the two peerings:
 
 [!INCLUDE [peering comparison](../../includes/expressroute-peering-comparison.md)]
 

articles/logic-apps/concepts-schedule-automated-recurring-tasks-workflows.md

@@ -36,7 +36,7 @@ You can also use the Schedule built-in actions to pause your workflow before the
 
 This guide describes the capabilities for the Schedule-type built-in triggers and actions.
 
-## Run recurring workloads with without multiple logic apps
+## Run recurring workloads without creating multiple logic apps
 
 You can schedule and run recurring workloads without creating a separate Consumption logic app for each scheduled job and running into the [limit on workflows per region and subscription](logic-apps-limits-and-config.md#definition-limits). Instead, you can either [create a Standard logic app with multiple workflows](create-single-tenant-workflows-azure-portal.md), or use the Consumption logic app pattern that's created by the [Azure QuickStart template: Logic Apps job scheduler](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.logic/logicapps-jobscheduler/).