Apply Ben's suggestions: shorten SQL description, simplify setup intro

- Overview: SQL database bullet shortened to match actual storage scope
- Database: simplify setup path intro sentence per Ben's suggestion

Author: kemister85

modules/ROOT/pages/tinymceai-on-premises-database.adoc

@@ -37,7 +37,7 @@ The AI service supports both MySQL and PostgreSQL equally. Pick whichever the op
 
 == Choosing a setup path
 
-Use Docker Compose for evaluation, managed cloud services (Amazon RDS, Cloud SQL, Azure Database) for production. All paths produce the same end state: a running database the AI service can connect to. Both MySQL and PostgreSQL are supported in every configuration.
+Use Docker Compose for evaluation or managed cloud services (Amazon RDS, Cloud SQL, Azure Database) for production.
 
 [.text-center]
 image::tinymceai-on-premises/database-setup-fig-1.svg[Database setup decision tree: local Docker Compose vs managed cloud database for evaluation and production,width=100%]

modules/ROOT/pages/tinymceai-on-premises.adoc

@@ -14,7 +14,7 @@ The infrastructure consists of three layers:
 * The *browser* runs the TinyMCE editor with the `tinymceai` plugin.
 * The *application layer* runs the token endpoint (which signs JWTs), the AI service container, and a load balancer or reverse proxy. It may consist of one or more AI service instances behind the load balancer (round-robin recommended). Each instance runs the same stateless container image.
 * The *data layer* consists of a SQL database, a Redis instance, and file storage:
-** *SQL database*: stores persistent data: configurations, conversations, files, and documents.
+** *SQL database*: stores persistent data such as configurations and conversations.
 ** *Redis*: caching and coordination (SSE delivery, rate limits, pub/sub). Enables the AI service to remain stateless.
 ** *File storage*: stores uploaded files and documents (S3, Azure Blob, filesystem, or the database itself).