Merge pull request #293855 from JoshTheTechWriter/italics-to-bold-2

Second PR for italics to bold bulk updates

Author: AnnaMHuff

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

@@ -72,16 +72,16 @@ If you already have a virtual network to host an Azure Spring Apps instance, ski
    |-----------------|--------------------------------------------------|
    | Subscription    | Select your subscription.                        |
    | Resource group  | Select your resource group, or create a new one. |
-   | Name            | Enter *azure-spring-apps-vnet*.                  |
+   | Name            | Enter **azure-spring-apps-vnet**.                  |
    | Location        | Select **East US**.                              |
 
 1. Select **Next: IP Addresses**.
 
-1. For the IPv4 address space, enter *10.1.0.0/16*.
+1. For the IPv4 address space, enter **10.1.0.0/16**.
 
-1. Select **Add subnet**. Then enter *service-runtime-subnet* for **Subnet name** and enter *10.1.0.0/24* for **Subnet address range**. Then select **Add**.
+1. Select **Add subnet**. Then enter **service-runtime-subnet** for **Subnet name** and enter **10.1.0.0/24** for **Subnet address range**. Then select **Add**.
 
-1. Select **Add subnet** again, and then enter the subnet name and subnet address range. For example, enter *apps-subnet* and *10.1.1.0/24*. Then select **Add**.
+1. Select **Add subnet** again, and then enter the subnet name and subnet address range. For example, enter **apps-subnet** and **10.1.1.0/24**. Then select **Add**.
 
 1. Select **Review + create**. Leave the rest as defaults, and select **Create**.
 
@@ -258,7 +258,7 @@ Those network resources are connected to your virtual network created in the pre
 :::image type="content" source="./media/how-to-deploy-in-azure-virtual-network/vnet-with-connected-device.png" alt-text="Screenshot of the Azure portal showing the Connected devices page for a virtual network." lightbox="./media/how-to-deploy-in-azure-virtual-network/vnet-with-connected-device.png":::
 
 > [!IMPORTANT]
-> The resource groups are fully managed by the Azure Spring Apps service. Do *not* manually delete or modify any resource inside.
+> The resource groups are fully managed by the Azure Spring Apps service. Do not manually delete or modify any resource inside.
 
 ## Using smaller subnet ranges
 

articles/spring-apps/basic-standard/how-to-deploy-with-custom-container-image.md

@@ -81,7 +81,7 @@ To disable listening on a port for images that aren't web applications, add the
 
    :::image type="content" source="media/how-to-deploy-with-custom-container-image/create-app-custom-container.png" alt-text="Screenshot of Azure portal Create App page with Runtime platform dropdown showing and Custom Container selected." lightbox="media/how-to-deploy-with-custom-container-image/create-app-custom-container.png":::
 
-1. Select **Edit** under *Image*, then fill in the fields as shown in the following image:
+1. Select **Edit** under **Image**, then fill in the fields as shown in the following image:
 
    :::image type="content" source="media/how-to-deploy-with-custom-container-image/custom-image-settings.png" alt-text="Screenshot of Azure portal that shows the Custom Image Settings pane." lightbox="media/how-to-deploy-with-custom-container-image/custom-image-settings.png":::
 
@@ -142,15 +142,15 @@ The following points will help you address common situations when deploying with
 
 There are two options to trust a Certificate Authority:
 
-**Option 1: Upload via Azure Spring Apps**
+Option 1: Upload via Azure Spring Apps
 
