edits; removed unnecessary images

Author: KarlErickson

articles/spring-apps/enterprise/how-to-deploy-in-azure-virtual-network.md

@@ -157,14 +157,10 @@ Use the following steps to grant permission:
 
    :::image type="content" source="media/how-to-deploy-in-azure-virtual-network/access-control.png" alt-text="Screenshot of the Azure portal Access Control (IAM) page showing the Check access tab with the Add role assignment button highlighted." lightbox="media/how-to-deploy-in-azure-virtual-network/access-control.png":::
 
-1. Assign the `Network Contributor` and `User Access Administrator` roles to the Azure Spring Apps Resource Provider. For more information, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
+1. Assign the `Network Contributor` and `User Access Administrator` roles to the Azure Spring Cloud Resource Provider. For more information, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
 
    > [!NOTE]
    > Role `User Access Administrator` is in the **Privileged administrator roles** and `Network Contributor` is in the **Job function roles**.
-   > If you don't find Azure Spring Apps Resource Provider, search for *Azure Spring Cloud Resource Provider*.
-
-   :::image type="content" source="./media/how-to-deploy-in-azure-virtual-network/assign-user-assign-administrator-role.png" alt-text="Screenshot of the Azure portal Access Control page with assigning User Assign Administrator Role." lightbox="./media/how-to-deploy-in-azure-virtual-network/assign-user-assign-administrator-role.png":::
-   :::image type="content" source="./media/how-to-deploy-in-azure-virtual-network/assign-network-contributor-role.png" alt-text="Screenshot of the Azure portal Access Control page with assigning Network Contributor role." lightbox="./media/how-to-deploy-in-azure-virtual-network/assign-network-contributor-role.png":::
 
 ### [Azure CLI](#tab/azure-CLI)
 
@@ -294,11 +290,11 @@ If your custom subnets don't contain route tables, Azure Spring Apps creates the
 
 ### Route table requirements
 
-The route tables to which your custom vnet is associated must meet the following requirements:
+The route tables to which your custom virtual network is associated must meet the following requirements:
 
-* You can associate your Azure route tables with your vnet only when you create a new Azure Spring Apps service instance. You can't change to use another route table after Azure Spring Apps has been created.
+* You can associate your Azure route tables with your virtual network only when you create a new Azure Spring Apps service instance. You can't change to use another route table after you create an Azure Spring Apps instance.
 * Both the Spring application subnet and the service runtime subnet must associate with different route tables or neither of them.
-* Permissions must be assigned before instance creation. Be sure to grant Azure Spring Apps Resource Provider the `User Access Administrator` and `Network Contributor` permissions on your route tables.
+* Permissions must be assigned before instance creation. Be sure to grant Azure Spring Cloud Resource Provider the `User Access Administrator` and `Network Contributor` permissions on your route tables.
 * You can't update the associated route table resource after cluster creation. While you can't update the route table resource, you can modify custom rules on the route table.
 * You can't reuse a route table with multiple instances due to potential conflicting routing rules.
 
@@ -315,5 +311,5 @@ If your custom DNS server can't add Azure DNS IP `168.63.129.16` as the upstream
 
 ## Next steps
 
-* [Troubleshooting Azure Spring Apps in VNET](troubleshooting-vnet.md)
-* [Customer Responsibilities for Running Azure Spring Apps in VNET](vnet-customer-responsibilities.md)
+* [Troubleshooting Azure Spring Apps in virtual networks](troubleshooting-vnet.md)
+* [Customer responsibilities for Running Azure Spring Apps in a virtual network](vnet-customer-responsibilities.md)