fix(docs): fix docs linting issue

Signed-off-by: dhmlau <dhmlau@ca.ibm.com>

Author: dhmlau

docs/site/Parsing-requests.md

@@ -96,8 +96,8 @@ query parameters. Please note that this style does not preserve the encoding of
 primitive types like numbers and booleans. They are always parsed as strings.
 
 To filter results from the GET `/todo-list` endpoint in the todo-list example
-with a relation, { "include": [ { "relation": "todo" } ] }, the following
-url-encoded query parameter can be used,
+with a relation, { "include": [ { "relation": "todo" } ] }, the following url-encoded
+query parameter can be used,
 
 ```
    http://localhost:3000/todos?filter=%7B%22include%22%3A%5B%7B%22relation%22%3A%22todoList%22%7D%5D%7D

docs/site/decorators/Decorators_openapi.md

@@ -224,8 +224,8 @@ supports receiving `url-encoded` payload for a json query parameter as per Open
 API specification.
 
 To filter results from the GET '/todo-list' endpoint in the todo-list example
-with a specific relation, { "include": [ { "relation": "todo" } ] }, the
-following `url-encoded` query parameter can be used,
+with a specific relation, { "include": [ { "relation": "todo" } ] }, the following
+`url-encoded` query parameter can be used,
 
 ```
    http://localhost:3000/todos?filter=%7B%22include%22%3A%5B%7B%22relation%22%3A%22todoList%22%7D%5D%7D

docs/site/migration/auth/authentication.md

@@ -90,8 +90,8 @@ Next let's take a look of the migration steps to get prepared:
 - provides persistency for `User`, see
   [section 2](#user-persistency-and-crud-apis).
 - creates a login controller, see [section 3](#creating-login-function).
-- mounts the JWT authentication component, see [section 4](#mounting-
-  authentication-component). It mainly includes:
+- mounts the JWT authentication component, see [section 4](#mounting- authentication-component).
+  It mainly includes:
   - a token service to generate and validate access tokens
   - an authentication strategy to validate the user identity