docs(cloud): Final rollout cleanup (paragraph-start inline-code + intro cross-links)

cloud_docs/concepts/database.md

@@ -73,7 +73,7 @@ Any PostgreSQL-compatible client works. A few popular options:
 
 ## Reset the database
 
-`scloud db wipe` deletes all tables, all data, and all applied migrations from the managed database. It asks for confirmation by default.
+The `scloud db wipe` command deletes all tables, all data, and all applied migrations from the managed database. It asks for confirmation by default.
 
 ```bash
 scloud db wipe

cloud_docs/concepts/deployments.md

@@ -131,7 +131,7 @@ By default, every file ignored by `.gitignore` is also excluded from the deploym
 !lib/src/generated/
 ```
 
-`scloud` may generate intermediate files under `.scloud/` directories. Add the pattern to your project's `.gitignore` so they don't end up in version control:
+The `scloud` CLI may generate intermediate files under `.scloud/` directories. Add the pattern to your project's `.gitignore` so they don't end up in version control:
 
 ```text title=".gitignore"
 # scloud deployment generated files

cloud_docs/concepts/passwords-secrets-env-vars.md

@@ -27,7 +27,7 @@ All three commands follow the same shape:
 
 Passwords are the default tier for sensitive values the server reads through the Serverpod API. They are encrypted at rest, never shown after they're set, and accessed in code by the name you gave them. Each password is stored under a `SERVERPOD_PASSWORD_` prefix that the CLI adds on `set` and that `getPassword()` strips on read, so the name in your code stays clean. Common cases include database passwords, JWT signing secrets, third-party API keys, and email service credentials.
 
-Serverpod Cloud also provisions a set of platform-managed passwords automatically: database credentials, Insights tokens, `serverpod_auth_idp_server` keys, and keys for the legacy auth module. `scloud password list` groups them into four categories: **Custom** (passwords you add), **Services** (database, Insights, and related platform passwords), **Auth** (passwords for `serverpod_auth_idp_server`), and **Legacy Auth** (passwords for the legacy authentication module). The Status column marks platform-managed passwords `AUTO (Platform)` and user-set ones `SET (User)`.
+Serverpod Cloud also provisions a set of platform-managed passwords automatically: database credentials, Insights tokens, `serverpod_auth_idp_server` keys, and keys for the legacy auth module. Run `scloud password list` to see them grouped into four categories: **Custom** (passwords you add), **Services** (database, Insights, and related platform passwords), **Auth** (passwords for `serverpod_auth_idp_server`), and **Legacy Auth** (passwords for the legacy authentication module). The Status column marks platform-managed passwords `AUTO (Platform)` and user-set ones `SET (User)`.
 
 Override a platform-managed password by setting a custom value with the same name. Unset it to restore the platform default.
 

cloud_docs/guides/ship-non-dart-files.md

@@ -37,7 +37,7 @@ Then deploy:
 scloud deploy
 ```
 
-Cloud zips your project directory and includes every file that isn't excluded from the deploy package (see [Control what gets uploaded](#control-what-gets-uploaded) below). `assets/` is the Serverpod naming convention for this folder. You can call it anything, but the rest of this guide assumes `assets/`.
+Cloud zips your project directory and includes every file that isn't excluded from the deploy package (see [Control what gets uploaded](#control-what-gets-uploaded) below). The `assets/` name is the Serverpod naming convention for this folder. You can call it anything, but the rest of this guide assumes `assets/`.
 
 To preview which files Cloud will upload before deploying:
 

cloud_docs/index.md

@@ -20,11 +20,11 @@ scloud launch
 
 - **Runtime and scaling.** Your app runs on a production runtime that scales as traffic grows.
 - **Networking and TLS.** Encrypted endpoints, certificates, and load balancing work without configuration.
-- **Managed Postgres** (optional). Cloud can provision a production-grade Postgres database with automatic migrations and backups.
-- **Secrets and environment variables.** Manage sensitive values through `scloud`; values are encrypted where applicable.
-- **Custom domains.** Attach your own domain; TLS certificates are provisioned and renewed. Cloud hosts both your backend and a preconfigured website for your Flutter web app.
-- **Logs and inspection.** View logs in the CLI or in Serverpod Insights, the desktop log viewer (requires a database).
-- **PubSub, caching, and file storage.** Supported through the Serverpod framework using third-party services today; managed services are on the roadmap.
+- **[Managed Postgres](/cloud/concepts/database)** (optional). Cloud can provision a production-grade Postgres database with automatic migrations and backups.
+- **[Secrets and environment variables](/cloud/concepts/passwords-secrets-env-vars).** Manage sensitive values through `scloud`; values are encrypted where applicable.
+- **[Custom domains](/cloud/concepts/custom-domains).** Attach your own domain; TLS certificates are provisioned and renewed. Cloud hosts both your backend and a preconfigured website for your Flutter web app.
+- **[Logs and inspection](/cloud/concepts/logs).** View logs in the CLI or in Serverpod Insights, the desktop log viewer (requires a database).
+- **PubSub, caching, and file storage.** Supported through the Serverpod framework using third-party services today; managed services are on the roadmap. See [Use Redis for PubSub and caching](/cloud/guides/redis) for the typical setup.
 
 ## Where to go next