Made requested changes

Including removing the ==== fences around code blocks.

Author: Jay Bryant

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/cloud-foundry.adoc

@@ -15,14 +15,12 @@ To use the endpoint, you must pass a valid UAA token with the request.
 === Disabling Extended Cloud Foundry Actuator Support
 If you want to fully disable the `/cloudfoundryapplication` endpoints, you can add the following setting to your `application.properties` file:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
 	  cloudfoundry:
 	    enabled: false
 ----
-====
 
 
 
@@ -31,14 +29,12 @@ If you want to fully disable the `/cloudfoundryapplication` endpoints, you can a
 By default, the security verification for `/cloudfoundryapplication` endpoints makes SSL calls to various Cloud Foundry services.
 If your Cloud Foundry UAA or Cloud Controller services use self-signed certificates, you need to set the following property:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
 	  cloudfoundry:
 	    skip-ssl-validation: true
 ----
-====
 
 
 
@@ -51,9 +47,7 @@ If you expect the Cloud Foundry endpoints to always be available at `/cloudfound
 The configuration differs, depending on the web server in use.
 For Tomcat, you can add the following configuration:
 
-====
 [source,java,indent=0,subs="verbatim"]
 ----
 include::{docs-java}/actuator/cloudfoundry/customcontextpath/MyCloudFoundryConfiguration.java[]
 ----
-====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/enabling.adoc

@@ -11,7 +11,6 @@ Actuators can generate a large amount of motion from a small change.
 
 To add the actuator to a Maven-based project, add the following '`Starter`' dependency:
 
-====
 [source,xml,indent=0,subs="verbatim"]
 ----
 	<dependencies>
@@ -21,15 +20,12 @@ To add the actuator to a Maven-based project, add the following '`Starter`' depe
 		</dependency>
 	</dependencies>
 ----
-====
 
 For Gradle, use the following declaration:
 
-====
 [source,gradle,indent=0,subs="verbatim"]
 ----
 	dependencies {
 		implementation 'org.springframework.boot:spring-boot-starter-actuator'
 	}
 ----
-====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/endpoints.adoc

@@ -1,7 +1,8 @@
 [[actuator.jmx]]
 == Monitoring and Management over JMX
 Java Management Extensions (JMX) provide a standard mechanism to monitor and manage applications.
-By default, this feature is not enabled. You can turn it on by setting the configprop:spring.jmx.enabled[] configuration property to `true`.
+By default, this feature is not enabled.
+You can turn it on by setting the configprop:spring.jmx.enabled[] configuration property to `true`.
 Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of `mbeanServer`.
 Any of your beans that are annotated with Spring JMX annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`) are exposed to it.
 
@@ -26,7 +27,6 @@ To solve this problem, you can set the configprop:spring.jmx.unique-names[] prop
 You can also customize the JMX domain under which endpoints are exposed.
 The following settings show an example of doing so in `application.properties`:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	spring:
@@ -37,15 +37,13 @@ The following settings show an example of doing so in `application.properties`:
 	    jmx:
 	      domain: "com.example.myapp"
 ----
-====
 
 
 
 [[actuator.jmx.disable-jmx-endpoints]]
 === Disabling JMX Endpoints
 If you do not want to expose endpoints over JMX, you can set the configprop:management.endpoints.jmx.exposure.exclude[] property to `*`, as the following example shows:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
@@ -54,7 +52,6 @@ If you do not want to expose endpoints over JMX, you can set the configprop:mana
 	      exposure:
 	        exclude: "*"
 ----
-====
 
 
 
@@ -64,15 +61,13 @@ Jolokia is a JMX-HTTP bridge that provides an alternative method of accessing JM
 To use Jolokia, include a dependency to `org.jolokia:jolokia-core`.
 For example, with Maven, you would add the following dependency:
 
-====
 [source,xml,indent=0,subs="verbatim"]
 ----
 	<dependency>
 		<groupId>org.jolokia</groupId>
 		<artifactId>jolokia-core</artifactId>
 	</dependency>
 ----
-====
 
 You can then expose the Jolokia endpoint by adding `jolokia` or `*` to the configprop:management.endpoints.web.exposure.include[] property.
 You can then access it by using `/actuator/jolokia` on your management HTTP server.
@@ -89,7 +84,6 @@ Jolokia has a number of settings that you would traditionally configure by setti
 With Spring Boot, you can use your `application.properties` file.
 To do so, prefix the parameter with `management.endpoint.jolokia.config.`, as the following example shows:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
@@ -98,20 +92,17 @@ To do so, prefix the parameter with `management.endpoint.jolokia.config.`, as th
 	      config:
 	        debug: true
 ----
-====
 
 
 
 [[actuator.jmx.jolokia.disabling]]
 ==== Disabling Jolokia
 If you use Jolokia but do not want Spring Boot to configure it, set the configprop:management.endpoint.jolokia.enabled[] property to `false`, as follows:
 
-====
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
 	  endpoint:
 	    jolokia:
 	      enabled: false
 ----
-====

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/jmx.adoc

@@ -21,13 +21,11 @@ These levels can be one of:
 === Configure a Logger
 To configure a given logger, `POST` a partial entity to the resource's URI, as the following example shows:
 
-====
 [source,json,indent=0,subs="verbatim"]
 ----
 	{
 		"configuredLevel": "DEBUG"
 	}
 ----
-====
 
 TIP: To "`reset`" the specific level of the logger (and use the default configuration instead), you can pass a value of `null` as the `configuredLevel`.