Merge pull request #294067 from JoshTheTechWriter/italics-to-bold-5

First commit of fifth batch of files.

Author: v-shils

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.
@@ -240,10 +240,10 @@ You can use environment variables to modify the autogenerated server configurati
 
 | Environment Variable              | Supported Value                                                | Description                                                                                                                                                         |
 |-----------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `BP_WEB_SERVER`                   | *nginx* or *httpd*                                             | Specifies the web server type, either *nginx* for Nginx or *httpd* for Apache HTTP server. Required when using the autogenerated server configuration file.        |
-| `BP_WEB_SERVER_ROOT`              | An absolute file path or a file path relative to */workspace*. | Sets the root directory for the static files. The default is `public`.                                                                                              |
-| `BP_WEB_SERVER_ENABLE_PUSH_STATE` | *true* or *false*                                              | Enables push state routing for your application. Regardless of the route that is requested, *index.html* is always served. Useful for single-page web applications. |
-| `BP_WEB_SERVER_FORCE_HTTPS`       | *true* or *false*                                              | Enforces HTTPS for server connections by redirecting all requests to use the HTTPS protocol.                                                                        |
+| `BP_WEB_SERVER`                   | `nginx` or `httpd`                                             | Specifies the web server type, either `nginx` for Nginx or `httpd` for Apache HTTP server. Required when using the autogenerated server configuration file.        |
+| `BP_WEB_SERVER_ROOT`              | An absolute file path or a file path relative to **/workspace**. | Sets the root directory for the static files. The default is `public`.                                                                                              |
+| `BP_WEB_SERVER_ENABLE_PUSH_STATE` | `true` or `false`                                              | Enables push state routing for your application. Regardless of the route that is requested, **index.html** is always served. Useful for single-page web applications. |
+| `BP_WEB_SERVER_FORCE_HTTPS`       | `true` or `false`                                              | Enforces HTTPS for server connections by redirecting all requests to use the HTTPS protocol.                                                                        |
 
 The following environment variables aren't supported.
 
@@ -257,8 +257,8 @@ You can configure web server by using a customized server configuration file. Th
 
 | Web server  | Default configuration file path                        | How to customize server configuration file path                                                                            |
 |-------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
-| nginx       | *nginx.conf*  under the root path of your source code. | Use environment variable `BP_NGINX_CONF_LOCATION` to specify the configuration file name. Place the file under the root path of your source code. |
-| httpd       | *httpd.conf* under the root path of your source code.  | Not supported.                                                                                                       |
+| `nginx`       | **nginx.conf**  under the root path of your source code. | Use environment variable `BP_NGINX_CONF_LOCATION` to specify the configuration file name. Place the file under the root path of your source code. |
+| `httpd`       | **httpd.conf** under the root path of your source code.  | Not supported.                                                                                                       |
 
 
 Your configuration file must conform to the restrictions described in the following table.
@@ -267,7 +267,7 @@ Your configuration file must conform to the restrictions described in the follow
 |----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------|
 | Listening port                               | Web server must listen on port 8080. The service checks the port on TCP for readiness and whether it's live. You must use the templated variable `PORT` in the configuration file. The appropriate port number is injected when the web server is launched. | `listen {{PORT}}`                                          | `Listen "${PORT}"`                            |
 | Log path                                     | Config log path to the console.                                                                                                                                                                                                                             | `access_log /dev/stdout`, `error_log stderr`               | `ErrorLog /proc/self/fd/2`                    |
-| File path with write permission              | Web server is granted write permission to the */tmp* directory. Configuring the full path requires write permission under the */tmp* directory.                                                                                                             | For example: *client_body_temp_path /tmp/client_body_temp* |                                               |
+| File path with write permission              | Web server is granted write permission to the **/tmp** directory. Configuring the full path requires write permission under the **/tmp** directory.                                                                                                             | For example: **client_body_temp_path/tmp/client_body_temp** |                                               |
 | Maximum accepted body size of client request | Web server is behind the gateway. The maximum accepted body size of the client request is set to 500 m in the gateway and the value for web server must be less than 500 m.                                                                                 | `client_max_body_size` should be less than 500 m.          | `LimitRequestBody` should be less than 500 m. |
 
 ## Buildpack bindings
@@ -284,14 +284,14 @@ Your deployment of static files to an Azure Spring Apps Enterprise instance may
 - `ERROR: Please check that you're running against the correct path.`
 - `ERROR: failed to detect: no buildpacks participating`
 
-The root cause of these errors is that the web server type isn't specified. To resolve these errors, set the environment variable `BP_WEB_SERVER` to *nginx* or *httpd*.
+The root cause of these errors is that the web server type isn't specified. To resolve these errors, set the environment variable `BP_WEB_SERVER` to `nginx` or `httpd`.
 
 The following table describes common deployment errors when you deploy static files to Azure Spring Apps Enterprise.
 
 | Error message                                                                     | Root cause                                                          | Solution                                                                                                                                                                                                                                                                          |
 |-----------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `112404: Exit code 0: purposely stopped, please refer to https://aka.ms/exitcode` | The web server failed to start.                                     | Validate your server configuration file to see if there's a configuration error. Then, check whether your configuration file conforms to the restrictions described in the [Use a customized server configuration file](#use-a-customized-server-configuration-file) section. |
-| `mkdir() "/var/client_body_temp" failed (13: Permission denied)`                  | The web server doesn't have write permission to the specified path. | Configure the path under the directory */tmp*; for example: */tmp/client_body_temp*.                                                                                                                                                                                              |
+| `mkdir() "/var/client_body_temp" failed (13: Permission denied)`                  | The web server doesn't have write permission to the specified path. | Configure the path under the directory **/tmp**; for example: **/tmp/client_body_temp**.                                                                                                                                                                                              |
 
 ## Next steps
 

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
    {