First commit of italics-to-bold-3.

Author: JoshTheTechWriter

articles/spring-apps/basic-standard/how-to-write-log-to-custom-persistent-storage.md

@@ -21,10 +21,10 @@ This article shows you how to load Logback and write logs to custom persistent s
 
 > [!NOTE]
 > When a file in the application's classpath has one of the following names, Spring Boot will automatically load it over the default configuration for Logback:
-> - *logback-spring.xml*
-> - *logback.xml*
-> - *logback-spring.groovy*
-> - *logback.groovy*
+> - **logback-spring.xml**
+> - **logback.xml**
+> - **logback-spring.groovy**
+> - **logback.groovy**
 
 ## Prerequisites
 
@@ -140,7 +140,7 @@ In the preceding example, there are two placeholders named `{LOGS}` in the path
         --service <spring-instance-name>
    ```
 
-    Go to the Azure Storage Account resource you bound and find the Azure file share that was attached as persistent storage. In this example, the logs will be written to the *spring-boot-logger.log* file at the root of your Azure file share. All of the rotated log files will be stored in the */archived* folder in your Azure file share.
+    Go to the Azure Storage Account resource you bound and find the Azure file share that was attached as persistent storage. In this example, the logs will be written to the **spring-boot-logger.log** file at the root of your Azure file share. All of the rotated log files will be stored in the **/archived** folder in your Azure file share.
 
 1. Optionally, use the following command to update the path or persistent storage of an existing app:
 

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

@@ -60,7 +60,7 @@ Use the following steps to deploy the PlanetWeatherProvider project.
    az spring app create --name planet-weather-provider --runtime-version NetCore_31
    ```
 
-   To enable automatic service registration, you've given the app the same name as the value of `spring.application.name` in the project's *appsettings.json* file:
+   To enable automatic service registration, you've given the app the same name as the value of `spring.application.name` in the project's **appsettings.json** file:
 
    ```json
    "spring": {
@@ -78,14 +78,14 @@ Use the following steps to deploy the PlanetWeatherProvider project.
    cd steeltoe-sample/src/planet-weather-provider
    ```
 
-1. Create the binaries and the *.zip* file to be deployed.
+1. Create the binaries and the **.zip** file to be deployed.
 
    ```console
    dotnet publish -c release -o ./publish
    ```
 
    > [!TIP]
-   > The project file contains the following XML to package the binaries in a *.zip* file after writing them to the *./publish* folder:
+   > The project file contains the following XML to package the binaries in a **.zip** file after writing them to the **./publish** folder:
    >
    > ```xml
    > <Target Name="Publish-Zip" AfterTargets="Publish">
@@ -105,7 +105,7 @@ Use the following steps to deploy the PlanetWeatherProvider project.
        --artifact-path ./publish-deploy-planet.zip
    ```
 
-   The `--main-entry` option specifies the relative path from the *.zip* file's root folder to the *.dll* file that contains the application's entry point. After the service uploads the *.zip* file, it extracts all the files and folders, and then tries to execute the entry point in the specified *.dll* file.
+   The `--main-entry` option specifies the relative path from the **.zip** file's root folder to the **.dll** file that contains the application's entry point. After the service uploads the **.zip** file, it extracts all the files and folders, and then tries to execute the entry point in the specified **.dll** file.
 
    This command may take several minutes to run.
 
@@ -119,7 +119,7 @@ Use the following steps to deploy the SolarSystemWeather project.
    az spring app create --name solar-system-weather --runtime-version NetCore_31
    ```
 
-   `solar-system-weather` is the name that is specified in the `SolarSystemWeather` project's *appsettings.json* file.
+   `solar-system-weather` is the name that is specified in the `SolarSystemWeather` project's **appsettings.json** file.
 
    This command may take several minutes to run.
 
@@ -129,7 +129,7 @@ Use the following steps to deploy the SolarSystemWeather project.
    cd ../solar-system-weather
    ```
 
-1. Create the binaries and *.zip* file to be deployed.
+1. Create the binaries and **.zip** file to be deployed.
 
    ```console
    dotnet publish -c release -o ./publish
@@ -333,7 +333,7 @@ Compiling the project takes 5-10 minutes. When the project is compiled, you shou
 
 The following steps show you how to generate configurations and deploy to Azure Spring Apps:
 
-1. Go to the *spring-petclinic-customers-service* folder. Generate configurations by running the following command. If you've already signed-in with Azure CLI, the command automatically picks up the credentials. Otherwise, it signs you in using a prompt with instructions. For more information, see [Authentication](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication) on the [azure-maven-plugins](https://github.com/microsoft/azure-maven-plugins) wiki.
+1. Go to the **spring-petclinic-customers-service** folder. Generate configurations by running the following command. If you've already signed-in with Azure CLI, the command automatically picks up the credentials. Otherwise, it signs you in using a prompt with instructions. For more information, see [Authentication](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication) on the [azure-maven-plugins](https://github.com/microsoft/azure-maven-plugins) wiki.
 
    ```bash
    mvn com.microsoft.azure:azure-spring-apps-maven-plugin:1.19.0:config -DappName=customers-service
