First commit of fifth batch of files.

Author: JoshTheTechWriter

articles/spring-apps/enterprise/how-to-configure-enterprise-spring-cloud-gateway.md

@@ -318,7 +318,7 @@ az spring gateway update \
 
 You must specify the protocol as HTTPS in the route configuration. The following JSON object instructs VMware Spring Cloud Gateway to use the HTTPS protocol for all traffic between the gateway and the app.
 
-1. Create a file named *test-tls-route.json* with the following content:
+1. Create a file named **test-tls-route.json** with the following content:
 
    ```json
    {
@@ -864,7 +864,7 @@ Use the following steps to update the add-on configuration.
 
 ### [Azure CLI](#tab/Azure-CLI) 
 
-1. Prepare the JSON file for add-on configurations (*\<file-name-of-addon-configs-json\>.json*) with the following content:
+1. Prepare the JSON file for add-on configurations (**\<file-name-of-addon-configs-json\>.json**) with the following content:
 
    ```json
    {

articles/spring-apps/enterprise/how-to-enterprise-configure-apm-integration-and-ca-certificates.md

@@ -526,7 +526,7 @@ az spring build-service builder buildpack-binding list \
 
 ### Create a binding
 
-Use this command to change the binding from *Unbound* to *Bound* status:
+Use this command to change the binding from **Unbound** to **Bound** status:
 
 ```azurecli
 az spring build-service builder buildpack-binding create \
@@ -572,7 +572,7 @@ For more information on the `properties` and `secrets` parameters for your build
 
 ### Delete a binding
 
-Use the following command to change the binding status from *Bound* to *Unbound*.
+Use the following command to change the binding status from **Bound** to **Unbound**.
 
 ```azurecli
 az spring build-service builder buildpack-binding delete \

articles/spring-apps/enterprise/how-to-enterprise-deploy-polyglot-apps.md

@@ -228,7 +228,7 @@ The [Paketo buildpacks samples](https://github.com/paketo-buildpacks/samples/tre
 
 - Serving static files with a default server configuration file using `BP_WEB_SERVER` to select either [HTTPD](https://github.com/paketo-buildpacks/samples/blob/main/web-servers/no-config-file-sample/HTTPD.md) or [NGINX](https://github.com/paketo-buildpacks/samples/blob/main/web-servers/no-config-file-sample/NGINX.md).
 - Using Node Package Manager to build a [React app](https://github.com/paketo-buildpacks/samples/tree/main/web-servers/react-frontend-sample) into static files that a web server can serve. Use the following steps:
-  1. Define a script under the `scripts` property of the *package.json* file that builds your production-ready static assets. For React, it's `build`.
+  1. Define a script under the `scripts` property of the **package.json** file that builds your production-ready static assets. For React, it's `build`.
   1. Find out where static assets are stored after the build script runs. For React, static assets are stored in `./build` by default.
   1. Set `BP_NODE_RUN_SCRIPTS` to the name of the build script.
   1. Set `BP_WEB_SERVER_ROOT` to the build output directory.

articles/spring-apps/enterprise/how-to-enterprise-deploy-static-file.md

@@ -95,7 +95,7 @@ Next, select **GENERATE** to get a sample project for Spring Boot with the follo
 
 ### Confirm the configuration of dependent libraries for the Service Registry client (Eureka client)
 
-Next, confirm that the *pom.xml* file for the project contains the following dependency. Add the dependency if it's missing.
+Next, confirm that the **pom.xml** file for the project contains the following dependency. Add the dependency if it's missing.
 
 ```xml
 <dependency>
@@ -106,7 +106,7 @@ Next, confirm that the *pom.xml* file for the project contains the following dep
 
 ### Implement the Service Registry client
 
-Add an `@EnableEurekaClient` annotation to the *SampleServiceAApplication.java* file to configure it as a Eureka Client.
+Add an `@EnableEurekaClient` annotation to the **SampleServiceAApplication.java** file to configure it as a Eureka Client.
 
 ```java
 package com.example.Sample.Service.A;
@@ -127,7 +127,7 @@ public class SampleServiceAApplication {
 
 ### Create a REST endpoint for testing
 
-You can now register the service to Service Registry, but you can't verify it until you implement a service endpoint. To create RESTful endpoints that external services can call, add a *ServiceAEndpoint.java* file to your project with the following code.
+You can now register the service to Service Registry, but you can't verify it until you implement a service endpoint. To create RESTful endpoints that external services can call, add a **ServiceAEndpoint.java** file to your project with the following code.
 
 ```java
 package com.example.Sample.Service.A;
@@ -184,7 +184,7 @@ The `--assign-endpoint` argument grants a public IP for validation and enables a
 
 After you create a service instance with Spring Boot and create an application in Azure Spring Apps, you deploy the application and confirm the operation. Before that, however, you must bind your application to the Service Registry so that it can get connection information from the registry.
 
-Typically, a Eureka client needs to write the following connection information settings in the *application.properties* configuration file of a Spring Boot application so that you can connect to the server:
+Typically, a Eureka client needs to write the following connection information settings in the **application.properties** configuration file of a Spring Boot application so that you can connect to the server:
 
 ```properties
 eureka.client.service-url.defaultZone=http://eureka:8761/eureka/
@@ -234,7 +234,7 @@ You can also bind your application to the Service Registry from the Azure portal
 
 ### Deploy an application to Azure Spring Apps
 
-Now that you bound your application, deploy the Spring Boot artifact file *Sample-Service-A-A-0.0.1-SNAPSHOT.jar* to Azure Spring Apps. To deploy, use the following command:
+Now that you bound your application, deploy the Spring Boot artifact file **Sample-Service-A-A-0.0.1-SNAPSHOT.jar** to Azure Spring Apps. To deploy, use the following command:
 
 ```azurecli
 az spring app deploy \
@@ -327,7 +327,7 @@ public class SampleServiceBApplication {
 
 ### Implement service endpoints in Service B
 
-Next, implement a new service endpoint (`/invoke-serviceA`) that invokes Service A. Add a *ServiceBEndpoint.java* file to your project with the following code.
+Next, implement a new service endpoint (`/invoke-serviceA`) that invokes Service A. Add a **ServiceBEndpoint.java** file to your project with the following code.
 
 ```java
 package com.example.Sample.Service.B;

articles/spring-apps/enterprise/how-to-enterprise-service-registry.md

@@ -49,9 +49,9 @@ First, you must get the assigned public endpoint for Spring Cloud Gateway and AP
 
 Register your application to establish a trust relationship between your app and the Microsoft identity platform using the following steps:
 
-1. From the *Home* screen, select **Microsoft Entra ID** from the left menu.
-1. Select **App Registrations** under *Manage*, then select **New registration**.
-1. Enter a display name for your application under *Name*, then select an account type to register under *Supported account types*.
+1. From the **Home** screen, select **Microsoft Entra ID** from the left menu.
+1. Select **App Registrations** under **Manage**, then select **New registration**.
+1. Enter a display name for your application under **Name**, then select an account type to register under *Supported account types*.
 1. In *Redirect URI (optional)* select **Web**, then enter the URL from the above section in the text box. The redirect URI is the location where Microsoft Entra ID redirects your client and sends security tokens after authentication.
 1. Select **Register** to finish registering the application.
 
@@ -61,7 +61,7 @@ When registration finishes, you'll see the *Application (client) ID* on the **Ov
 
 You can also add redirect URIs after app registration by following these steps:
 
-1. From your application overview, under *Manage* in the left menu, select **Authentication**.
+1. From your application overview, under **Manage** in the left menu, select **Authentication**.
 1. Select **Web**, then select **Add URI** under *Redirect URIs*.
 1. Add a new redirect URI, then select **Save**.
 
@@ -73,7 +73,7 @@ For more information on Application Registration, see [Quickstart: Register an a
 
 The application uses a client secret to authenticate itself in SSO workflow. You can add a client secret using the following steps:
 
-1. From your application overview, under *Manage* in the left menu, select **Certificates & secrets**.
+1. From your application overview, under **Manage** in the left menu, select **Certificates & secrets**.
 1. Select **Client secrets**, then select **New client secret**.
 1. Enter a description for the client secret, then set an expiration date.
 1. Select **Add**.

articles/spring-apps/enterprise/how-to-set-up-sso-with-azure-ad.md

@@ -284,7 +284,7 @@ To view the newly published accelerator, refresh Dev Tools Portal.
 
 ### Reference a fragment in your own accelerators
 
-Writing and maintaining accelerators can become repetitive and verbose as new accelerators are added. Some people create new projects by copying existing ones and making modifications, but this process can be tedious and error prone. To make the creation and maintenance of accelerators easier, Application Accelerator supports a feature named Composition that enables the reuse of parts of an accelerator, called *fragments*.
+Writing and maintaining accelerators can become repetitive and verbose as new accelerators are added. Some people create new projects by copying existing ones and making modifications, but this process can be tedious and error prone. To make the creation and maintenance of accelerators easier, Application Accelerator supports a feature named *Composition* that enables the reuse of parts of an accelerator, called *fragments*.
 
 Use the following steps to reference a fragment in your accelerator:
 

articles/spring-apps/enterprise/how-to-use-accelerator.md

@@ -149,7 +149,7 @@ This section describes how to view and try out APIs with schema definitions in A
 
 1. Configure routing rules to apps.
 
-   To create rules to access the app in Spring Cloud Gateway for Tanzu route configuration, save the following contents to the *sample.json* file.
+   To create rules to access the app in Spring Cloud Gateway for Tanzu route configuration, save the following contents to the **sample.json** file.
 
    ```json
    {

articles/spring-apps/enterprise/how-to-use-enterprise-api-portal.md

@@ -41,7 +41,7 @@ This section describes how to add, update, and manage API routes for apps that u
 
 The route configuration definition includes the following parts:
 
-- OpenAPI URI: This URI references an OpenAPI specification. You can use a public URI endpoint such as `https://petstore3.swagger.io/api/v3/openapi.json` or a constructed URI such as `http://<app-name>/{relative-path-to-OpenAPI-spec}`, where *`<app-name>`* is the name of an application in Azure Spring Apps that includes the API definition. Both OpenAPI 2.0 and OpenAPI 3.0 specs are supported. The specification displays in the API portal if enabled.
+- OpenAPI URI: This URI references an OpenAPI specification. You can use a public URI endpoint such as `https://petstore3.swagger.io/api/v3/openapi.json` or a constructed URI such as `http://<app-name>/{relative-path-to-OpenAPI-spec}`, where `<app-name>` is the name of an application in Azure Spring Apps that includes the API definition. Both OpenAPI 2.0 and OpenAPI 3.0 specs are supported. The specification displays in the API portal if enabled.
 - routes: A list of route rules to direct traffic to apps and apply filters.
 - protocol: The backend protocol of the application to which Spring Cloud Gateway routes traffic. The protocol's supported values are `HTTP` or `HTTPS`, and the default is `HTTP`. To secure traffic from Spring Cloud Gateway to your HTTPS-enabled application, you need to set the protocol to `HTTPS` in your route configuration.
 - app level routes: There are three route properties that you can configure at the app level to avoid repetition across all or most of the routes in the route configuration. The concrete routing rule overrides the app level routing rule for the same property. You can define the following properties at the app level: `predicates`, `filters`, and `ssoEnabled`. If you use the `OpenAPI URI` feature to define routes, the only app level routing property to support is `filters`.
@@ -116,7 +116,7 @@ The following table lists the route definitions. All the properties are optional
 
 Use the following steps to create a sample application using Spring Cloud Gateway.
 
-1. Use the following command to create a test application named *test-app* in Azure Spring Apps:
+1. Use the following command to create a test application named `test-app` in Azure Spring Apps:
 
    ```azurecli
    az spring app create \
@@ -144,7 +144,7 @@ Use the following steps to create a sample application using Spring Cloud Gatewa
 
 1. Create a rule to access the health check endpoint of the test app through Spring Cloud Gateway.
 
-   Save the following content to a *test-api.json* file. This configuration includes a RateLimit filter, which allows 20 requests every 10 seconds, and a RewritePath filter, which allows the request endpoint to reach the standard Spring Boot health check endpoint.
+   Save the following content to a **test-api.json** file. This configuration includes a RateLimit filter, which allows 20 requests every 10 seconds, and a RewritePath filter, which allows the request endpoint to reach the standard Spring Boot health check endpoint.
 
    ```json
    {

articles/spring-apps/enterprise/how-to-use-enterprise-spring-cloud-gateway.md

@@ -24,8 +24,8 @@ Use the following steps to create an Azure Spring Apps service instance:
    | Setting                   | Suggested value                   | Description                                                                                                                                                                                                                                                                                        |
    |---------------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
    | **Subscription**          | Your subscription name.           | The Azure subscription that you want to use for your server. If you have multiple subscriptions, choose the subscription in which you'd like to be billed for the resource.                                                                                                                        |
-   | **Resource group**        | *myresourcegroup*                 | A new resource group name or an existing one from your subscription.                                                                                                                                                                                                                               |
-   | **Name**                  | *myasa*                           | A unique name that identifies your Azure Spring Apps service. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number. |
+   | **Resource group**        | **myresourcegroup**                 | A new resource group name or an existing one from your subscription.                                                                                                                                                                                                                               |
+   | **Name**                  | **myasa**                           | A unique name that identifies your Azure Spring Apps service. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number. |
    | **Plan**                  | **Enterprise**                    | The pricing plan that determines the resource and cost associated with your instance.                                                                                                                                                                                                              |
    | **Region**                | The region closest to your users. | The location that is closest to your users.                                                                                                                                                                                                                                                        |
    | **Zone Redundant**        | Unselected                        | The option to create your Azure Spring Apps service in an Azure availability zone. This feature isn't currently supported in all regions.                                                                                                                                                          |