Fix typos

spring-boot-admin-docs/src/main/asciidoc/client.adoc

@@ -41,7 +41,7 @@ To interact with JMX-beans in the admin UI you have to include https://jolokia.o
 ----
 
 [[loglevel-management]]
-=== Loglevel managment ===
+=== Loglevel management ===
 For applications using Spring Boot 1.5.x (or later) you can manage loglevels out-of-the-box.
 For applications using older versions of Spring Boot the loglevel management is only available for http://logback.qos.ch/[Logback]. It is accessed via JMX so <<jmx-bean-management, include Jolokia>> in your application. In addition you have configure Logback's `JMXConfigurator`:
 
@@ -118,7 +118,7 @@ spring.boot.admin.password
 | `false`
 
 | spring.boot.admin.client.metadata.*
-| Metadata key-value-pairs to be asscoiated with this instance.
+| Metadata key-value-pairs to be associated with this instance.
 |
 |===
 

spring-boot-admin-docs/src/main/asciidoc/faqs.adoc

 [[faqs]]
 == FAQs ==
-[qanda]
+[q-and-a]
 Can I include spring-boot-admin into my business application?::
   *tl;dr* You can, but you shouldn't. +
   You can set `spring.boot.admin.context-path` to alter the path where the UI and REST-API is served, but depending on the complexity of your application you might get in trouble. On the other hand in my opinion it makes no sense for an application to monitor itself. In case your application goes down your monitoring tool also does.

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

@@ -69,7 +69,7 @@ Each application that wants to register has to include the Spring Boot Admin Cli
 .application.yml
 ----
 spring.boot.admin.url: http://localhost:8080  #<1>
-managment.security.enabled: false  #<2>
+management.security.enabled: false  #<2>
 ----
 <1> The URL of the Spring Boot Admin Server to register at.
 <2> Since Spring Boot 1.5.x all endpoints are secured by default. For the sake of brevity we're disabling the security for now. Have a look at the <<securing-spring-boot-admin,security section>> on how to deal with secured endpoints.

spring-boot-admin-docs/src/main/asciidoc/server-discovery.adoc

@@ -21,7 +21,7 @@ NOTE: When using Eureka, the `healthCheckUrl` known to Eureka is used for health
 | `true`
 
 | spring.boot.admin.discovery.converter.management-context-path
-| Will be appended to the service-url of the discovered service when the managment-url is converted by the `DefaultServiceInstanceConverter`.
+| Will be appended to the service-url of the discovered service when the management-url is converted by the `DefaultServiceInstanceConverter`.
 |
 
 | spring.boot.admin.discovery.converter.health-endpoint-path
@@ -42,15 +42,15 @@ user.password
 | Credentials being used to access the endpoints.
 |
 
-| managment.port
+| management.port
 | The port is substituted in the service URL and will be used for accessing the actuator endpoints.
 |
 
-| managment.path
-| The path is appendend to the service URL and will be used for accessing the actuator endpoints.
+| management.path
+| The path is appended to the service URL and will be used for accessing the actuator endpoints.
 | `${spring.boot.admin.discovery.converter.mangement-context-path}`
 
 | health.path
-| The path is appendend to the service URL and will be used for the health-checking. Ignored by the `EurekaServiceInstanceConverter`.
+| The path is appended to the service URL and will be used for the health-checking. Ignored by the `EurekaServiceInstanceConverter`.
 | `${spring.boot.admin.discovery.converter.health-endpoint}`
 |===