Use one sentence per line in v7 docs

Reflows hard-wrapped prose so each sentence occupies its own line.
Line breaks only, no wording changes.

Signed-off-by: arhimede <julian@dotkernel.com>

Author: arhimede

docs/book/v7/commands/create-admin-account.md

@@ -56,7 +56,8 @@ php ./bin/cli.php help admin:create
 
 **Q: Can I choose the role of the created account?**
 
-A: No. The command always assigns the `admin` role; other roles must be set afterwards.
+A: No.
+The command always assigns the `admin` role; other roles must be set afterwards.
 See [Authorization](../core-features/authorization.md).
 
 **Q: What can I use as the identity?**

docs/book/v7/commands/display-available-endpoints.md

@@ -88,7 +88,8 @@ php ./bin/cli.php route:list --help
 
 **Q: Is the output generated from a static file?**
 
-A: No. The command walks the application's registered routes in realtime, so it always reflects the current configuration.
+A: No.
+The command walks the application's registered routes in realtime, so it always reflects the current configuration.
 
 **Q: Which filters are available?**
 

docs/book/v7/commands/generate-database-migrations.md

@@ -13,8 +13,7 @@ Run the following command in your application’s root directory:
 vendor/bin/doctrine-migrations diff
 ```
 
-If you have mapping modifications, this will create a new migration file under
-`src/Core/src/App/src/Migration/`, in the `Core\App\Migration` namespace.
+If you have mapping modifications, this will create a new migration file under `src/Core/src/App/src/Migration/`, in the `Core\App\Migration` namespace.
 The location comes from the `doctrine.migrations.migrations_paths` key in `Core\App\ConfigProvider`.
 Opening the migration file, you will notice that it contains some queries that will drop your `oauth_*` tables because they are unmapped (there is no doctrine entity describing them).
 You should delete your latest migration with the DROP queries in it as we will create another one, without the DROP queries in it.

docs/book/v7/commands/generate-tokens.md

@@ -98,4 +98,5 @@ Clear it with `php ./bin/clear-config-cache.php`.
 
 **Q: Does the command store the token for me?**
 
-A: No. It only prints the value; copying it into the configuration file is a manual step.
+A: No.
+It only prints the value; copying it into the configuration file is a manual step.

docs/book/v7/core-features/authentication.md

@@ -27,9 +27,7 @@ Authentication in Dotkernel API is built around the `mezzio/mezzio-authenticatio
 To customize authentication behavior (token lifetimes, algorithms, etc.), edit `config/autoload/local.php` under the `authentication` key.
 See the [Mezzio OAuth2 documentation](https://docs.mezzio.dev/mezzio-authentication-oauth2/v1/intro/#configuration) for all available options.
 
-> You can check the
-> [mezzio/mezzio-authentication-oauth2](https://docs.mezzio.dev/mezzio-authentication-oauth2/v1/intro/#configuration)
-> configuration part for more info.
+> You can check the [mezzio/mezzio-authentication-oauth2](https://docs.mezzio.dev/mezzio-authentication-oauth2/v1/intro/#configuration) configuration part for more info.
 
 ## How it works
 
@@ -250,5 +248,6 @@ See [Middleware flow](../flow/middleware-flow.md).
 
 **Q: Is authenticating enough to access an endpoint?**
 
-A: No. Authentication establishes the identity; the role still needs permission for the route.
+A: No.
+Authentication establishes the identity; the role still needs permission for the route.
 See [Authorization](authorization.md).

docs/book/v7/core-features/authorization.md

@@ -194,7 +194,8 @@ Because the middleware only knows `AuthorizationInterface`, no application code
 
 **Q: Do the permissions cover every route?**
 
-A: Yes, exactly. The three populated roles grant 38 permissions across the 38 declared routes, with no route ungranted and no permission naming a route that does not exist.
+A: Yes, exactly.
+The three populated roles grant 38 permissions across the 38 declared routes, with no route ungranted and no permission naming a route that does not exist.
 `app::view-index` and `app::create-error-report` are the only two granted to two roles.
 
 **Q: What does a rejected request look like?**

docs/book/v7/core-features/content-validation.md

@@ -129,7 +129,8 @@ A: The server attempts to deserialize the body as best it can, rather than rejec
 
 **Q: Will `application/vnd.api+json` be rejected if I only configured `application/json`?**
 
-A: No. Validation resolves to the more generic media type, so the request is served as JSON.
+A: No.
+Validation resolves to the more generic media type, so the request is served as JSON.
 
 **Q: How do I configure a file upload endpoint?**
 

docs/book/v7/core-features/error-reporting.md

@@ -166,7 +166,8 @@ A: The log entry includes the token used, and tokens can be defined as key-value
 
 **Q: Do these tokens expire?**
 
-A: No. Because they are indefinite, rotate them manually from time to time.
+A: No.
+Because they are indefinite, rotate them manually from time to time.
 See [Basic security](../security/basic-security.md).
 
 **Q: Where do the reports end up?**
@@ -176,5 +177,6 @@ If it does not exist, it is created automatically.
 
 **Q: Does this endpoint need an auth token as well?**
 
-A: No. It is authorized solely by the error reporting token.
+A: No.
+It is authorized solely by the error reporting token.
 See [Using the documentation](../openapi/use-documentation.md).

docs/book/v7/core-features/rendering-and-sending-emails.md

@@ -63,7 +63,8 @@ A: Files combining PHP and HTML with the `.phtml` extension.
 
 **Q: Does `MailService` still need a renderer injected?**
 
-A: No. Rendering happens in the handler, and the finished body is passed to the mail service as a parameter.
+A: No.
+Rendering happens in the handler, and the finished body is passed to the mail service as a parameter.
 
 **Q: How do I render a template and send it?**
 

docs/book/v7/extended-features/core-and-app.md

@@ -73,5 +73,6 @@ See [File structure](../introduction/file-structure.md).
 
 **Q: Was this split present before version 6.0?**
 
-A: No. It was introduced in 6.0 when common logic was moved into the Core module.
+A: No.
+It was introduced in 6.0 when common logic was moved into the Core module.
 See [Upgrading from 5.x to 6.0](../upgrading/UPGRADE-6.0.md).