Merge pull request #234241 from KarlErickson/taoxu0903-patch-4

edit "Update how-to-enterprise-deploy-static-file.md #234212"

Author: prmerger-automator[bot]

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

@@ -15,7 +15,7 @@ ms.custom: event-tier1-build-2022, devx-track-java
 > [!NOTE]
 > Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
 
-**This article applies to:** ❌ Basic/Standard tier ✔️ Enterprise tier
+**This article applies to:** ❌ Basic/Standard ✔️ Enterprise
 
 This article shows you how to deploy your static files to Azure Spring Apps Enterprise tier using the Tanzu Web Servers buildpack. This approach is useful if you have applications that are purely for holding static files like HTML, CSS, or front-end applications built with the JavaScript framework of your choice. You can directly deploy these applications with an automatically configured web server (HTTPD and NGINX) to serve those assets.
 
@@ -24,19 +24,20 @@ This article shows you how to deploy your static files to Azure Spring Apps Ente
 - An already provisioned Azure Spring Apps Enterprise tier instance. For more information, see [Quickstart: Build and deploy apps to Azure Spring Apps using the Enterprise tier](quickstart-deploy-apps-enterprise.md).
 - One or more applications running in Azure Spring Apps. For more information on creating apps, see [How to Deploy Spring Boot applications from Azure CLI](./how-to-launch-from-source.md).
 - [Azure CLI](/cli/azure/install-azure-cli), version 2.45.0 or higher.
-- Your static files or dynamic front-end application.
+- Your static files or dynamic front-end application - for example, a React app.
 
 ## Deploy your static files
 
 You can deploy static files to Azure Spring Apps using NGINX or HTTPD web servers in the following ways:
 
 - You can deploy static files directly. Azure Spring Apps automatically configures the specified web server to serve the static files.
-- You can create your front-end application in the JavaScript framework of your choice, and then deploy your dynamic front-end application as static content.
-- You can create a server configuration file to customize the web server.
+- You can create your front-end application in the JavaScript framework of your choice, and then deploy your dynamic front-end application from source code. Azure Spring Apps builds your app into static content and uses your configured web server to serve the static files.
+
+You can also create a server configuration file to customize the web server.
 
 ### Deploy static files directly
 
-Use the following command to deploy static files directly using an auto-generated default server configuration file.
+Use the following command to deploy static files directly using an autogenerated default server configuration file.
 
 ```azurecli
 az spring app deploy
@@ -47,11 +48,11 @@ az spring app deploy
     --build-env BP_WEB_SERVER=nginx
 ```
 
-For more information, see the [Configure an auto-generated server configuration file](#configure-an-auto-generated-server-configuration-file) section of this article.
+For more information, see the [Configure an autogenerated server configuration file](#configure-an-autogenerated-server-configuration-file) section of this article.
 
 ### Deploy your front-end application as static content
 
-Use the following command to deploy a dynamic front-end application as static content.
+Use the following command to deploy a dynamic front-end application from source code.
 
 ```azurecli
 az spring app deploy
@@ -84,20 +85,20 @@ For more information, see the [Using a customized server configuration file](#us
 The [Paketo buildpacks samples](https://github.com/paketo-buildpacks/samples/tree/main/web-servers) demonstrate common use cases for several different application types, including the following use cases:
 
 - 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/javascript-frontend-sample) into static files that can be served by a web server. Use the following steps:
+- Using Node Package Manager to build a [React app](https://github.com/paketo-buildpacks/samples/tree/main/web-servers/javascript-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. 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.
 - Serving static files with your own server configuration file, using either [HTTPD](https://github.com/paketo-buildpacks/samples/tree/main/web-servers/httpd-sample) or [NGINX](https://github.com/paketo-buildpacks/samples/tree/main/web-servers/nginx-sample).
 
-## Configure an auto-generated server configuration file
+## Configure an autogenerated server configuration file
 
-You can use environment variables to modify the auto-generated server configuration file. The following table shows supported environment variables.
+You can use environment variables to modify the autogenerated server configuration file. The following table shows supported environment variables.
 
 | 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 auto-generated server configuration file.        |
+| `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.                                                                        |