docs(cloud): Final rollout cleanup (paragraph-start inline-code + intro cross-links)#632
Open
developerjamiu wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final cleanup PR for the Cloud IA rollout (issue #568), stacked on #627 (PR 14). Two commits.
Commit 1: paragraph-start inline-code fixes
The recurring house-style §6 violation (inline code at the start of a sentence or paragraph). Caught via sweep, fixed across four pages:
concepts/database.md: "Thescloud db wipecommand deletes..."concepts/deployments.md: "ThescloudCLI may generate..."concepts/passwords-secrets-env-vars.md: "Runscloud password listto see them grouped..."guides/ship-non-dart-files.md: "Theassets/name is the Serverpod naming convention..."Commit 2: intro cross-links (per Alex's note)
The capability bullets in the introduction's "What Serverpod Cloud manages" section now link to their corresponding concept or guide pages, so a reader who hits Managed Postgres / Secrets / Custom domains / Logs / PubSub can jump straight to the relevant page. Two bullets (Runtime and scaling, Networking and TLS) don't have a clean 1:1 destination and stay unlinked.
Out of scope
cloud_docs/getting-started/launch.md:30(link toserverpod.dev/cloudexists). Marked resolved on the issue comment.Test plan
npm run buildpasses