Edits to various basic-standard files.

Author: JoshTheTechWriter

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

@@ -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": {
@@ -219,7 +219,7 @@ You can define more metrics for the JVM, as shown in this screenshot of the **Me
 
 ## View AppDynamics Agent logs
 
-By default, Azure Spring Apps prints the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
+By default, Azure Spring Apps prints the **info** level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
 
 You can also get the logs of the AppDynamics Agent from the following locations:
 

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
 

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

@@ -29,7 +29,7 @@ With Azure Spring Apps, you can connect selected Azure services to your applicat
 
 ### [Java](#tab/Java)
 
-1. In your project's *pom.xml* file, add the following dependency:
+1. In your project's **pom.xml** file, add the following dependency:
 
    ```xml
    <dependency>
@@ -42,7 +42,7 @@ With Azure Spring Apps, you can connect selected Azure services to your applicat
    </dependency>
    ```
 
-1. In the *application.properties* file, remove any `spring.datasource.*` properties.
+1. In the **application.properties** file, remove any `spring.datasource.*` properties.
 
 1. Update the current app by running `az spring app deploy`, or create a new deployment for this change by running `az spring app deployment create`.
 

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

@@ -37,7 +37,7 @@ PostgreSQL authentication uses accounts stored in PostgreSQL. If you choose to u
 
 Use the following steps to prepare your project.
 
-1. In your project's *pom.xml* file, add the following dependency:
+1. In your project's **pom.xml** file, add the following dependency:
 
    ```xml
    <dependency>
@@ -50,7 +50,7 @@ Use the following steps to prepare your project.
    </dependency>
    ```
 
-1. In the *application.properties* file, remove any `spring.datasource.*` properties.
+1. In the **application.properties** file, remove any `spring.datasource.*` properties.
 
 1. Update the current app by running `az spring app deploy`, or create a new deployment for this change by running `az spring app deployment create`.
 

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

@@ -31,7 +31,7 @@ If you don't have a deployed Azure Spring Apps instance, follow the steps in the
 
 ### [Java](#tab/Java)
 
-1. Add the following dependency to your project's *pom.xml* file:
+1. Add the following dependency to your project's **pom.xml** file:
 
    ```xml
    <dependency>
@@ -40,7 +40,7 @@ If you don't have a deployed Azure Spring Apps instance, follow the steps in the
    </dependency>
    ```
 
-1. Remove any `spring.redis.*` properties from the *application.properties* file
+1. Remove any `spring.redis.*` properties from the **application.properties** file
 
 1. Update the current deployment using `az spring app update` or create a new deployment using `az spring app deployment create`.
 

articles/spring-apps/basic-standard/how-to-built-in-persistent-storage.md

@@ -19,12 +19,12 @@ ms.custom: devx-track-java, devx-track-extended-java, devx-track-azurecli, engag
 
 Azure Spring Apps provides two types of built-in storage for your application: persistent and temporary.
 
-By default, Azure Spring Apps provides temporary storage for each application instance. Temporary storage is limited to 5 GB per instance with */tmp* as the default mount path.
+By default, Azure Spring Apps provides temporary storage for each application instance. Temporary storage is limited to 5 GB per instance with **/tmp** as the default mount path.
 
 > [!WARNING]
 > If you restart an application instance, the associated temporary storage is permanently deleted.
 
-Persistent storage is a file-share container managed by Azure and allocated per application. All instances of an application share data stored in persistent storage. An Azure Spring Apps instance can have a maximum of 10 applications with persistent storage enabled. Each application is allocated 50 GB of persistent storage. The default mount path for persistent storage is */persistent*.
+Persistent storage is a file-share container managed by Azure and allocated per application. All instances of an application share data stored in persistent storage. An Azure Spring Apps instance can have a maximum of 10 applications with persistent storage enabled. Each application is allocated 50 GB of persistent storage. The default mount path for persistent storage is **/persistent**.
 
 ## Enable or disable built-in persistent storage
 

