Merge pull request #293835 from JoshTheTechWriter/italics-to-bold

Bulk formatting updates

Author: v-shils

articles/spring-apps/basic-standard/access-app-virtual-network.md

@@ -42,7 +42,7 @@ Use the following steps to create a private DNS zone for an application in the p
 
 1. On the **Private DNS zones** page, select **Add**.
 
-1. Fill out the form on the **Create Private DNS zone** page. For **Name**, enter *private.azuremicroservices.io*.
+1. Fill out the form on the **Create Private DNS zone** page. For **Name**, enter **private.azuremicroservices.io**.
 
 1. Select **Review + Create**.
 
@@ -212,9 +212,9 @@ Use the following steps to use the private DNS zone to translate/resolve DNS:
    |----------------|-----------------------------------------------------------------------------------------------------------------------------|
    | **Name**       | Enter *\**.                                                                                                                 |
    | **Type**       | Select **A**.                                                                                                               |
-   | **TTL**        | Enter *1*.                                                                                                                  |
+   | **TTL**        | Enter **1**.                                                                                                                  |
    | **TTL unit**   | Select **Hours**.                                                                                                           |
-   | **IP address** | Enter the [IP address](#find-the-ip-address-for-your-application). The following screenshot uses the IP address *10.1.0.7*. |
+   | **IP address** | Enter the [IP address](#find-the-ip-address-for-your-application). The following screenshot uses the IP address **10.1.0.7**. |
 
    :::image type="content" source="media/access-app-virtual-network/private-dns-zone-add-record.png" alt-text="Screenshot of the Azure portal that shows the Add record set page." lightbox="media/access-app-virtual-network/private-dns-zone-add-record.png":::
 
@@ -246,7 +246,7 @@ Use the following steps to link the private DNS zone you created to the virtual
 
 1. Select **Virtual network links**, and then select **Add**.
 
-1. For **Link name**, enter *azure-spring-apps-dns-link*.
+1. For **Link name**, enter **azure-spring-apps-dns-link**.
 
 1. For **Virtual network**, select the virtual network you created previously.
 

articles/spring-apps/basic-standard/concept-app-status.md

@@ -51,7 +51,7 @@ The provisioning state is accessible only from the CLI. The status is reported a
 | Creating  | The resource is creating and isn't ready.              |
 | Updating  | The resource is updating and the functionality might be different from the deployment definition until the update is complete.                               |
 | Succeeded | Successfully supplied resources and deploys the binary. The deployment's functionality is the same as the definition and all app instances are working. |
-| Failed    | Failed to achieve the *Succeeded* goal.                 |
+| Failed    | Failed to achieve the **Succeeded** goal.                 |
 | Deleting  | The resource is being deleted which prevents operation, and the resource isn't available in this status. |
 
 ### Registration status
@@ -73,9 +73,9 @@ The instance status is reported as one of the following values:
 
 | Value       | Definition |
 |-------------|------------|
-| Starting    | The binary is successfully deployed to the given instance. The instance booting the jar file might fail because the jar can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the *Starting* state. |
+| Starting    | The binary is successfully deployed to the given instance. The instance booting the **.jar** file might fail because the **.jar** file can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the **Starting** state. |
 | Running     | The instance works. The instance can serve requests from inside Azure Spring Apps. |
-| Failed      | The app instance failed to start the user's binary after several retries. The app instance might be in one of the following states:<br/>- The app might stay in the *Starting* status and never be ready for serving requests.<br/>- The app might boot up but crash in a few seconds. |
+| Failed      | The app instance failed to start the user's binary after several retries. The app instance might be in one of the following states:<br/>- The app might stay in the **Starting** status and never be ready for serving requests.<br/>- The app might boot up but crash in a few seconds. |
 | Terminating | The app instance is shutting down. The app might not serve requests and the app instance is removed. |
 
 ### App discovery status

articles/spring-apps/basic-standard/concept-understand-app-and-deployment.md

@@ -17,7 +17,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 
 **This article applies to:** ✅ Basic/Standard ✅ Enterprise
 
-*App* and *Deployment* are the two key concepts in the resource model of Azure Spring Apps. In Azure Spring Apps, an *App* is an abstraction of one business app. One version of code or binary deployed as the *App* runs in a *Deployment*. Apps run in an *Azure Spring Apps service instance*, or simply *service instance*, as shown next.
+*App* and *Deployment* are the two key concepts in the resource model of Azure Spring Apps. In Azure Spring Apps, an App is an abstraction of one business app. One version of code or binary deployed as the App runs in a Deployment. Apps run in an *Azure Spring Apps service instance*, or simply *service instance*, as shown next.
 
 :::image type="content" source="media/concept-understand-app-and-deployment/app-deployment-rev.png" alt-text="Diagram showing the relationship between the apps and deployments." border="false":::
 

articles/spring-apps/basic-standard/connect-managed-identity-to-azure-sql.md

@@ -54,7 +54,7 @@ az ad sp show --id <identity-object-ID> --query displayName
 
 ### Configure your Java app to use a managed identity
 
-Open the *src/main/resources/application.properties* file, then add `Authentication=ActiveDirectoryMSI;` at the end of the `spring.datasource.url` line, as shown in the following example. Be sure to use the correct value for the $AZ_DATABASE_NAME variable.
+Open the **src/main/resources/application.properties** file, then add `Authentication=ActiveDirectoryMSI;` at the end of the `spring.datasource.url` line, as shown in the following example. Be sure to use the correct value for the $AZ_DATABASE_NAME variable.
 
 ```properties
 spring.datasource.url=jdbc:sqlserver://$AZ_DATABASE_NAME.database.windows.net:1433;database=demo;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;Authentication=ActiveDirectoryMSI;

articles/spring-apps/basic-standard/diagnostic-services.md

@@ -209,7 +209,7 @@ Use this query to find response `Status`, `RequestTime`, and other properties of
 
 ### Show ingress log entries for a specific requestId
 
-To review log entries for a specific `requestId` value *\<request_ID>*, run the following query:
+To review log entries for a specific `requestId` value `<request_ID>`, run the following query:
 
 ```kusto
 AppPlatformIngressLogs
@@ -230,7 +230,7 @@ AppPlatformBuildLogs
 
 ### Show build log entries for a specific app in a specific build stage
 
-To review log entries for a specific app in a specific build stage, run the following query. Replace the *`<app-name>`* placeholder with your application name. Replace the *`<build-stage>`* placeholder with one of the following values, which represent the stages of the build process: `prepare`, `detect`, `restore`, `analyze`, `build`, `export`, or `completion`.
+To review log entries for a specific app in a specific build stage, run the following query. Replace the `<app-name>` placeholder with your application name. Replace the `<build-stage>` placeholder with one of the following values, which represent the stages of the build process: `prepare`, `detect`, `restore`, `analyze`, `build`, `export`, or `completion`.
 
 ```kusto
 AppPlatformBuildLogs

articles/spring-apps/basic-standard/faq.md

@@ -89,7 +89,7 @@ For the quickest way to get started with Azure Spring Apps, follow the instructi
 
 Find metrics in the App Overview tab and the [Azure Monitor](/azure/azure-monitor/essentials/data-platform-metrics#metrics-explorer) tab.
 
-Azure Spring Apps supports exporting Spring application logs and metrics to Azure Storage, Event Hubs, and [Log Analytics](/azure/azure-monitor/logs/data-platform-logs). The table name in Log Analytics is *AppPlatformLogsforSpring*. To learn how to enable it, see [Diagnostic services](diagnostic-services.md).
+Azure Spring Apps supports exporting Spring application logs and metrics to Azure Storage, Event Hubs, and [Log Analytics](/azure/azure-monitor/logs/data-platform-logs). The table name in Log Analytics is `AppPlatformLogsforSpring`. To learn how to enable it, see [Diagnostic services](diagnostic-services.md).
 
 ### Does Azure Spring Apps support distributed tracing?
 

articles/spring-apps/basic-standard/how-to-access-data-plane-azure-ad-rbac.md

@@ -49,8 +49,8 @@ After the role is assigned, the assignee can access the Spring Cloud Config Serv
 
 1. Compose the endpoint. We support the default endpoints of the Spring Cloud Config Server and Spring Cloud Service Registry managed by Azure Spring Apps.
 
-    * *'https://SERVICE_NAME.svc.azuremicroservices.io/eureka/{path}'*
-    * *'https://SERVICE_NAME.svc.azuremicroservices.io/config/{path}'*
+    * `https://SERVICE_NAME.svc.azuremicroservices.io/eureka/<path>`
+    * `https://SERVICE_NAME.svc.azuremicroservices.io/config/<path>`
 
     >[!NOTE]
     > If you're using Microsoft Azure operated by 21Vianet, replace `*.azuremicroservices.io` with `*.microservices.azure.cn`. For more information, see the section [Check endpoints in Azure](/azure/china/resources-developer-guide#check-endpoints-in-azure) in the [Microsoft Azure operated by 21Vianet developer guide](/azure/china/resources-developer-guide).
@@ -77,9 +77,9 @@ After the role is assigned, you can register Spring Boot apps to Spring Cloud Co
 
 For more information, see the samples [Access Azure Spring Apps managed Config Server](https://github.com/Azure-Samples/azure-spring-apps-samples/tree/main/custom-config-server-client) and [Access Azure Spring Apps managed Service Registry](https://github.com/Azure-Samples/azure-spring-apps-samples/tree/main/custom-eureka-client). The following sections explain some important details in these samples.
 
-**In *AccessTokenManager.java*:**
+In **AccessTokenManager.java**:
 
-`AccessTokenManager` is responsible for getting an access token from Microsoft Entra ID. Configure the service principal's sign-in information in the *application.properties* file and initialize `ApplicationTokenCredentials` to get the token. You can find this file in both samples.
+`AccessTokenManager` is responsible for getting an access token from Microsoft Entra ID. Configure the service principal's sign-in information in the **application.properties** file and initialize `ApplicationTokenCredentials` to get the token. You can find this file in both samples.
 
 ```java
 prop.load(in);
@@ -91,7 +91,7 @@ credentials = new ApplicationTokenCredentials(
     clientId, tenantId, secret, AzureEnvironment.AZURE);
 ```
 
-**In *CustomConfigServiceBootstrapConfiguration.java*:**
+In **CustomConfigServiceBootstrapConfiguration.java**:
 
 `CustomConfigServiceBootstrapConfiguration` implements the custom REST template for Config Server and injects the token from Microsoft Entra ID as `Authorization` headers. You can find this file in the [Config Server sample](https://github.com/Azure-Samples/azure-spring-apps-samples/tree/main/custom-config-server-client).
 
@@ -111,7 +111,7 @@ public class RequestResponseHandlerInterceptor implements ClientHttpRequestInter
 }
 ```
 
-**In *CustomRestTemplateTransportClientFactories.java*:**
+In **CustomRestTemplateTransportClientFactories.java**:
 
 The previous two classes are for the implementation of the custom REST template for Spring Cloud Service Registry. The `intercept` part is the same as in the Config Server above. Be sure to add `factory.mappingJacksonHttpMessageConverter()` to the message converters. You can find this file in the [Spring Cloud Service Registry sample](https://github.com/Azure-Samples/azure-spring-apps-samples/tree/main/custom-eureka-client).
 

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

@@ -51,7 +51,7 @@ To activate an application through the Azure CLI, use the following steps.
 
 1. Create a resource group.
 1. Create an instance of Azure Spring Apps.
-1. Create an application using the following command. Replace the placeholders *\<...>* with your own values.
+1. Create an application using the following command. Replace the placeholders `<...>` with your own values.
 
     ```azurecli
     az spring app create \
@@ -81,7 +81,7 @@ To activate an application through the Azure CLI, use the following steps.
               APPDYNAMICS_CONTROLLER_PORT=443
     ```
 
-Azure Spring Apps pre-installs the AppDynamics Java agent to the path */opt/agents/appdynamics/java/javaagent.jar*. You can activate the agent from your applications' JVM options, then configure the agent using environment variables. You can find values for these variables at [Monitor Azure Spring Apps with Java Agent](https://docs.appdynamics.com/appd/24.x/24.3/en/application-monitoring/install-app-server-agents/java-agent/monitor-azure-spring-cloud-with-java-agent). For more information about how these variables help to view and organize reports in the AppDynamics UI, see [Tiers and Nodes](https://docs.appdynamics.com/appd/24.x/24.3/en/application-monitoring/tiers-and-nodes).
+Azure Spring Apps pre-installs the AppDynamics Java agent to the path **/opt/agents/appdynamics/java/javaagent.jar**. You can activate the agent from your applications' JVM options, then configure the agent using environment variables. You can find values for these variables at [Monitor Azure Spring Apps with Java Agent](https://docs.appdynamics.com/appd/24.x/24.3/en/application-monitoring/install-app-server-agents/java-agent/monitor-azure-spring-cloud-with-java-agent). For more information about how these variables help to view and organize reports in the AppDynamics UI, see [Tiers and Nodes](https://docs.appdynamics.com/appd/24.x/24.3/en/application-monitoring/tiers-and-nodes).
 
 ### Activate an application with the AppDynamics Agent using the Azure portal
 
@@ -109,7 +109,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" {
@@ -132,7 +132,7 @@ resource "azurerm_spring_cloud_java_deployment" "example" {
 
 ### Automate provisioning using 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).
+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: {
@@ -153,7 +153,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": {

articles/spring-apps/basic-standard/how-to-application-insights.md

@@ -133,7 +133,7 @@ To check and update the current settings for the Application Insights buildpack
 1. Choose your builder.
 1. Select **Edit** under the Bindings column.
 
-Application Insights settings are found in the *ApplicationInsights* item listed under the *Binding type* column.
+Application Insights settings are found in the **ApplicationInsights** item listed under the **Binding type** column.
 
 1. Select the **Bound** hyperlink, or select **Edit Binding** under the ellipse, to open and edit the Application Insights buildpack bindings.
 
@@ -147,7 +147,7 @@ Application Insights settings are found in the *ApplicationInsights* item listed
 
 ## Manage Application Insights using Azure CLI
 
-You can manage Application Insights using Azure CLI commands. In the following commands, be sure to replace the *\<placeholder>* text with the values described. The *\<service-instance-name>* placeholder refers to the name of your Azure Spring Apps instance.
+You can manage Application Insights using Azure CLI commands. In the following commands, be sure to replace the `<placeholder>` text with the values described. The `<service-instance-name>` placeholder refers to the name of your Azure Spring Apps instance.
 
 ### Enable Application Insights
 
@@ -352,7 +352,7 @@ The following sections describe how to automate your deployment using Bicep, Azu
 
 ### Bicep
 
-To deploy using a Bicep file, copy the following content into a *main.bicep* file. For more information, see [Microsoft.AppPlatform Spring/monitoringSettings](/azure/templates/microsoft.appplatform/spring/monitoringsettings).
+To deploy using a Bicep file, copy the following content into a **main.bicep** file. For more information, see [Microsoft.AppPlatform Spring/monitoringSettings](/azure/templates/microsoft.appplatform/spring/monitoringsettings).
 
 ```bicep
 param springName string
@@ -376,7 +376,7 @@ resource monitorSetting 'Microsoft.AppPlatform/Spring/monitoringSettings@2020-11
 
 ### ARM templates
 
-To deploy using an ARM template, copy the following content into an *azuredeploy.json* file. For more information, see [Microsoft.AppPlatform Spring/monitoringSettings](/azure/templates/microsoft.appplatform/spring/monitoringsettings).
+To deploy using an ARM template, copy the following content into an **azuredeploy.json** file. For more information, see [Microsoft.AppPlatform Spring/monitoringSettings](/azure/templates/microsoft.appplatform/spring/monitoringsettings).
 
 ```json
 {

articles/spring-apps/basic-standard/how-to-bind-cosmos.md

@@ -29,7 +29,7 @@ Instead of manually configuring your Spring Boot applications, you can automatic
 
 ### [Java](#tab/Java)
 
-1. Add one of the following dependencies to your application's *pom.xml* file. Choose the dependency that is appropriate for your API type.
+1. Add one of the following dependencies to your application's **pom.xml** file. Choose the dependency that is appropriate for your API type.
 
    * API type: NoSQL