diff --git a/multi/multi__spring_cloud_config_server.html b/multi/multi__spring_cloud_config_server.html
index d264133b..52e92ecb 100644
--- a/multi/multi__spring_cloud_config_server.html
+++ b/multi/multi__spring_cloud_config_server.html
@@ -82,7 +82,7 @@ git branch or tag name contains a slash ("/") then the label in the
HTTP URL should be specified with the special string "(_)" instead (to
avoid ambiguity with other URL paths). For example, if the label is
foo/bar, replacing the slash would result in a label that looks like
-foo(_)bar. The inclusion of the special string "(\_)" can also be
+foo(_)bar. The inclusion of the special string "(_)" can also be
applied to the {application} parameter. Be careful with the brackets
in the URL if you are using a command line client like curl (e.g.
escape them from the shell with quotes '').
Spring Cloud Config Server supports a git repository URL with @@ -95,7 +95,7 @@ using (for example):
server: git: uri: https://github.com/myorg/{application}
or a "one repo per profile" policy using a similar pattern but with
-{profile}.
Additionally, using the special string "(\_)" within your
+{profile}.
Additionally, using the special string "(_)" within your
{application} parameters can enable support for multiple
organizations (for example):
spring: cloud: @@ -103,7 +103,7 @@ organizations (for example):server: git: uri: https://github.com/{application}where
{application}is provided at request time in the format -"organization(\_)application".
There is also support for more complex requirements with pattern +"organization(_)application".
There is also support for more complex requirements with pattern
matching on the application and profile name. The pattern format is a
comma-separated list of {application}/{profile} names with wildcards
(where a pattern beginning with a wildcard may need to be
diff --git a/single/spring-cloud-config.html b/single/spring-cloud-config.html
index dcae4be8..10041f63 100644
--- a/single/spring-cloud-config.html
+++ b/single/spring-cloud-config.html
@@ -184,7 +184,7 @@ git branch or tag name contains a slash ("/") then the label in the
HTTP URL should be specified with the special string "(_)" instead (to
avoid ambiguity with other URL paths). For example, if the label is
foo/bar, replacing the slash would result in a label that looks like
-foo(_)bar. The inclusion of the special string "(\_)" can also be
+foo(_)bar. The inclusion of the special string "(_)" can also be
applied to the {application} parameter. Be careful with the brackets
in the URL if you are using a command line client like curl (e.g.
escape them from the shell with quotes '').
Spring Cloud Config Server supports a git repository URL with @@ -197,7 +197,7 @@ using (for example):
server: git: uri: https://github.com/myorg/{application}
or a "one repo per profile" policy using a similar pattern but with
-{profile}.
Additionally, using the special string "(\_)" within your
+{profile}.
Additionally, using the special string "(_)" within your
{application} parameters can enable support for multiple
organizations (for example):
spring: cloud: @@ -205,7 +205,7 @@ organizations (for example):server: git: uri: https://github.com/{application}where
{application}is provided at request time in the format -"organization(\_)application".
There is also support for more complex requirements with pattern +"organization(_)application".
There is also support for more complex requirements with pattern
matching on the application and profile name. The pattern format is a
comma-separated list of {application}/{profile} names with wildcards
(where a pattern beginning with a wildcard may need to be
diff --git a/spring-cloud-config.xml b/spring-cloud-config.xml
index 2fd3ce5f..e3cf1a44 100644
--- a/spring-cloud-config.xml
+++ b/spring-cloud-config.xml
@@ -274,10 +274,10 @@ working copy as a cache.