Acrolinx fixes

Author: KarlErickson

articles/spring-apps/concept-outbound-type.md

@@ -20,12 +20,12 @@ ms.custom: devx-track-java, engagement-fy23
 
 This article describes how to customize an instance's egress route to support custom network scenarios. For example, you might want to customize an instance's egress route for networks that disallow public IPs and require the instance to sit behind a network virtual appliance (NVA).
 
-By default, Azure Spring Apps provisions a Standard SKU Load Balancer that you can set up and use for egress. However, the default setup may not meet the requirements of all scenarios. For example, public IPs may not be allowed, or more hops may be required for egress. When you use this feature to customize egress, Azure Spring Apps won't create public IP resources.
+By default, Azure Spring Apps provisions a Standard SKU Load Balancer that you can set up and use for egress. However, the default setup may not meet the requirements of all scenarios. For example, public IPs may not be allowed, or more hops may be required for egress. When you use this feature to customize egress, Azure Spring Apps doesn't create public IP resources.
 
 ## Prerequisites
 
 - All prerequisites for deploying Azure Spring Apps in a virtual network. For more information, see [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
-- An API version of *2022-09-01 preview* or greater.
+- An API version of `2022-09-01 preview` or greater.
 - [Azure CLI version 1.1.7 or later](/cli/azure/install-azure-cli).
 
 ## Limitations
@@ -47,7 +47,7 @@ The default `outboundType` value is `loadBalancer`. If `outboundType` is set to
 > [!NOTE]
 > Using an outbound type is an advanced networking scenario and requires proper network configuration.
 
-If `outboundType` is set to `userDefinedRouting`, Azure Spring Apps won't automatically configure egress paths. You must set up egress paths yourself. You could still find two load balancers in your resource group. They're only used for internal traffic and won't expose any public IP. You must prepare two route tables associated with two subnets: one to service the runtime and another for the user app.
+If `outboundType` is set to `userDefinedRouting`, Azure Spring Apps doesn't automatically configure egress paths. You must set up egress paths yourself. You could still find two load balancers in your resource group. They're only used for internal traffic and don't expose any public IP. You must prepare two route tables associated with two subnets: one to service the runtime and another for the user app.
 
 > [!IMPORTANT]
 > An `outboundType` of `userDefinedRouting` requires a route for `0.0.0.0/0` and the next hop destination of a network virtual appliance in the route table. For more information, see [Customer responsibilities for running Azure Spring Apps in a virtual network](vnet-customer-responsibilities.md).

articles/spring-apps/how-to-create-user-defined-route-instance.md

@@ -37,7 +37,7 @@ This diagram illustrates the following features of the architecture:
 
 - Public ingress traffic must flow through firewall filters.
 - Each Azure Spring Apps instance is isolated within a dedicated subnet.
-- The firewall is owned and managed by customers.
+- Customers own and manage the firewall.
 - This structure ensures that the firewall enables a healthy environment for all the functions you need.
 - Azure Spring Apps doesn't automatically generate public IP resources.