doc: add document

Author: 黎木健

docs/src/main/asciidoc/spring-cloud-zookeeper.adoc

@@ -486,19 +486,22 @@ https://github.com/spring-cloud/spring-cloud-config[Config Server and Client].
 Configuration is loaded into the Spring Environment during the special "`bootstrap`"
 phase. Configuration is stored in the `/config` namespace by default. Multiple
 `PropertySource` instances are created, based on the application's name and the active
-profiles, to mimic the Spring Cloud Config order of resolving properties. For example, an
-application with a name of `testApp` and with the `dev` profile has the following property
-sources created for it:
+profiles, to mimic the Spring Cloud Config order of resolving properties. What's more, it
+supports multiple business namespaces through `defaultContext`. For example, an application
+with a name of `testApp` and with the `dev`, with `namespace1,namespace2` defaultContext
+profile has the following property sources created for it:
 
 * `config/testApp,dev`
 * `config/testApp`
-* `config/application,dev`
-* `config/application`
+* `config/namespace1,dev`
+* `config/namespace1`
+* `config/namespace2,dev`
+* `config/namespace2`
 
 The most specific property source is at the top, with the least specific at the bottom.
-Properties in the `config/application` namespace apply to all applications that use
-zookeeper for configuration. Properties in the `config/testApp` namespace are available
-only to the instances of the service named `testApp`.
+Properties in the `config/testApp` namespace are only available to the instances of the service
+named "testApp". If you want to share the configuration with other applications, you can
+configure the same `defaultContext` like `namespace1` or `namespace2`.
 
 Configuration is currently read on startup of the application. Sending a HTTP `POST`
 request to `/refresh` causes the configuration to be reloaded. Watching the configuration

spring-cloud-zookeeper-config/src/main/java/org/springframework/cloud/zookeeper/config/ZookeeperPropertySourceLocator.java

@@ -41,9 +41,9 @@
  * "bootstrap" phase. Configuration is stored in the {@code /config} namespace by default.
  * Multiple {@code PropertySource} instances are created based on the application's name
  * and the active profiles that mimics the Spring Cloud Config order of resolving
- * properties.What's more,it supports multiple business namespaces through {@code defaultContext}.
- * For example, an application with the name "testApp",and with the "dev"
- * profile,with "namespace1,namespace2" defaultContext will have the following property sources
+ * properties. What's more,it supports multiple business namespaces through {@code defaultContext}.
+ * For example, an application with the name "testApp", and with the "dev"
+ * profile, with "namespace1,namespace2" defaultContext will have the following property sources
  * created:
  *
  * <pre>{@code
@@ -55,11 +55,9 @@
  * config/namespace2
  * }</pre>
  *
- * The most specific property source is at the top, with the least specific at the bottom.
- * Properties is the {@code config/application} namespace are applicable to all
- * applications using zookeeper for configuration. Properties in the
- * {@code config/testApp} namespace are only available to the instances of the service
- * named "testApp".
+ * Properties in the {@code config/testApp} namespace are only available to the instances of the service
+ * named "testApp". If you want to share the configuration with other applications, you can configure the
+ * same {@code defaultContext} like "namespace1" or "namespace2".
  *
  * @author Spencer Gibb
  * @author lemonJ