diff --git a/README.adoc b/README.adoc
index 2d5694e9..e667db17 100644
--- a/README.adoc
+++ b/README.adoc
@@ -72,7 +72,8 @@ The YAML and properties forms are coalesced into a single
 map, even if the origin of the values (reflected in the
 "propertySources" of the "standard" form) has multiple sources.
 
-Spring Cloud Config Server also supports multiple git repositories:
+Spring Cloud Config Server pulls configuration for remote clients
+from a git repository (which must be provided):
 
 ----
 spring:
@@ -81,20 +82,8 @@ spring:
 	  server:
 	    git:
 	      uri: https://github.com/spring-cloud-samples/config-repo
-	      repos:
-	        - patterns: *pattern
-	          uri: https://github.com/pattern1/config-repo
-	        - patterns: pattern*,*pattern1*
-	          uri: https://github.com/pattern2/config-repo
-	        - patterns: local*
-	          uri: file:/home/configsvc/config-repo
 ----
 
-In the above example, if {application} does not match to any of the patterns
-under "spring.cloud.config.server.git.repos", it will use the default uri
-defined under "spring.cloud.config.server.git.uri".  Acceptable pattern
-format is "*xxx", "xxx*", or "*xxx*".
-
 === Client Side Usage
 
 To use these features in an application, just build it as a Spring
diff --git a/docs/src/main/asciidoc/spring-cloud-config.adoc b/docs/src/main/asciidoc/spring-cloud-config.adoc
index b6f74970..0f595ccb 100644
--- a/docs/src/main/asciidoc/spring-cloud-config.adoc
+++ b/docs/src/main/asciidoc/spring-cloud-config.adoc
@@ -141,7 +141,17 @@ Git, but just loads the config files from the local classpath or file
 system (any static URL you want to point to with
 "spring.cloud.config.server.native.searchLocations"). To use the native
 profile just launch the Config Server with
-"spring.profiles.active=native". 
+"spring.profiles.active=native".
+
+WARNING: The default value of the `searchLocations` is identical to a
+local Spring Boot application (so
+`[classpath:/, classpath:/config, file:./, file:./config]`) which will
+expose the `application.properties` from the server to all clients.
+
+TIP: A filesystem backend is great for getting started quickly and
+for testing. To use it in production you need to be sure that the 
+file system is reliable, and shared across all instances of the
+Config Server.
 
 This repository implementation maps the `{label}` parameter of the
 HTTP resource to a suffix on the search path, so properties files are