@@ -368,7 +368,7 @@ The following steps show you how to generate configurations and deploy to Azure
    mvn azure-spring-apps:deploy
    ```
 
-1. Go to the *spring-petclinic-api-gateway* folder. Run the following commands to generate the configuration and deploy `api-gateway`. Select **yes** for **Public endpoint**.
+1. Go to the **spring-petclinic-api-gateway** folder. Run the following commands to generate the configuration and deploy `api-gateway`. Select **yes** for **Public endpoint**.
 
    ```bash
    mvn com.microsoft.azure:azure-spring-apps-maven-plugin:1.19.0:config -DappName=api-gateway
@@ -396,7 +396,7 @@ To get the PetClinic app functioning with all sections like Admin Server, Visits
 - vets-service
 - visits-service
 
-Correct the app names in each *pom.xml* file for these modules, and then run the `deploy` command again.
+Correct the app names in each **pom.xml** file for these modules, and then run the `deploy` command again.
 
 #### [IntelliJ](#tab/IntelliJ)
 
@@ -408,7 +408,7 @@ Use the following steps to import the sample project in IntelliJ.
 
 1. Open the IntelliJ **Welcome** dialog and select **Import Project** to open the import wizard.
 
-1. Select the *spring-petclinic-microservices* folder.
+1. Select the **spring-petclinic-microservices** folder.
 
    :::image type="content" source="media/quickstart-deploy-apps/import-project-1-pet-clinic.png" alt-text="Screenshot of the IntelliJ import wizard that shows the PetClinic sample project." lightbox="media/quickstart-deploy-apps/import-project-1-pet-clinic.png":::
 
@@ -420,19 +420,19 @@ To deploy to Azure, you must sign in with your Azure account with Azure Toolkit
 
    :::image type="content" source="media/quickstart-deploy-apps/deploy-to-azure-1-pet-clinic.png" alt-text="Screenshot of the IntelliJ project explorer that shows the Deploy to Azure Spring Apps menu option." lightbox="media/quickstart-deploy-apps/deploy-to-azure-1-pet-clinic.png":::
 
-1. In the **Name** field, append *:api-gateway* to the existing **Name**.
-1. In the **Artifact** textbox, select *spring-petclinic-api-gateway-3.0.1*.
+1. In the **Name** field, append **:api-gateway** to the existing **Name**.
+1. In the **Artifact** textbox, select **spring-petclinic-api-gateway-3.0.1**.
 1. In the **Subscription** textbox, verify your subscription.
 1. In the **Spring Apps** textbox, select the instance of Azure Spring Apps that you created in [Provision Azure Spring Apps instance](./quickstart-provision-service-instance.md).
 1. In the **App:** textbox, select **Create app...**.
