Merge pull request #93454 from csj/patch-1

Update networking.md

Author: Court72

articles/container-apps/networking.md

@@ -11,7 +11,7 @@ ms.author: cshoe
 
 # Networking architecture in Azure Container Apps
 
-Azure Container Apps run in the context of an [environment](environment.md), which is supported by a virtual network (VNET). When you create an environment, you can provide a custom VNET, otherwise a VNET is automatically generated for you. Generated VNETs are inaccessible to you as they're created in Microsoft's tenent. To take full control over your VNET, provide an existing VNET to Container Apps as you create your environment.
+Azure Container Apps run in the context of an [environment](environment.md), which is supported by a virtual network (VNET). When you create an environment, you can provide a custom VNET, otherwise a VNET is automatically generated for you. Generated VNETs are inaccessible to you as they're created in Microsoft's tenant. To take full control over your VNET, provide an existing VNET to Container Apps as you create your environment.
 
 The following articles feature step-by-step instructions for creating Container Apps environments with different accessibility levels.
 
@@ -97,7 +97,7 @@ Once you're satisfied with the latest revision, you can lock traffic to that rev
 
 #### Update existing revision
 
-Consider a situation where you have a known good revision that's serving 100% of your traffic, but you want to issue and update to your app. You can deploy and test new revisions using their direct endpoints without affecting the main revision serving the app.
+Consider a situation where you have a known good revision that's serving 100% of your traffic, but you want to issue an update to your app. You can deploy and test new revisions using their direct endpoints without affecting the main revision serving the app.
 
 Once you're satisfied with the updated revision, you can shift a portion of traffic to the new revision for testing and verification.