Update articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

Change accepted from Microsoft

Co-authored-by: Esther Fan <[email protected]>

Author: SonnyGillissen

articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

@@ -132,7 +132,7 @@ To secure outbound traffic from your logic app, you can integrate your logic app
   |-------------|------------------|--------|-------------|----------|---------|
   | * | 443 | Subnet integrated with Standard logic app | Storage account | TCP | Storage account |
   | * | 445 | Subnet integrated with Standard logic app | Storage account | TCP | Server Message Block (SMB) File Share |
-  | * | 20000-30000 | Subnet integrated with Standard logic app | Worker Process | TCP | Communication between App Service Plan and Logic App Standard nodes |
+  | * | 20000-30000 | Subnet integrated with Standard logic app | Worker process | TCP | Communication between App Service Plan and Standard logic app nodes |
 
 - For Azure-hosted managed connectors to work, you need to have an uninterrupted connection to the managed API service. With virtual network integration, make sure that no firewall or network security policy blocks these connections. If your virtual network uses a network security group (NSG), user-defined route table (UDR), or a firewall, make sure that the virtual network allows outbound connections to [all managed connector IP addresses](/connectors/common/outbound-ip-addresses#azure-logic-apps) in the corresponding region. Otherwise, Azure-managed connectors won't work.