Polish .adoc source files

Author: wilkinsona

docs/src/docs/asciidoc/configuration.adoc

@@ -3,11 +3,15 @@
 
 This section covers how to configure Spring REST Docs.
 
+
+
 [[configuration-uris]]
 === Documented URIs
 
 This section covers configuring documented URIs.
 
+
+
 [[configuration-uris-mockmvc]]
 ==== MockMvc URI Customization
 
@@ -30,12 +34,10 @@ This configuration is applied by `MockMvcRestDocumentationConfigurer`.
 You can use its API to change one or more of the defaults to suit your needs.
 The following example shows how to do so:
 
-====
 [source,java,indent=0]
 ----
 include::{examples-dir}/com/example/mockmvc/CustomUriConfiguration.java[tags=custom-uri-configuration]
 ----
-====
 
 NOTE: If the port is set to the default for the configured scheme (port 80 for HTTP or port 443 for HTTPS), it is omitted from any URIs in the generated snippets.
 
@@ -59,13 +61,11 @@ When using WebTestClient, the default base for URIs documented by Spring REST Do
 You can customize this base by using the {spring-framework-api}/org/springframework/test/web/reactive/server/WebTestClient.Builder.html#baseUrl-java.lang.String-[ `baseUrl(String)` method on `WebTestClient.Builder`].
 The following example shows how to do so:
 
-====
 [source,java,indent=0]
 ----
 include::{examples-dir}/com/example/webtestclient/CustomUriConfiguration.java[tags=custom-uri-configuration]
 ----
 <1> Configure the base of documented URIs to be `https://api.example.com`.
-====
 
 
 
@@ -76,7 +76,6 @@ The default snippet encoding is `UTF-8`.
 You can change the default snippet encoding by using the `RestDocumentationConfigurer` API.
 For example, the following examples use `ISO-8859-1`:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -94,7 +93,6 @@ include::{examples-dir}/com/example/webtestclient/CustomEncoding.java[tags=custo
 ----
 include::{examples-dir}/com/example/restassured/CustomEncoding.java[tags=custom-encoding]
 ----
-====
 
 TIP: When Spring REST Docs converts the content of a request or a response to a `String`, the `charset` specified in the `Content-Type` header is used if it is available.
 In its absence, the JVM's default `Charset` is used.
@@ -110,7 +108,6 @@ Markdown is also supported out of the box.
 You can change the default format by using the `RestDocumentationConfigurer` API.
 The following examples show how to do so:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -128,7 +125,6 @@ include::{examples-dir}/com/example/webtestclient/CustomFormat.java[tags=custom-
 ----
 include::{examples-dir}/com/example/restassured/CustomFormat.java[tags=custom-format]
 ----
-====
 
 
 
@@ -147,7 +143,6 @@ Six snippets are produced by default:
 You can change the default snippet configuration during setup by using the `RestDocumentationConfigurer` API.
 The following examples produce only the `curl-request` snippet by default:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -165,15 +160,15 @@ include::{examples-dir}/com/example/webtestclient/CustomDefaultSnippets.java[tag
 ----
 include::{examples-dir}/com/example/restassured/CustomDefaultSnippets.java[tags=custom-default-snippets]
 ----
-====
+
+
 
 [[configuration-default-preprocessors]]
 === Default Operation Preprocessors
 
 You can configure default request and response preprocessors during setup by using the `RestDocumentationConfigurer` API.
 The following examples remove the `Foo` headers from all requests and pretty print all responses:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -197,4 +192,5 @@ include::{examples-dir}/com/example/restassured/CustomDefaultOperationPreprocess
 ----
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
-====
+
+

docs/src/docs/asciidoc/contributing.adoc

@@ -29,3 +29,5 @@ If you would like an enhancement to be made to Spring REST Docs, pull requests a
 The source code is on {github}[GitHub].
 You may want to search the {github}/issues?q=is%3Aissue[existing issues] and {github}/pulls?q=is%3Apr[pull requests] to see if the enhancement has already been proposed.
 You may also want to {github}/issues/new[open a new issue] to discuss a possible enhancement before work on it begins.
+
+

docs/src/docs/asciidoc/customizing-requests-and-responses.adoc

@@ -8,7 +8,6 @@ Preprocessing is configured by calling `document` with an `OperationRequestPrepr
 You can obtain instances by using the static `preprocessRequest` and `preprocessResponse` methods on `Preprocessors`.
 The following examples show how to do so:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -32,13 +31,11 @@ include::{examples-dir}/com/example/restassured/PerTestPreprocessing.java[tags=p
 ----
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
-====
 
 Alternatively, you may want to apply the same preprocessors to every test.
 You can do so by using the `RestDocumentationConfigurer` API in your `@Before` method to configure the preprocessors.
 For example, to remove the `Foo` header from all requests and pretty print all responses, you could do one of the following (depending on your testing environment):
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -62,12 +59,10 @@ include::{examples-dir}/com/example/restassured/EveryTestPreprocessing.java[tags
 ----
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
-====
 
 Then, in each test, you can perform any configuration specific to that test.
 The following examples show how to do so:
 
-====
 [source,java,indent=0,role="primary"]
 .MockMvc
 ----
@@ -85,7 +80,6 @@ include::{examples-dir}/com/example/webtestclient/EveryTestPreprocessing.java[ta
 ----
 include::{examples-dir}/com/example/restassured/EveryTestPreprocessing.java[tags=use]
 ----
-====
 
 Various built-in preprocessors, including those illustrated above, are available through the static methods on `Preprocessors`.
 See <<Preprocessors, below>> for further details.
@@ -155,3 +149,5 @@ If one of the built-in preprocessors does not meet your needs, you can write you
 You can then use your custom preprocessor in exactly the same way as any of the built-in preprocessors.
 
 If you want to modify only the content (body) of a request or response, consider implementing the `ContentModifier` interface and using it with the built-in `ContentModifyingOperationPreprocessor`.
+
+