Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: RoRoJ

pages/vpc/reference-content/understanding-routing.mdx

@@ -127,11 +127,11 @@ When you update to new routing behavior, the only automatic change is that your
 
 Your Private Networks will continue to receive only their local default route announcements, **unless** you enable `Receive all default route announcements` in each Private Network's settings. Therefore, there is no risk of the scope of default route announcements automatically changing without your specific intervention, even after updating to new routing behavior.
 
-Your existing setup may be impacted by the new behavior if you want your custom routes to be scoped only to the next-hop resource's Private Network. In this case we recommend that you use [Network ACL rules](/vpc/reference-content/understanding-acls) via the VPC API to limit access to the custom route.
+Your existing setup may be impacted by the new behavior if you want your custom routes to be scoped only to the next-hop resource's Private Network. In this case, we recommend that you use [Network ACL rules](/vpc/reference-content/understanding-acls) via the VPC API to limit access to the custom route.
 
 ### Example use of NACLs to mitigate impact
 
-The example below shows how to achieve desired routing behavior for a custom route which is now advertised across the whole VPC.
+The example below shows how to achieve the desired routing behavior for a custom route which is now advertised across the whole VPC.
 
 #### Scenario