articles/spring-apps/basic-standard/how-to-capture-dumps.md

@@ -87,7 +87,7 @@ Use the following steps to generate a heap or thread dump of your app in Azure S
 
 ## Get your diagnostic files
 
-Navigate to the target file path in your persistent storage and find your dump/JFR. From there, you can download them to your local machine. The name of the generated file will be similar to *`<app-instance>_heapdump_<time-stamp>.hprof`* for the heap dump, *`<app-instance>_threaddump_<time-stamp>.txt`* for the thread dump, and *`<app-instance>_JFR_<time-stamp>.jfr`* for the JFR file.
+Navigate to the target file path in your persistent storage and find your dump/JFR. From there, you can download them to your local machine. The name of the generated file will be similar to `<app-instance>_heapdump_<time-stamp>.hprof` for the heap dump, `<app-instance>_threaddump_<time-stamp>.txt` for the thread dump, and `<app-instance>_JFR_<time-stamp>.jfr` for the JFR file.
 
 ## Next steps
 

articles/spring-apps/basic-standard/how-to-cicd.md

@@ -109,11 +109,11 @@ You can now build and deploy your projects using a series of tasks. The followin
 To deploy using a pipeline, follow these steps:
 
 1. Select **Pipelines**, then create a new pipeline with a Maven template.
-1. Edit the *azure-pipelines.yml* file to set the `mavenPomFile` field to *'complete/pom.xml'*.
+1. Edit the **azure-pipelines.yml** file to set the `mavenPomFile` field to **complete/pom.xml**.
 1. Select **Show assistant** on the right side, then select the **Azure Spring Apps** template.
 1. Select the service connection you created for your Azure Subscription, then select your Azure Spring Apps instance and app instance.
 1. Disable **Use Staging Deployment**.
-1. Set **Package or folder** to *complete/target/spring-boot-complete-0.0.1-SNAPSHOT.jar*.
+1. Set **Package or folder** to **complete/target/spring-boot-complete-0.0.1-SNAPSHOT.jar**.
 1. Select **Add** to add this task to your pipeline.
 
    Your pipeline settings should match the following image.
@@ -179,9 +179,9 @@ The following steps show you how to enable a blue-green deployment from the **Re
 1. Select **Pipelines** and create a new pipeline for your Maven build and publish artifact.
    1. Select **Azure Repos Git** for your code location.
    1. Select a repository where your code is located.
-   1. Select the **Maven** template and modify the file to set the `mavenPomFile` field to *`complete/pom.xml`*.
+   1. Select the **Maven** template and modify the file to set the `mavenPomFile` field to **complete/pom.xml**.
    1. Select **Show assistant** on the right side and select the **Publish build artifacts** template.
-   1. Set **Path to publish** to *complete/target/spring-boot-complete-0.0.1-SNAPSHOT.jar*.
+   1. Set **Path to publish** to **complete/target/spring-boot-complete-0.0.1-SNAPSHOT.jar**.
    1. Select **Save and run**.
 
 1. Select **Releases**, then **Create release**.
@@ -202,7 +202,7 @@ The following steps show you how to enable a blue-green deployment from the **Re
    1. Select **Add**, then **Save**.
 1. Select **1 job, 1 task** under **Stages**.
 1. Navigate to the **Azure Spring Apps Deploy** task in **Stage 1**, then select the ellipsis next to **Package or folder**.
-1. Select *spring-boot-complete-0.0.1-SNAPSHOT.jar* in the dialog, then select **OK**.
+1. Select **spring-boot-complete-0.0.1-SNAPSHOT.jar** in the dialog, then select **OK**.
 
    :::image type="content" source="media/how-to-cicd/change-artifact-path.jpg" alt-text="Screenshot of Azure DevOps that shows the Select a file or folder dialog box." lightbox="media/how-to-cicd/change-artifact-path.jpg":::