Merge pull request #296853 from JoshTheTechWriter/seventh-batch-of-files

Round 7 of formatting edits

Author: JamesJBarnett

articles/spring-apps/basic-standard/how-to-connect-to-app-instance-for-troubleshooting.md

@@ -203,7 +203,7 @@ The following list shows the tools available, which depend on your service plan
 - Custom image deployment: Depends on the installed tool set in your image.
 
 > [!NOTE]
-> JDK tools aren't included in the path for the *source code* deployment type. Run `export PATH="$PATH:/layers/tanzu-buildpacks_microsoft-openjdk/jdk/bin"` before running any JDK commands.
+> JDK tools aren't included in the path for the source code deployment type. Run `export PATH="$PATH:/layers/tanzu-buildpacks_microsoft-openjdk/jdk/bin"` before running any JDK commands.
 
 ## Limitations
 

articles/spring-apps/basic-standard/how-to-enable-system-assigned-managed-identity.md

@@ -71,7 +71,7 @@ az spring app create \
     --system-assigned
 ```
 
-### Enable system-assigned managed identity on an existing app**
+### Enable system-assigned managed identity on an existing app
 
 Use `az spring app identity assign` command to enable the system-assigned identity on an existing app.
 

articles/spring-apps/basic-standard/how-to-fix-app-restart-issues-caused-by-out-of-memory.md

@@ -41,7 +41,7 @@ The **Resource health** page on the Azure portal shows app restart events due to
 
 ### Configure memory size
 
-The metrics *App memory Usage*, `jvm.memory.used`, and `jvm.memory.committed` provide a view of memory usage. For more information, see the [Metrics](tools-to-troubleshoot-memory-issues.md#metrics) section of [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md). Configure the maximum memory sizes in JVM options to ensure that memory is under the limit.
+The metrics `App memory usage`, `jvm.memory.used`, and `jvm.memory.committed` provide a view of memory usage. For more information, see the [Metrics](tools-to-troubleshoot-memory-issues.md#metrics) section of [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md). Configure the maximum memory sizes in JVM options to ensure that memory is under the limit.
 
 The sum of the maximum memory sizes of all the parts in the [Java memory model](concepts-for-java-memory-management.md#java-memory-model) should be less than the real available app memory. To set your maximum memory sizes, see the typical memory layout described in the [Memory usage layout](concepts-for-java-memory-management.md#memory-usage-layout) section of [Java memory management](concepts-for-java-memory-management.md).
 

articles/spring-apps/basic-standard/how-to-github-actions.md

@@ -63,7 +63,7 @@ This example uses the [steeltoe sample on GitHub](https://github.com/Azure-Sampl
 
 :::image type="content" source="media/how-to-github-actions/actions1.png" alt-text="Screenshot of the GitHub Actions secrets and variables page with the New repository secret button highlighted." lightbox="media/how-to-github-actions/actions1.png":::
 
-Set the secret name to `AZURE_CREDENTIALS` and its value to the JSON string that you found under the heading *Set up your GitHub repository and authenticate*.
+Set the secret name to `AZURE_CREDENTIALS` and its value to the JSON string that you found under the heading **Set up your GitHub repository and authenticate**.
 
 :::image type="content" source="media/how-to-github-actions/actions2.png" alt-text="Screenshot of the GitHub Actions secrets / New secret page." lightbox="media/how-to-github-actions/actions2.png":::
 
@@ -206,7 +206,7 @@ This example uses the [PiggyMetrics](https://github.com/Azure-Samples/piggymetri
 
 :::image type="content" source="media/how-to-github-actions/actions1.png" alt-text="Screenshot of the GitHub Actions secrets and variables page with the New repository secret button highlighted." lightbox="media/how-to-github-actions/actions1.png":::
 
-Set the secret name to `AZURE_CREDENTIALS` and its value to the JSON string that you found under the heading *Set up your GitHub repository and authenticate*.
+Set the secret name to `AZURE_CREDENTIALS` and its value to the JSON string that you found under the heading **Set up your GitHub repository and authenticate**.
 
 :::image type="content" source="media/how-to-github-actions/actions2.png" alt-text="Screenshot of the GitHub Actions secrets / New secret page." lightbox="media/how-to-github-actions/actions2.png":::
 

articles/spring-apps/basic-standard/how-to-maven-deploy-apps.md

@@ -116,7 +116,7 @@ To generate configurations and deploy the app, follow these steps:
 
    * **Subscription ID** - the subscription you used to create an Azure Spring Apps instance.
    * **Service instance** - the name of your Azure Spring Apps instance.
-   * **App name** - an app name of your choice, or use the default value `artifactId`.
+   * **App name** - an app name of your choice, or use the default value **artifactId**.
    * **Public endpoint** - **true** to expose the app to public access; otherwise, **false**.
 
 1. Verify that the `appName` element in the POM file has the correct value. The relevant portion of the POM file should look similar to the following example.

articles/spring-apps/basic-standard/how-to-migrate-standard-tier-to-enterprise-tier.md

@@ -156,10 +156,10 @@ Follow these steps to use Application Configuration Service for Tanzu as a centr
 
 1. Select **Settings** and complete the form in **Repositories** to add a new entry with the following information:
 
-   - Name: `default`
-   - Patterns: `api-gateway,customers-service`
-   - URI: `https://github.com/Azure-Samples/spring-petclinic-microservices-config`
-   - Label: `master`
+   - Name: **default**
+   - Patterns: **api-gateway,customers-service**
+   - URI: **https://github.com/Azure-Samples/spring-petclinic-microservices-config**
+   - Label: **master**
 
    :::image type="content" source="./media/how-to-migrate-standard-tier-to-enterprise-tier/config-service-settings.png" alt-text="Screenshot of the Azure portal showing the Settings tab of the Application Configuration Service page." lightbox="./media/how-to-migrate-standard-tier-to-enterprise-tier/config-service-settings.png":::
 

