Docs linting fixes

Signed-off-by: George Steel <[email protected]>

Author: gsteel

docs/book/intro.md

@@ -28,14 +28,14 @@ APIs. In particular, it specifies the following:
   appending a serialization format of either `json` or `xml`:
   `application/problem+json`, `application/problem+xml`.
 - Error responses will have each of the following keys:
-  - `detail`, a human-readable description of the specific error.
-  - `type`, a unique URI for the general error type, generally pointing to
-    human-readable documentation of that given type.
-  - `title`, a short, human-readable title for the general error type; the title
-    should not change for given `type`s.
-  - `status`, conveying the HTTP status code; this is so that all information
-    is in one place, but also to correct for changes in the status code due to
-    usage of proxy servers.
+    - `detail`, a human-readable description of the specific error.
+    - `type`, a unique URI for the general error type, generally pointing to
+      human-readable documentation of that given type.
+    - `title`, a short, human-readable title for the general error type; the title
+      should not change for given `type`s.
+    - `status`, conveying the HTTP status code; this is so that all information
+      is in one place, but also to correct for changes in the status code due to
+      usage of proxy servers.
 
 Optionally, an `instance` key may be present, with a unique URI for the specific
 error; this will often point to an error log for that specific response.

docs/book/response.md

@@ -141,21 +141,21 @@ This package also provides a factory for generating the
 - Pulls the `Psr\Http\Message\ResponseInterface` service to provide as the
   `$responseFactory` parameter.
 - If a `config` service is present:
-  - If the service contains a `debug` key with a boolean value, that value is
-    provided as the `$isDebug` parameter.
-  - If the service contains a `problem-details` key with an array value
-    containing a `json_flags` key, and that value is an integer, that value is
-    provided as the `$jsonFlags` parameter.
-  - If the service contains a `problem-details` key with an array value
-    containing a `default_types_map` key, and that value is an array, that
-    value is provided as the `$defaultTypesMap` parameter; see the
-    [default types documentation](default-types.md) for details on defining
-    this map. (Since 1.1.0.)
-  - If the service contains a `problem-details` key with an array value
-    containing a `include-throwable-details` key,
-    and that value is a boolean,
-    that value is used instead of global `debug` value for the `$includeThrowableDetail` parameter.
-    (Since 1.14.0.)
+    - If the service contains a `debug` key with a boolean value, that value is
+      provided as the `$isDebug` parameter.
+    - If the service contains a `problem-details` key with an array value
+      containing a `json_flags` key, and that value is an integer, that value is
+      provided as the `$jsonFlags` parameter.
+    - If the service contains a `problem-details` key with an array value
+      containing a `default_types_map` key, and that value is an array, that
+      value is provided as the `$defaultTypesMap` parameter; see the
+      [default types documentation](default-types.md) for details on defining
+      this map. (Since 1.1.0.)
+    - If the service contains a `problem-details` key with an array value
+      containing a `include-throwable-details` key,
+      and that value is a boolean,
+      that value is used instead of global `debug` value for the `$includeThrowableDetail` parameter.
+      (Since 1.14.0.)
 
 ### Example configuration