edits

Author: KarlErickson

articles/spring-apps/includes/quickstart-deploy-microservice-apps/clean-up-resources.md

@@ -9,7 +9,7 @@ ms.date: 05/24/2022
 <!--
 For clarity of structure, a separate markdown file is used to describe how to clean up resources using Azure Portal or AZD.
 
-[!INCLUDE [clean-up-resources-portal-or-azd](includes/quickstart-deploy-microservice-apps/clean-up-resources.md)]
+[!INCLUDE [clean-up-resources](includes/quickstart-deploy-microservice-apps/clean-up-resources.md)]
 
 -->
 

articles/spring-apps/includes/quickstart-deploy-microservice-apps/deploy-microservice-apps-with-basic-standard-plan.md

@@ -3,7 +3,7 @@ author: KarlErickson
 ms.author: v-shilichen
 ms.service: spring-apps
 ms.topic: include
-ms.date: 01/03/2024
+ms.date: 01/10/2024
 ---
 
 <!--
@@ -23,7 +23,7 @@ For clarity of structure, a separate markdown file is used to describe how to de
 
 Use the following steps to initialize the Pet Clinic application using Azure Developer CLI templates:
 
-1. Open a terminal, create a new, empty folder, and then navigate to it.
+1. In the Bash window, create a new, empty folder and then navigate to it.
 
 1. Use the following command to initialize the project:
 
@@ -84,7 +84,7 @@ Use the following steps to create the service instance:
    | **Name**           | *myasa*                           | A unique name that identifies your Azure Spring Apps instance. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number. |
    | **Plan**           | **Standard**                      | The pricing plan determines the resources and cost associated with your instance.                                                                                                                                                                                                                   |
    | **Region**         | The region closest to your users. | The location that is closest to your users.                                                                                                                                                                                                                                                         |
-   | **Zone Redundant** | Unchecked                         | Creates your Azure Spring Apps service in an Azure availability zone. Not currently supported in all regions.                                                                                                                                                                                       |
+   | **Zone Redundant** | Unselected                        | Creates your Azure Spring Apps service in an Azure availability zone. Not currently supported in all regions.                                                                                                                                                                                       |
 
 1. Navigate to the **Diagnostic settings** tab on the **Create Azure Spring Apps** page and then select **Create new** to create a new Log Analytics workspaces instance. On the **Create new Log Analytics workspace** page, update the name of the **Log Analytics workspace** as needed, and then select **OK** to confirm the creation.
 
@@ -104,7 +104,7 @@ Use the following steps to create the service instance:
 
 1. Select **Config Server** in the navigation pane.
 
-1. On the **Config Server** page, for **URI**, enter *`https://github.com/Azure-Samples/spring-petclinic-microservices-config.git`*, and then select **Validate**.
+1. On the **Config Server** page, for **URI**, enter *https://github.com/Azure-Samples/spring-petclinic-microservices-config.git* and then select **Validate**.
 
    :::image type="content" source="../../media/quickstart-deploy-microservice-apps/validate-config-server.png" alt-text="Screenshot of the Azure portal that shows the Config Server page with the Default URI and the Validate button highlighted and the Apply button disabled." lightbox="../../media/quickstart-deploy-microservice-apps/validate-config-server.png":::
 
@@ -122,7 +122,7 @@ Use the following steps to create the required resources:
 
    The console outputs messages similar to the following example:
 
-   ```text
+   ```output
    Logged in to Azure.
    ```
 
@@ -158,7 +158,7 @@ You can now deploy the app to Azure Spring Apps.
 
 Use the following steps to deploy the microservice applications using the [Maven plugin for Azure Spring Apps](https://github.com/microsoft/azure-maven-plugins/wiki/Azure-Spring-Apps):
 
-1. Navigate to the sample project directory and use the following command to configure the apps for Azure Spring Apps:
+1. Navigate to the sample project directory and then use the following command to configure the apps for Azure Spring Apps:
 
    ```bash
    ./mvnw -P spring-apps com.microsoft.azure:azure-spring-apps-maven-plugin:1.17.0:config