-1. Enter *api-gateway*, then select **OK**.
-1. Set **Public Endpoint** to *Enable*.
+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`.
 
    :::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":::
 
 1. In the **Before launch** section of the dialog, double-click **Run Maven Goal**.
-1. In the **Working directory** textbox, navigate to the *spring-petclinic-microservices/spring-petclinic-api-gateway* folder.
+1. In the **Working directory** textbox, navigate to the **spring-petclinic-microservices/spring-petclinic-api-gateway** folder.
 1. In the **Command line** textbox, enter *package -DskipTests*. Select **OK**.
 
    :::image type="content" source="media/quickstart-deploy-apps/deploy-to-azure-spring-apps-2-pet-clinic.png" alt-text="Screenshot of the IntelliJ Deploy to Azure dialog box with the Select Maven Goal section highlighted." lightbox="media/quickstart-deploy-apps/deploy-to-azure-spring-apps-2-pet-clinic.png":::
@@ -445,8 +445,8 @@ Repeat the previous steps to deploy `customers-service` and other Pet Clinic app
 
 1. Modify the **Name** and **Artifact** to identify the `customers-service` app.
 1. In the **App:** textbox, select **Create app...** to create `customers-service` app.
-1. Verify that the **Public Endpoint** option is set to *Disabled*.
-1. In the **Before launch** section of the dialog, switch the **Working directory** to the *petclinic/customers-service* folder.
+1. Verify that the **Public Endpoint** option is set to **Disabled**.
+1. In the **Before launch** section of the dialog, switch the **Working directory** to the **petclinic/customers-service** folder.
 1. Start the deployment by selecting the **Run** button at the bottom of the **Deploy Azure Spring Apps app** dialog.
 
 ## Verify the services

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

@@ -33,11 +33,11 @@ The Enterprise deployment plan includes the following Tanzu components:
 * An Azure subscription. If you don't have a subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 * Two dedicated subnets for the Azure Spring Apps cluster, one for the service runtime and another for the Spring applications. For subnet and virtual network requirements, see the [Virtual network requirements](how-to-deploy-in-azure-virtual-network.md#virtual-network-requirements) section of [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
 * An existing Log Analytics workspace for Azure Spring Apps diagnostics settings and a workspace-based Application Insights resource. For more information, see [Analyze logs and metrics with diagnostics settings](diagnostic-services.md) and [Application Insights Java In-Process Agent in Azure Spring Apps](how-to-application-insights.md).
-* Three internal Classless Inter-Domain Routing (CIDR) ranges (at least */16* each) that you've identified for use by the Azure Spring Apps cluster. These CIDR ranges won't be directly routable and will be used only internally by the Azure Spring Apps cluster. Clusters may not use *169.254.0.0/16*, *172.30.0.0/16*, *172.31.0.0/16*, or *192.0.2.0/24* for the internal Spring app CIDR ranges, or any IP ranges included within the cluster virtual network address range.
+* Three internal Classless Inter-Domain Routing (CIDR) ranges (at least `/16` each) that you've identified for use by the Azure Spring Apps cluster. These CIDR ranges won't be directly routable and will be used only internally by the Azure Spring Apps cluster. Clusters may not use `169.254.0.0/16`, `172.30.0.0/16`, `172.31.0.0/16`, or `192.0.2.0/24` for the internal Spring app CIDR ranges, or any IP ranges included within the cluster virtual network address range.
 * Service permission granted to the virtual network. The Azure Spring Apps Resource Provider requires `User Access Administrator` and `Network Contributor` permissions to your virtual network in order to grant a dedicated and dynamic service principal on the virtual network for further deployment and maintenance. For instructions and more information, see the [Grant service permission to the virtual network](how-to-deploy-in-azure-virtual-network.md#grant-service-permission-to-the-virtual-network) section of [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
 * If you're using Azure Firewall or a Network Virtual Appliance (NVA), you'll also need to satisfy the following prerequisites:
   * Network and fully qualified domain name (FQDN) rules. For more information, see [Virtual network requirements](how-to-deploy-in-azure-virtual-network.md#virtual-network-requirements).
-  * A unique User Defined Route (UDR) applied to each of the service runtime and Spring application subnets. For more information about UDRs, see [Virtual network traffic routing](../../virtual-network/virtual-networks-udr-overview.md). The UDR should be configured with a route for *0.0.0.0/0* with a destination of your NVA before deploying the Azure Spring Apps cluster. For more information, see the [Bring your own route table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table) section of [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
+  * A unique User Defined Route (UDR) applied to each of the service runtime and Spring application subnets. For more information about UDRs, see [Virtual network traffic routing](../../virtual-network/virtual-networks-udr-overview.md). The UDR should be configured with a route for `0.0.0.0/0` with a destination of your NVA before deploying the Azure Spring Apps cluster. For more information, see the [Bring your own route table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table) section of [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
 * [Azure CLI](/cli/azure/install-azure-cli)
 * If you're deploying an Azure Spring Apps Enterprise plan instance for the first time in the target subscription, see the [Requirements](../enterprise/how-to-enterprise-marketplace-offer.md#requirements) section of [Enterprise plan in Azure Marketplace](../enterprise/how-to-enterprise-marketplace-offer.md).
 
@@ -119,12 +119,12 @@ To deploy the Azure Spring Apps cluster using the Azure CLI script, follow these
    * The Azure location name that you saved earlier.
    * The name of the resource group that you created earlier.
    * The name of the virtual network resource group where you'll deploy your resources.
-   * The name of the spoke virtual network (for example, *vnet-spoke*).
-   * The name of the subnet to be used by the Azure Spring Apps Application Service (for example, *snet-app*).
-   * The name of the subnet to be used by the Azure Spring Apps Runtime Service (for example, *snet-runtime*).
+   * The name of the spoke virtual network (for example, **vnet-spoke**).
+   * The name of the subnet to be used by the Azure Spring Apps Application Service (for example, **snet-app**).
+   * The name of the subnet to be used by the Azure Spring Apps Runtime Service (for example, **snet-runtime**).
    * The name of the resource group for the Azure Log Analytics workspace to be used for storing diagnostic logs.
-   * The name of the Azure Log Analytics workspace (for example, *la-cb5sqq6574o2a*).
-   * The CIDR ranges from your virtual network to be used by Azure Spring Apps (for example, *XX.X.X.X/16,XX.X.X.X/16,XX.X.X.X/16*).
+   * The name of the Azure Log Analytics workspace (for example, **la-cb5sqq6574o2a**).
+   * The CIDR ranges from your virtual network to be used by Azure Spring Apps (for example, **XX.X.X.X/16,XX.X.X.X/16,XX.X.X.X/16**).
    * The key/value pairs to be applied as tags on all resources that support tags. For more information, see [Use tags to organize your Azure resources and management hierarchy](../../azure-resource-manager/management/tag-resources.md). Use a space-separated list to apply multiple tags (for example, *environment=Dev BusinessUnit=finance*).
 
 After you provide this information, the script will create and deploy the Azure resources.