Polish

Closes gh-10636

spring-boot-project/spring-boot-docs/src/main/asciidoc/documentation-overview.adoc

@@ -123,7 +123,7 @@ When you're ready to push your Spring Boot application to production, we've got
 <<production-ready-features.adoc#production-ready-customizing-endpoints, Customization>>
 * *Connection options:*
 <<production-ready-features.adoc#production-ready-monitoring, HTTP>> |
-<<production-ready-features.adoc#production-ready-jmx, JMX>> |
+<<production-ready-features.adoc#production-ready-jmx, JMX>>
 * *Monitoring:*
 <<production-ready-features.adoc#production-ready-metrics, Metrics>> |
 <<production-ready-features.adoc#production-ready-auditing, Auditing>> |

spring-boot-project/spring-boot-docs/src/main/asciidoc/getting-started.adoc

@@ -252,7 +252,7 @@ endif::[]
 [[getting-started-installing-the-cli]]
 === Installing the Spring Boot CLI
 The Spring Boot CLI is a command line tool that can be used if you want to quickly
-prototype with Spring. It allows you to run http://groovy.codehaus.org/[Groovy] scripts,
+prototype with Spring. It allows you to run http://groovy-lang.org/[Groovy] scripts,
 which means that you have a familiar Java-like syntax, without so much boilerplate code.
 
 You don't need to use the CLI to work with Spring Boot but it's definitely the quickest

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

@@ -581,7 +581,7 @@ The `application.properties` example above will change the endpoint from `/appli
 NOTE: Unless the management port has been configured to
 <<production-ready-customizing-management-server-port,expose endpoints using a different
 HTTP port>>, `management.endpoints.web.base-path` is relative to `server.context-path`. If `management.server.port`
-is configured, `management.endpoints.web.base-path`, is relative to `management.server.context-path`.
+is configured, `management.endpoints.web.base-path`, is relative to `management.server.servlet.context-path`.