@@ -184,7 +184,7 @@ Use the following steps to deploy the microservice applications using the [Maven
    > [!NOTE]
    > Deployment to Azure Spring Apps can take up to 25 minutes.
 
-After the command is executed, a log displays output similar to the following example, which indicates that all deployments are successful:
+After the command runs, a log displays output similar to the following example, which indicates that all deployments are successful:
 
 ```output
 [INFO] Deployment(default) is successfully updated.

articles/spring-apps/includes/quickstart-deploy-microservice-apps/deploy-microservice-apps-with-enterprise-plan.md

@@ -3,7 +3,7 @@ author: KarlErickson
 ms.author: v-shilichen
 ms.service: spring-apps
 ms.topic: include
-ms.date: 01/03/2024
+ms.date: 01/10/2024
 ---
 
 <!--
@@ -29,27 +29,27 @@ Use the following steps to prepare the project and run the sample locally:
    git clone https://github.com/Azure-Samples/spring-petclinic-microservices.git
    ```
 
-1. Enter the project root directory and use the following command to build the project:
+1. Navigate to the project root directory and then use the following command to build the project:
 
    ```bash
    ./mvnw clean package -DskipTests
    ```
 
 Use the following steps if you want to run the application locally. Otherwise, you can skip these steps.
 
-1. Open a terminal and use the following command to start Config Server:
+1. Open a new Bash window and then use the following command to start Config Server:
 
    ```bash
    ./mvnw spring-boot:run -pl spring-petclinic-config-server
    ```
 
-1. Open a terminal and use the following command to start Discovery Server:
+1. Open a new Bash window and then use the following command to start Discovery Server:
 
    ```bash
    ./mvnw spring-boot:run -pl spring-petclinic-discovery-server
    ```
 
-1. For the Customers, Veterinarians, Visits, and Spring Cloud Gateway services, open new terminal and use the following commands to start the services:
+1. For the Customers, Vets, Visits, and Spring Cloud Gateway services, open a new Bash window and use the following commands to start the services:
 
    ```bash
    ./mvnw spring-boot:run -pl spring-petclinic-customers-service
@@ -59,7 +59,7 @@ Use the following steps if you want to run the application locally. Otherwise, y
        -pl spring-petclinic-api-gateway
    ```
 
-1. Open a new terminal and enter the project `spring-petclinic-frontend` directory. Use the following commands to install dependencies and run the front end application:
+1. Open a new Bash window and navigate to the project `spring-petclinic-frontend` directory. Use the following commands to install dependencies and run the frontend application:
 
    ```bash
    npm install
@@ -98,7 +98,7 @@ Use the following steps to create all the Azure resources that the app depends o
    | **Resource group** | *myresourcegroup*                 | A new resource group name or an existing one from your subscription.                                                                                                        |
    | **Region**         | The region closest to your users. | The region is used to create the resource group.                                                                                                                            |
 
-   :::image type="content" source="../../media/quickstart-deploy-microservice-apps/custom-deployment-microservice.png" alt-text="Screenshot of the Azure portal that shows the custom deployment for microservice." lightbox="../../media/quickstart-deploy-microservice-apps/custom-deployment-microservice.png":::
+   :::image type="content" source="../../media/quickstart-deploy-microservice-apps/custom-deployment-microservice.png" alt-text="Screenshot of the Azure portal that shows the Custom deployment page." lightbox="../../media/quickstart-deploy-microservice-apps/custom-deployment-microservice.png":::
 
 1. Select **Review and Create** to review your selections. Then, select **Create** to deploy the app to Azure Spring Apps.
 
@@ -120,15 +120,15 @@ The **Deploy to Azure** button in the previous section launches an Azure portal
 
 ### [Azure portal + Maven plugin](#tab/Azure-portal-maven-plugin-ent)
 
-[!INCLUDE [deploy-spring-apps-maven-plugin](microservice-spring-apps-maven-plugin.md)]
+[!INCLUDE [microservice-spring-apps-maven-plugin](microservice-spring-apps-maven-plugin.md)]
 
-2. Use the following command to deploy the back end applications:
+2. Use the following command to deploy the backend applications:
 
    ```bash
    ./mvnw azure-spring-apps:deploy
    ```
 
-   After the command is executed, you can see from the following log messages that the deployment was successful:
+   After the command runs, you can see from the following log messages that the deployment was successful:
 
    ```output
    [INFO] Start deploying artifact(customers-service-3.0.1.jar) to deployment(default) of app(customers-service)...
@@ -151,7 +151,7 @@ The **Deploy to Azure** button in the previous section launches an Azure portal
    [INFO] Deployment Status: Running
    ```
 
-2. The Azure portal doesn't support deploying the front end applications, so use the following Azure CLI command to deploy the front end application:
+1. The Azure portal doesn't support deploying the frontend applications, so use the following Azure CLI command to deploy the frontend application:
 
    ```azurecli
    az spring app deploy \
@@ -163,7 +163,7 @@ The **Deploy to Azure** button in the previous section launches an Azure portal
        --builder ${APP_FRONTEND}
    ```
 
-   After the command is executed, you can see from the following log messages that the deployment was successful:
+   After the command runs, you can see from the following log messages that the deployment was successful:
 
    ```output
    [5/5] Updating deployment in app "frontend" (this operation can take a while to complete)

articles/spring-apps/includes/quickstart-deploy-microservice-apps/microservice-spring-apps-maven-plugin.md

@@ -2,9 +2,8 @@
 author: karlerickson
 ms.author: v-shilichen
 ms.service: spring-apps
-ms.custom: event-tier1-build-2022
 ms.topic: include
-ms.date: 01/03/2024
+ms.date: 01/10/2024
 ---
 
 <!--
@@ -15,7 +14,7 @@ Use the following line at the end of the heading Prerequisites, with blank lines
 
 Use the following steps to deploy using the [Maven plugin for Azure Spring Apps](https://github.com/microsoft/azure-maven-plugins/wiki/Azure-Spring-Apps):
 
-1. Navigate to the project root directory, and then run the following command to configure the apps in Azure Spring Apps:
+1. Navigate to the project root directory and then run the following command to configure the apps in Azure Spring Apps:
 
    ```bash
    ./mvnw -P spring-apps-enterprise com.microsoft.azure:azure-spring-apps-maven-plugin:1.19.0:config

articles/spring-apps/includes/quickstart-deploy-microservice-apps/prepare-spring-project.md

@@ -3,7 +3,7 @@ author: KarlErickson
 ms.author: v-shilichen
 ms.service: spring-apps
 ms.topic: include
-ms.date: 01/03/2024
+ms.date: 01/10/2024
 ---
 
 <!--
@@ -15,16 +15,15 @@ For clarity of structure, a separate markdown file is used to describe how to pr
 
 Use the following steps to prepare the sample locally:
 
-1. The sample project is ready on GitHub. Clone the sample project by using the following command:
+1. Clone the sample project by using the following command:
 
    ```bash
    git clone https://github.com/Azure-Samples/spring-petclinic-microservices.git
    ```
 
-1. Use the following command to change directory to the sample root path and then run the sample project locally:
+1. Navigate to the project root directory and then use the following command to run the sample project locally:
 
    ```bash
-   cd spring-petclinic-microservices
    bash ./scripts/run_all_without_infra.sh
    ```