diff --git a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
index d9251c3fdff..e244c735f0a 100644
--- a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
+++ b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
@@ -236,13 +236,13 @@ HTTP (if there is an server available). An HTTP endpoints can be customized furt
 creating a bean of type `MvcEndpoint`. Your `MvcEndpoint` is not a `@Controller` but it
 can use `@RequestMapping` (and `@Managed*`) to expose resources.
 
-TIP: If you are doing this as a library feature consider adding a configuration class to
-`/META-INF/spring.factories` under the key
-`org.springframework.boot.actuate.autoconfigure.EndpointWebMvcConfiguration`. If you do
-that then the endpoint will move to a child context with all the other MVC endpoints if
-your users ask for a separate management port or address. A configuration declared this
-way can be a `WebConfigurerAdapter` if it wants to add static resources (for instance) to
-the management endpoints.
+TIP: If you are doing this as a library feature consider adding a configuration class
+annoated with `@ManagementContextConfiguration` to `/META-INF/spring.factories` under the
+key `org.springframework.boot.actuate.autoconfigure.ManagementContextConfiguration`. If
+you do that then the endpoint will move to a child context with all the other MVC
+endpoints if your users ask for a separate management port or address. A configuration
+declared this way can be a `WebConfigurerAdapter` if it wants to add static resources (for
+instance) to the management endpoints.