articles/spring-apps/basic-standard/how-to-use-grpc.md

@@ -245,7 +245,7 @@ public class CustomersServiceImpl extends CustomersServiceGrpc.CustomersServiceI
 
 ## Configure the server port
 
-Next, configure the server port to `1025` for the Basic/Standard plan or to `8080` for the Enterprise plan so that the ingress rule works correctly. Add the following line to the **application.properties** file in the **spring-petclinic-customers-service/src/main/resources** folder.
+Next, configure the server port to **1025** for the Basic/Standard plan or to **8080** for the Enterprise plan so that the ingress rule works correctly. Add the following line to the **application.properties** file in the **spring-petclinic-customers-service/src/main/resources** folder.
 
 ```properties
 grpc.server.port=1025

articles/spring-apps/basic-standard/includes/quickstart-deploy-microservice-apps/prepare-spring-project-enterprise-plan.md

@@ -51,7 +51,7 @@ Use the following steps if you want to run the application locally. Otherwise, y
        -pl spring-petclinic-api-gateway
    ```
 
-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:
+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

articles/spring-apps/basic-standard/quickstart-deploy-apps.md

@@ -72,7 +72,7 @@ Use the following steps to deploy the PlanetWeatherProvider project.
 
    This command may take several minutes to run.
 
-1. Change directory to the `PlanetWeatherProvider` project folder.
+1. Change directory to the **PlanetWeatherProvider** project folder.
 
    ```console
    cd steeltoe-sample/src/planet-weather-provider
@@ -427,7 +427,7 @@ To deploy to Azure, you must sign in with your Azure account with Azure Toolkit
 1. In the **App:** textbox, select **Create app...**.
 1. Enter **api-gateway**, then select **OK**.
 1. Set **Public Endpoint** to **Enable**.
-1. Set **Memory** to `2.0Gi` and **JVM options** to `-Xms2048m -Xmx2048m`.
+1. Set **Memory** to **2.0Gi** and **JVM options** to **-Xms2048m -Xmx2048m**.
 
    :::image type="content" source="media/quickstart-deploy-apps/memory-jvm-options.png" alt-text="Screenshot of the IntelliJ Create Azure Spring App dialog box that shows Memory and JVM options controls." lightbox="media/quickstart-deploy-apps/memory-jvm-options.png":::
 

articles/spring-apps/basic-standard/quickstart-deploy-infrastructure-vnet-bicep.md

@@ -62,8 +62,8 @@ Next, open a Bash window and run the following Azure CLI command, replacing the
 * `springCloudInstanceName`: The name of the Azure Spring Apps resource.
 * `appInsightsName`: The name of the Application Insights instance for Azure Spring Apps.
 * `laWorkspaceResourceId`: The resource ID of the existing Log Analytics workspace (for example, **/subscriptions/\<your subscription>/resourcegroups/\<your Log Analytics resource group>/providers/Microsoft.OperationalInsights/workspaces/\<your Log Analytics workspace name>**).
-* **springCloudAppSubnetID:** The resource ID of the Azure Spring Apps Application Subnet.
-* **springCloudRuntimeSubnetID:** The resource ID of the Azure Spring Apps Runtime Subnet.
+* `springCloudAppSubnetID`: The resource ID of the Azure Spring Apps Application Subnet.
+* `springCloudRuntimeSubnetID`: The resource ID of the Azure Spring Apps Runtime Subnet.
 * `springCloudServiceCidrs`: A comma-separated list of IP address ranges (three in total) in CIDR format. The IP ranges are reserved to host underlying Azure Spring Apps infrastructure. These three ranges should be at least `/16` unused IP ranges, and must not overlap with any routable subnet IP ranges used within the network.
 
   ```azurecli