From 82d41c1e83dc0596fd8581fd600f0fb5f3663998 Mon Sep 17 00:00:00 2001
From: Andy Wilkinson <awilkinson@pivotal.io>
Date: Fri, 26 Jan 2018 15:41:13 +0000
Subject: [PATCH] Reinstate information about web endpoints' default URL
 mapping

Closes gh-11755
---
 .../src/main/asciidoc/production-ready-features.adoc         | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
index 4cfe10b6b1..07538dfbad 100644
--- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
+++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
@@ -56,7 +56,10 @@ includes a number of built-in endpoints and lets you add your own. For example,
 Each individual endpoint can be <<production-ready-endpoints-enabling-endpoints, enabled
 or disabled>>. This controls whether or not the endpoint is created and its bean exists in
 the application context. To be remotely accessible an endpoint also has to be
-<<production-ready-endpoints-exposing-endpoints, exposed>>.
+<<production-ready-endpoints-exposing-endpoints, exposed via JMX or HTTP>>. Most
+applications choose HTTP, where the ID of the endpoint along with a prefix of `/actuator`
+is mapped to a URL. For example, by default, the `health` endpoint is mapped to
+`/actuator/health`.
 
 The following technology-agnostic endpoints are available: