docs cleanup suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: skarim

SUPPORT.md

@@ -4,7 +4,7 @@
 
 This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
 
-For help or questions about using this project, please use GitHib discussions. Add a comment to an existing post or create a new discussion post.
+For help or questions about using this project, please use GitHub Discussions. Add a comment to an existing post or create a new discussion post.
 
 **gh-stack** is under active development and maintained by GitHub staff. We will do our best to respond to support, feature requests, and community questions in a timely manner.
 

docs/src/content/docs/faq.md

@@ -14,12 +14,12 @@ A stacked PR is a pull request that is part of an ordered chain of PRs, where ea
 You can create a stack using the `gh stack` CLI:
 
 ```sh
-gh stack init
+gh stack init auth-layer
 # ... make commits on the first branch ...
-gh stack add auth-layer
-# ... make commits ...
 gh stack add api-routes
 # ... make commits ...
+gh stack add request-validation
+# ... make commits ...
 gh stack submit
 ```
 

docs/src/content/docs/getting-started/quick-start.md

@@ -89,6 +89,6 @@ This shows all branches, their PR links, statuses, and the most recent commit on
 
 ## What's Next?
 
-- [Working with Stacked PRs](/gh-stack/guides/using-prs/) — Learn about the PR review and merge experience
+- [Working with Stacked PRs](/gh-stack/guides/stacked-prs/) — Learn about the PR review and merge experience
 - [Typical Workflows](/gh-stack/guides/workflows/) — Common patterns for day-to-day use
 - [CLI Reference](/gh-stack/reference/cli/) — Full command documentation

docs/src/content/docs/guides/stacked-prs.md

@@ -5,7 +5,7 @@ description: Practical guide for reviewing, merging, and managing stacked pull r
 
 This guide covers the practical day-to-day experience of working with Stacked PRs — how to review them, how merging works step by step, and how to keep things in sync from the CLI.
 
-For an introduction to what stacks are and how GitHub supports them natively, see the [Overview](/gh-stack/introduction/overview/). For a visual walkthrough of the UI, see [Using Stacks in the GitHub UI](/gh-stack/guides/ui-walkthrough/).
+For an introduction to what stacks are and how GitHub supports them natively, see the [Overview](/gh-stack/introduction/overview/). For a visual walkthrough of the UI, see [Using Stacks in the GitHub UI](/gh-stack/guides/ui/).
 
 ## Reviewing Stacked PRs
 

docs/src/content/docs/index.mdx

@@ -66,12 +66,12 @@ When you're ready to merge, you merge from the bottom up. Each PR can be merged
 gh extension install github/gh-stack
 
 # Create a stack (creates and checks out the first branch)
-gh stack init
-# ... make commits ...
-gh stack add auth-layer
+gh stack init auth-layer
 # ... make commits ...
 gh stack add api-routes
 # ... make commits ...
+gh stack add frontend
+# ... make commits ...
 
 # Push all branches
 gh stack push

docs/src/content/docs/introduction/overview.md

@@ -120,6 +120,6 @@ Create a new branch when you're starting a different concern that depends on wha
 ## Next Steps
 
 - [Quick Start](/gh-stack/getting-started/quick-start/) — Install the CLI and create your first stack
-- [Working with Stacked PRs](/gh-stack/guides/using-prs/) — Learn about the PR review and merge experience
+- [Working with Stacked PRs](/gh-stack/guides/stacked-prs/) — Learn about the PR review and merge experience
 - [Typical Workflows](/gh-stack/guides/workflows/) — Common patterns for day-to-day use
 - [CLI Reference](/gh-stack/reference/cli/) — Complete command documentation