-To load the CA certs into your apps, see [Use TLS/SSL certificates in your application in Azure Spring Apps](how-to-use-tls-certificate.md). Then the certs will be mounted into the location */etc/azure-spring-cloud/certs/public/*.
+To load the CA certs into your apps, see [Use TLS/SSL certificates in your application in Azure Spring Apps](how-to-use-tls-certificate.md). Then the certs will be mounted into the location **/etc/azure-spring-cloud/certs/public/**.
 
-**Option 2: Manual installation in the image**
+Option 2: Manual installation in the image
 
 To trust a CA in the image, set the following variables depending on your environment:
 
-* You must import Java applications into the trust store by adding the following lines into your *Dockerfile*:
+* You must import Java applications into the trust store by adding the following lines into your **Dockerfile**:
 
   ```dockerfile
   ADD EnterpriseRootCA.crt /opt/
@@ -191,9 +191,9 @@ If you deployed the instance to a VNet, make sure you allow the network traffic
 
 ### Install an APM into the image manually
 
-The installation steps vary on different application performance monitors (APMs) and languages. The following steps are for New Relic with Java applications. You must modify the *Dockerfile* using the following steps:
+The installation steps vary on different application performance monitors (APMs) and languages. The following steps are for New Relic with Java applications. You must modify the **Dockerfile** using the following steps:
 
-1. Download and install the agent file into the image by adding the following to the *Dockerfile*:
+1. Download and install the agent file into the image by adding the following to the **Dockerfile**:
 
    ```dockerfile
    ADD newrelic-agent.jar /opt/agents/newrelic/java/newrelic-agent.jar

articles/spring-apps/basic-standard/how-to-dynatrace-one-agent-monitor.md

@@ -43,7 +43,7 @@ The following sections describe how to activate Dynatrace OneAgent.
 ### Prepare your Azure Spring Apps environment
 
 1. Create an instance of Azure Spring Apps.
-1. Create an application that you want to report to Dynatrace by running the following command. Replace the placeholders *\<...>* with your own values.
+1. Create an application that you want to report to Dynatrace by running the following command. Replace the placeholders `<...>` with your own values.
    ```azurecli
    az spring app create \
        --resource-group <your-resource-group-name> \
@@ -64,7 +64,7 @@ You can add the environment variable key/value pairs to your application using e
 
 #### Option 1: Azure CLI
 
-To add the key/value pairs using the Azure CLI, run the following command, replacing the placeholders *\<...>* with the values determined in the previous steps.
+To add the key/value pairs using the Azure CLI, run the following command, replacing the placeholders `<...>` with the values determined in the previous steps.
 
 ```azurecli
 az spring app deploy \
@@ -98,7 +98,7 @@ Using Terraform, Bicep, or Azure Resource Manager template (ARM template), you c
 
 ### Automate provisioning using Terraform
 
-To configure the environment variables in a Terraform template, add the following code to the template, replacing the *\<...>* placeholders with your own values. For more information, see [Manages an Active Azure Spring Apps Deployment](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/spring_cloud_active_deployment).
+To configure the environment variables in a Terraform template, add the following code to the template, replacing the `<...>` placeholders with your own values. For more information, see [Manages an Active Azure Spring Apps Deployment](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/spring_cloud_active_deployment).
 
 ```terraform
 environment_variables = {
@@ -111,7 +111,7 @@ environment_variables = {
 
 ### Automate provisioning using a Bicep file
 
-To configure the environment variables in a Bicep file, add the following code to the file, replacing the *\<...>* placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=bicep).
+To configure the environment variables in a Bicep file, add the following code to the file, replacing the `<...>` placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=bicep).
 
 ```bicep
 environmentVariables: {
@@ -124,7 +124,7 @@ environmentVariables: {
 
 ### Automate provisioning using an ARM template
 
-To configure the environment variables in an ARM template, add the following code to the template, replacing the *\<...>* placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=json).
+To configure the environment variables in an ARM template, add the following code to the template, replacing the `<...>` placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=json).
 
 ```json
 "environmentVariables": {

articles/spring-apps/basic-standard/how-to-elastic-apm-java-agent-monitor.md

@@ -89,7 +89,7 @@ Before proceeding, you need your Elastic APM server connectivity information han
 
    :::image type="content" source="media/how-to-elastic-apm-java-agent-monitor/upload-files-microsoft-azure.png" alt-text="Screenshot of the Azure portal that shows the Upload files pane of the File share page." lightbox="media/how-to-elastic-apm-java-agent-monitor/upload-files-microsoft-azure.png":::
 
-1. After you have the Elastic APM endpoint and secret token, use the following command to activate Elastic APM Java agent when deploying applications. The placeholder *`<agent-location>`* refers to the mounted storage location of the Elastic APM Java Agent.
+1. After you have the Elastic APM endpoint and secret token, use the following command to activate Elastic APM Java agent when deploying applications. The placeholder `<agent-location>` refers to the mounted storage location of the Elastic APM Java Agent.
 
    ```azurecli
    az spring app deploy \
@@ -108,7 +108,7 @@ You can also run a provisioning automation pipeline using Terraform, Bicep, or a
 
 ### Automate provisioning using Terraform
 
-To configure the environment variables in a Terraform template, add the following code to the template, replacing the *\<...>* placeholders with your own values. For more information, see [Manages an Active Azure Spring Apps Deployment](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/spring_cloud_active_deployment).
+To configure the environment variables in a Terraform template, add the following code to the template, replacing the `<...>` placeholders with your own values. For more information, see [Manages an Active Azure Spring Apps Deployment](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/spring_cloud_active_deployment).
 
 ```terraform
 resource "azurerm_spring_cloud_java_deployment" "example" {
@@ -126,7 +126,7 @@ resource "azurerm_spring_cloud_java_deployment" "example" {
 
 ### Automate provisioning using a Bicep file
 
-To configure the environment variables in a Bicep file, add the following code to the file, replacing the *\<...>* placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=bicep).
+To configure the environment variables in a Bicep file, add the following code to the file, replacing the `<...>` placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=bicep).
 
 ```bicep
 deploymentSettings: {
@@ -143,7 +143,7 @@ deploymentSettings: {
 
 ### Automate provisioning using an ARM template
 
-To configure the environment variables in an ARM template, add the following code to the template, replacing the *\<...>* placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=json).
+To configure the environment variables in an ARM template, add the following code to the template, replacing the `<...>` placeholders with your own values. For more information, see [Microsoft.AppPlatform Spring/apps/deployments](/azure/templates/microsoft.appplatform/spring/apps/deployments?tabs=json).
 
 ```json
 "deploymentSettings": {
@@ -170,7 +170,7 @@ Use the following steps to monitor applications and metrics:
 
    :::image type="content" source="media/how-to-elastic-apm-java-agent-monitor/elastic-apm-get-kibana-link.png" alt-text="Screenshot of the Azure portal that shows the Elasticsearch page with the Deployment URL Kibana link highlighted." lightbox="media/how-to-elastic-apm-java-agent-monitor/elastic-apm-get-kibana-link.png":::
 
-1. After Kibana is open, search for *APM* in the search bar, then select **APM**.
+1. After Kibana is open, search for **APM** in the search bar, then select **APM**.
 
    :::image type="content" source="media/how-to-elastic-apm-java-agent-monitor/elastic-apm-kibana-search-apm.png" alt-text="Screenshot of Elastic / Kibana that shows the APM search results." lightbox="media/how-to-elastic-apm-java-agent-monitor/elastic-apm-kibana-search-apm.png":::
 

articles/spring-apps/basic-standard/how-to-elastic-diagnostic-settings.md

@@ -68,7 +68,7 @@ Use the following steps to analyze the logs:
 
 Application logs provide critical information and verbose logs about your application's health, performance, and more. Use the following steps to analyze the logs:
 
-1. In Kibana, in the **Search** bar at top, type *Discover*, then select the result.
+1. In Kibana, in the **Search** bar at top, type **Discover**, then select the result.
 
    :::image type="content" source="media/how-to-elastic-diagnostic-settings/elastic-kibana-go-discover.png" alt-text="Screenshot of Elastic / Kibana  that shows the search results for Discover." lightbox="media/how-to-elastic-diagnostic-settings/elastic-kibana-go-discover.png":::
 
@@ -148,7 +148,7 @@ Kibana allows you to visualize data with Dashboards and a rich ecosystem of visu
 
 Use the following steps to show the various log levels in your logs so you can assess the overall health of the services.
 
-1. From the available fields list on left in **Discover**, search for *log.level* in the search box under the **logs-** index pattern.
+1. From the available fields list on left in **Discover**, search for **log.level** in the search box under the **logs-** index pattern.
 
 1. Select the **log.level** field. From the floating informational panel about **log.level**, select **Visualize**.
 

articles/spring-apps/basic-standard/how-to-enable-ingress-to-app-tls.md

@@ -75,7 +75,7 @@ To enable ingress-to-app TLS in the [Azure portal](https://portal.azure.com/), f
 1. Create an app in the portal as you normally would. Navigate to it in the portal.
 2. Scroll down to the **Settings** group in the left navigation pane.
 3. Select **Ingress-to-app TLS**.
-4. Switch **Ingress-to-app TLS** to *Yes*.
+4. Switch **Ingress-to-app TLS** to **Yes**.
 
 :::image type="content" source="media/how-to-enable-ingress-to-app-tls/enable-i2a-tls.png" alt-text="Screenshot of the Azure portal that shows the app Ingress-to-app TLS page." lightbox="media/how-to-enable-ingress-to-app-tls/enable-i2a-tls.png":::
 

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

@@ -52,15 +52,15 @@ To set up a managed identity in the portal, first create an app, and then enable
 1. Create an app in the portal as you normally would. Navigate to it in the portal.
 2. Scroll down to the **Settings** group in the left navigation pane.
 3. Select **Identity**.
-4. Within the **System assigned** tab, switch **Status** to *On*. Select **Save**.
+4. Within the **System assigned** tab, switch **Status** to **On**. Select **Save**.
 
 ### [Azure CLI](#tab/azure-cli)
 
 You can enable system-assigned managed identity during app creation or on an existing app.
 
 ### Enable system-assigned managed identity during creation of an app
 
-The following example creates an app named *app_name* with a system-assigned managed identity, as requested by the `--assign-identity` parameter.
+The following example creates an app named `app_name` with a system-assigned managed identity, as requested by the `--assign-identity` parameter.
 
 ```azurecli
 az spring app create \

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

@@ -107,7 +107,7 @@ az spring app create --name solar-system-weather
 
 ### Deploy with Azure CLI directly
 
-Create the *.github/workflows/main.yml* file in the repository with the following content. Replace *\<your resource group name>* and *\<your service name>* with the correct values.
+Create the **.github/workflows/main.yml** file in the repository with the following content. Replace `<your resource group name>` and `<your service name>` with the correct values.
 
 ```yaml
 name: Steeltoe-CD
@@ -238,7 +238,7 @@ Azure Spring Apps supports deploying to deployments with built artifacts (for ex
 The following example deploys to the default production deployment in Azure Spring Apps using JAR file built by Maven. This example is the only possible deployment scenario when using the Basic SKU:
 
 > [!NOTE]
-> The package search pattern should only return exactly one package. If the build task produces multiple JAR packages such as *sources.jar* and *javadoc.jar*, you need to refine the search pattern so that it only matches the application binary artifact.
+> The package search pattern should only return exactly one package. If the build task produces multiple JAR packages such as **sources.jar** and **javadoc.jar**, you need to refine the search pattern so that it only matches the application binary artifact.
 
 ```yml
 name: AzureSpringApps
@@ -528,7 +528,7 @@ jobs:
 
 ## Run the workflow
 
-GitHub **Actions** should be enabled automatically after you push *.github/workflow/main.yml* to GitHub. The action is triggered when you push a new commit. If you create this file in the browser, your action should have already run.
+GitHub **Actions** should be enabled automatically after you push **.github/workflow/main.yml** to GitHub. The action is triggered when you push a new commit. If you create this file in the browser, your action should have already run.
 
 To verify that the action has been enabled, select the **Actions** tab on the GitHub repository page:
 

articles/spring-apps/basic-standard/how-to-integrate-azure-load-balancers.md

@@ -39,7 +39,7 @@ We recommend that the domain name, as seen by the browser, is the same as the ho
 
 ## Integrate Azure Spring Apps with Azure Traffic Manager
 
-To integrate Azure Spring Apps with Traffic Manager, add its public endpoints as traffic manager’s endpoints and then configure custom domain for both traffic manager and Azure Spring Apps.
+To integrate Azure Spring Apps with Traffic Manager, add its public endpoints as traffic manager's endpoints and then configure custom domain for both traffic manager and Azure Spring Apps.
 
 ### Add Endpoint in Traffic Manager
 
@@ -57,15 +57,15 @@ Add endpoints in traffic manager:
 
 To finish the configuration:
 
-1. Sign in to the website of your domain provider, and create a CNAME record mapping from your custom domain to traffic manager’s Azure default domain name.
+1. Sign in to the website of your domain provider, and create a CNAME record mapping from your custom domain to traffic manager's Azure default domain name.
 
 ## Integrate Azure Spring Apps with Azure App Gateway
 
 To integrate with Azure Spring Apps service, complete the following configurations:
 
 ### Configure Backend Pool
 
-1. Specify **Target type** as *IP address* or *FQDN*.
+1. Specify **Target type** as **IP address** or **FQDN**.
 1. Enter your Azure Spring Apps public endpoints.
 
    :::image type="content" source="media/how-to-integrate-azure-load-balancers/app-gateway-1.png" alt-text="Screenshot of the Azure portal that shows the Add backend pool page with the Backend targets values highlighted." lightbox="media/how-to-integrate-azure-load-balancers/app-gateway-1.png":::

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

@@ -51,9 +51,9 @@ The following procedures deploy a Hello World application using IntelliJ IDEA.
 ## Open gs-spring-boot project
 
 1. Download and unzip the source repository for this tutorial, or clone it using the following Git command: `git clone https://github.com/spring-guides/gs-spring-boot.git`
-1. Navigate to the *gs-spring-boot\complete* folder.
+1. Navigate to the **gs-spring-boot\complete** folder.
 1. Open IntelliJ **Welcome** dialog, select **Import Project** to open the import wizard.
-1. Select the *gs-spring-boot\complete* folder.
+1. Select the **gs-spring-boot\complete** folder.
 
    :::image type="content" source="media/how-to-intellij-deploy-apps/import-project.png" alt-text="Screenshot of IntelliJ IDEA Open File or Project dialog box with complete folder highlighted." lightbox="media/how-to-intellij-deploy-apps/import-project.png":::