Document the new local config YAML features

Also remove --git-url command line flag (since you can
put it in configserver.yml now).

docs/src/main/asciidoc/intro.adoc

@@ -4,7 +4,7 @@ Cloud]. You can write Groovy scripts to run Spring Cloud component
 applications (e.g. `@EnableEurekaServer`). You can also easily do
 things like encryption and decryption to support Spring Cloud Config
 clients with secret configuration values. With the Launcher CLI you
-can also launch services like Eureka, Zipkin, Config Server
+can launch services like Eureka, Zipkin, Config Server
 conveniently all at once from the command line (very useful at
 development time).
 

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

@@ -51,6 +51,23 @@ Summary of supported deployables:
 | Zipkin Server with UI for visualizing traces. Stores span data in memory and accepts them via HTTP POST of JSON data.
 |===
 
+Each of these apps can be configured using a local YAML file with the same name (in the current
+working directory or a subdirectory called "config"). E.g. in `configserver.yml` you might want to
+do something like this to locate a local git repository for the backend:
+
+.configserver.yml
+[source,yaml,indent=0]
+----
+spring:
+  profiles:
+    active: git
+  cloud:
+    config:
+      server:
+        git:
+          uri: file://${user.home}/dev/demo/config-repo
+----
+
 == Writing Groovy Scripts and Running Applications
 
 Spring Cloud CLI has support for most of the Spring Cloud declarative