clean up docs

Author: hauner

docs/modules/ROOT/pages/gradle.adoc

@@ -1,14 +1,15 @@
-= Gradle Plugin
 include::partial$links.adoc[]
 
-The xref:gradle::index.adoc[openapi-processor-gradle] gradle plugin can run any of the **openapi-processor**'s.
+= Gradle Plugin
+
+The xref:gradle::index.adoc[openapi-processor-gradle] Gradle plugin can run any of the **openapi-processor**'s.
 
-To use it in a Gradle project, the Gradle file of the project requires a few additional instructions. The following sections describe how to activate & configure **openapi-processor-spring** in a `build.gradle` file.
+To use it in a Gradle project, the Gradle file of the project requires a few additional instructions. The following sections describe how to activate and configure **openapi-processor-spring** in a `build.gradle` file.
 
 
 == adding the plugin
 
-To activate the plugin add it to (like any other gradle plugin) the `plugins` configuration:
+To activate the plugin, add it to (like any other Gradle plugin) the `plugins` configuration:
 
 [source,groovy]
 ----
@@ -21,7 +22,7 @@ plugins {
 
 == configuring processor-spring
 
-The plugin will add an `openapiProcessor` configuration block that is used to configure the processors. Configuration for a specific processor belongs inside it with the processor name as configuration block name.
+The plugin will add an `openapiProcessor` configuration block used to configure the processors. Configuration for a specific processor belongs inside it with the processor name as configuration block name.
 
 [source,groovy]
 ----

docs/modules/ROOT/pages/links.adoc

@@ -1,6 +1,7 @@
-= Links
 include::partial$links.adoc[]
 
+= Links
+
 == OpenAPI
 
 * link:{openapi}[OpenAPI, window="_blank"] Homepage of the OpenAPI Initiative.

docs/modules/ROOT/pages/mapping/annotation.adoc

@@ -101,7 +101,7 @@ Previously an annotation mapping was lost if the type was mapped at the same tim
 
 Assume the following mapping:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs="attributes+"]
 ----
 openapi-processor-mapping: {var-mapping-version}
 
@@ -147,7 +147,7 @@ public class FooBar {
 
 Given the following OpenAPI description, that describe two (echo like) endpoints that receive an object via post and return the same object. In the mapping file we add a custom bean validation annotation. It checks the sum of both properties in `Foo` and `Bar`.
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi: {var-openapi-version}
 info:
@@ -218,7 +218,7 @@ components:
 
 and a `mapping.yaml` with annotation type mappings:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version} # <1>
 

docs/modules/ROOT/pages/mapping/endpoint.adoc

@@ -83,7 +83,7 @@ It is possible to add mappings that apply only to a specific http method. The mo
 
 Here are a few examples of possible http endpoint mappings:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 

docs/modules/ROOT/pages/mapping/extension.adoc

@@ -10,7 +10,7 @@ Apart from the annotation mapping by an OpenAPI type, openapi-processor can use
 
 Here is a simple schema that has `x-` tensions on the `bar` property.
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi: {var-openapi-version}
 # ...
@@ -29,7 +29,7 @@ components:
 
 In general openapi-processor will ignore the `x-` tension properties unless we map the `x-` tensions/values to annotations like this:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:

docs/modules/ROOT/pages/mapping/global.adoc

@@ -5,7 +5,7 @@ Global type mapping will replace **any** usage of an OpenAPI type in the api des
 
 It is defined like below, and it should be added to the `map/types` section in the `mapping.yaml` which is a list of global type mappings:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 
@@ -134,7 +134,7 @@ This will generate the same code as the longer mapping version above.
 
 It is possible to create type mappings with nested generics types. Here are a few examples:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 

docs/modules/ROOT/pages/mapping/logging.adoc

@@ -11,7 +11,7 @@ In case the processor uses the mapping, but it still doesn't behave as expected,
 
 To control the logging, there are two new xref:processor/configuration.adoc#_logging[logging options].
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:
@@ -100,7 +100,7 @@ If the `mapping-target` is `stdout` the processor output will be written without
 
 to enable logging with maven use:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:
@@ -116,7 +116,7 @@ logging:
 
 to get the simple output, or
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:
@@ -139,7 +139,7 @@ Gradle requires the `mapping-target` to be `stdout`. Gradle can only globally en
 
 to enable logging with gradle use:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:

docs/modules/ROOT/pages/mapping/null.adoc

@@ -31,7 +31,7 @@ Normally the processor would generate a simple pojo with a `String` property.
 
 By adding a `null` mapping for the `/foo` endpoint (this does work only on the endpoint level. A global null mapping gets ignored):
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 

docs/modules/ROOT/pages/mapping/package-name.adoc

@@ -1,14 +1,16 @@
+include::partial$vars.adoc[]
+
 = package-name mapping
 
 The type mapping (v2 and up) configuration allows to reference the target `package-name` in generic parameters using the `+{package-name}+` expression. This makes it possible to adjust the `package-name` without touching the mapping, and it does reduce duplication.
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 options:
   package-name: io.openapiprocessor.generated
 
 map:
   types:
-    - type: FooPage => org.springframework.data.domain.Page<{package-name}.model.Foo>
+    - type: FooPage => org.springframework.data.domain.Page<\{package-name}.model.Foo>
 ----

docs/modules/ROOT/pages/mapping/parameter.adoc

@@ -48,7 +48,7 @@ map:
 
 and an openapi.yaml with multiple endpoints having a parameter named "date"
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi: {var-openapi-version}
 info:
@@ -103,7 +103,7 @@ It is possible to add additional parameters that are not described in the OpenAP
 
 While it is possible to add it at the global level, it is best used at the endpoint level.
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 
@@ -119,7 +119,7 @@ map:
 
 Given the mapping configuration above and the following endpoint description:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi: {var-openapi-version}
 info:
@@ -170,7 +170,7 @@ It may also be useful to remove a parameter, maybe it is handled by a request fi
 
 Again, even if it is possible to add it at the global level, it is best used at the endpoint level.
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi-processor-mapping: {var-mapping-version}
 
@@ -186,7 +186,7 @@ map:
 
 Given the configuration above and the following endpoint description:
 
-[source,yaml,subs="attributes"]
+[source,yaml,subs=attributes+]
 ----
 openapi: {var-openapi-version}
 info: