Polish Actuator doc

Closes gh-10861

spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc

@@ -2242,19 +2242,6 @@ of how to register handlers in the servlet container.
 
 
 
-[[howto-use-actuator-with-jersey]]
-=== Actuator and Jersey
-Actuator HTTP endpoints are available only for Spring MVC-based applications. If you want
-to use Jersey and still use the actuator, you need to enable Spring MVC (by depending
-on `spring-boot-starter-web`, for example). By default, both Jersey and the Spring MVC
-dispatcher servlet are mapped to the same path (`/`). You need to change the path for
-one of them (by configuring `server.servlet.path` for Spring MVC or
-`spring.jersey.application-path` for Jersey). For example, if you add
-`server.servlet.path=/system` into `application.properties`, the actuator HTTP endpoints
-are available under `/system`.
-
-
-
 [[howto-security]]
 == Security
 

spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -660,11 +660,13 @@ additional entry:
 
 [[production-ready-monitoring]]
 == Monitoring and Management over HTTP
-If you are developing a Spring MVC application, Spring Boot Actuator auto-configures all
+If you are developing a web application, Spring Boot Actuator auto-configures all
 enabled endpoints to be exposed over HTTP. The default convention is to use the `id` of
 the endpoint with a prefix of `/actuator` as the URL path. For example, `health` is
 exposed as `/actuator/health`.
 
+TIP: Actuator is supported natively with Spring MVC, Spring WebFlux and Jersey.
+
 
 
 [[production-ready-customizing-management-server-context-path]]