updates

Author: craigshoemaker

articles/container-apps/java-spring-cloud-config-server-usage.md

@@ -11,8 +11,12 @@ ms.author: cshoe
 
 # Configure settings for the Spring Cloud Configure Server component in Azure Container Apps (preview)
 
+Spring Cloud Config Server provides a centralized location to make configuration data available to multiple applications. Use the following guidance to learn how to configure and manage your Spring Cloud Config Server component.
+
 ## Show
 
+You can show the details of an individual component by name using the `show` command.
+
 ```azurecli
 az containerapp env java-component spring-cloud-config show \
   --environment <ENVIRONMENT_NAME> \
@@ -22,6 +26,8 @@ az containerapp env java-component spring-cloud-config show \
 
 ## List
 
+You can list all registered Java components using the `list` command.
+
 ```azurecli
 az containerapp env java-component list \
   --environment <ENVIRONMENT_NAME> \
@@ -30,6 +36,8 @@ az containerapp env java-component list \
 
 ## Bind
 
+Use the `--bind` parameter of the `update` command to create a connection between the Spring Cloud Config Server component and your container app.
+
 ```azurecli
 az containerapp update \
   --name <CONTAINER_APP_NAME> \
@@ -39,6 +47,8 @@ az containerapp update \
 
 ## Unbind
 
+To break the connection between your container app and the Spring Cloud Config Server component, use the the `--unbind` parameter of the `update` command.
+
 ``` azurecli
 az containerapp update \
   --name <CONTAINER_APP_NAME> \
@@ -52,8 +62,6 @@ The `az containerapp update` command uses the `--configuration` parameter to con
 
 The following table lists the different configuration values available.
 
-### Git backend configurations
-
 The following configuration settings are available on the `spring.cloud.config.server.git` configuration property.
 
 | Name | Property path | Description |
@@ -78,43 +86,31 @@ The following configuration settings are available on the `spring.cloud.config.s
 
 ### Common configurations
 
-### Logging configurations
-
-- [**logging.level.**\*](https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-custom-log-levels)
-
-- [**logging.group.**\*](https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-custom-log-groups)
-
-  Any other configurations under the `logging.*` namespace should be forbidden. For example, disallow writing log files by using `logging.file`.
+- logging related configurations
+  - [**logging.level.***](https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-custom-log-levels)
+  - [**logging.group.***](https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-custom-log-groups)
+  - Any other configurations under logging.* namespace should be forbidden, for example, writing log files by using `logging.file` should be forbidden.
 
 - **spring.cloud.config.server.overrides**
-
   - Extra map for a property source to be sent to all clients unconditionally.
 
 - **spring.cloud.config.override-none**
-
-  You can change the priority of all overrides in the client to be more like default values. The setting allows applications to supply their own values in environment variables or System properties. Values are set with the `spring.cloud.config.override-none=true` flag (the default is `false`) in the remote repository.
+  - You can change the priority of all overrides in the client to be more like default values, letting applications supply their own values in environment variables or System properties, by setting the spring.cloud.config.override-none=true flag (the default is false) in the remote repository.
 
 - **spring.cloud.config.allow-override**
-
-  If you enable config first bootstrap, you allow client applications to override configuration from the config server by placing two properties within the application's configuration coming from the config server.
+  - If you enable config first bootstrap, you can allow client applications to override configuration from the config server by placing two properties within the applications configuration coming from the config server.
 
 - **spring.cloud.config.server.health.**
-
-  You can configure the Health Indicator to check more applications along with custom profiles and custom labels
+  - You can configure the Health Indicator to check more applications along with custom profiles and custom labels
 
 - **spring.cloud.config.server.accept-empty**
+  - You can set `spring.cloud.config.server.accept-empty` to `false` so that the server returns a HTTP `404` status, if the application is not found. By default, this flag is set to `true`.
 
-  You can set `spring.cloud.config.server.accept-empty` to `false` so that the server returns an HTTP `404` status if the application isn't found. By default, this flag is set to `true`.
-
-### Encryption and decryption (symmetric)
-
-- **encrypt.key**
-
-  Using a symmetric key is often most convenient, as it's a single property value to configure.
-
-- **spring.cloud.config.server.encrypt.enabled**
-
-  You can set this value to `false`, to disable server-side decryption.
+- **Encryption and decryption (symmetric)**
+  - **encrypt.key**
+    - It is convenient to use a symmetric key since it is a single property value to configure.
+  - **spring.cloud.config.server.encrypt.enabled**
+    - You can set this to `false`, to disable server-side decryption.
 
 ## Spring Cloud Config Server refresh
 

articles/container-apps/java-spring-cloud-config-server.md

@@ -11,7 +11,9 @@ ms.author: cshoe
 
 # Connect to a managed Spring Cloud Config Server in Azure Container Apps (preview)
 
-Spring Cloud Config Server provides a centralized location to make configuration data available to multiple applications. In this article, you learn to connect an app hosted in Azure Container Apps to a Java Spring Cloud Config Server instance. The Spring Cloud Config Server component uses a GitHub repository as the source for configuration settings. Configuration values are made available to your container app via a configuration binding. A binding is a connection established between the Config Server and your app. As values change in the configuration, they automatically flow to your application, all without requiring you to recompile or redeploy your application.
+Spring Cloud Config Server provides a centralized location to make configuration data available to multiple applications. In this article, you learn to connect an app hosted in Azure Container Apps to a Java Spring Cloud Config Server instance.
+
+The Spring Cloud Config Server component uses a GitHub repository as the source for configuration settings. Configuration values are made available to your container app via a binding between the component and your container app. As values change in the configuration server, they automatically flow to your application, all without requiring you to recompile or redeploy your application.
 
 In this tutorial, you learn to: