From aece7f15e86af574bf51229a52e77c00e660c663 Mon Sep 17 00:00:00 2001
From: buildmaster <buildmaster@springframework.org>
Date: Fri, 6 Sep 2019 12:29:43 +0000
Subject: [PATCH] Sync docs from master to gh-pages

---
 reference/html/README.html             | 2 +-
 reference/html/index.html              | 2 +-
 reference/html/spring-cloud-build.html | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/reference/html/README.html b/reference/html/README.html
index e4a3cbdd..d986e273 100644
--- a/reference/html/README.html
+++ b/reference/html/README.html
@@ -563,7 +563,7 @@ The order of plugin declaration is important!
 </table>
 </div>
 <div class="paragraph">
-<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
+<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
 </div>
 <div class="paragraph">
 <p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code>&lt;configprops.inclusionPattern&gt;spring.sleuth.*&lt;/configprops.inclusionPattern&gt;</code>).</p>
diff --git a/reference/html/index.html b/reference/html/index.html
index 2a834663..abaed6f2 100644
--- a/reference/html/index.html
+++ b/reference/html/index.html
@@ -564,7 +564,7 @@ The order of plugin declaration is important!
 </table>
 </div>
 <div class="paragraph">
-<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
+<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
 </div>
 <div class="paragraph">
 <p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code>&lt;configprops.inclusionPattern&gt;spring.sleuth.*&lt;/configprops.inclusionPattern&gt;</code>).</p>
diff --git a/reference/html/spring-cloud-build.html b/reference/html/spring-cloud-build.html
index 2a834663..abaed6f2 100644
--- a/reference/html/spring-cloud-build.html
+++ b/reference/html/spring-cloud-build.html
@@ -564,7 +564,7 @@ The order of plugin declaration is important!
 </table>
 </div>
 <div class="paragraph">
-<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
+<p>In order for the build to generate the <code>adoc</code> file with all your configuration properties, your <code>docs</code> module should contain all the dependencies on the classpath, that you would want to scan for configuration properties. The file will be output to <code>${docsModule}/src/main/asciidoc/_configprops.adoc</code> file (configurable via the <code>configprops.path</code> property).</p>
 </div>
 <div class="paragraph">
 <p>If you want to modify which of the configuration properties are put in the table, you can tweak the <code>configprops.inclusionPattern</code> pattern to include only a subset of the properties (e.g. <code>&lt;configprops.inclusionPattern&gt;spring.sleuth.*&lt;/configprops.inclusionPattern&gt;</code>).</p>