diff --git a/docs/src/content/docs/index.mdx b/docs/src/content/docs/index.mdx
index 4ab91684310..e350c446b73 100644
--- a/docs/src/content/docs/index.mdx
+++ b/docs/src/content/docs/index.mdx
@@ -24,7 +24,7 @@ import WorkflowHero from '../../components/WorkflowHero.astro';
 
 <WorkflowHero />
 
-Wake up to ready-to-review repository improvements-automated triage, CI insights, docs updates, and test enhancements from simple markdown workflows.
+Wake up to ready-to-review repository improvements — automated triage, CI insights, docs updates, and test enhancements from simple markdown workflows.
 
 GitHub Agentic Workflows deliver this: repository automation, running the coding agents you know and love, in GitHub Actions, with strong guardrails and security-first design principles.
 
diff --git a/docs/src/content/docs/setup/quick-start.mdx b/docs/src/content/docs/setup/quick-start.mdx
index 17eed0c2518..aeac2d9863a 100644
--- a/docs/src/content/docs/setup/quick-start.mdx
+++ b/docs/src/content/docs/setup/quick-start.mdx
@@ -76,7 +76,7 @@ The wizard generates a compiled workflow file (`.lock.yml`) automatically — yo
 
 > [!NOTE]
 > **Setting up `COPILOT_GITHUB_TOKEN`?**
-> 1. [Create a fine-grained PAT](https://github.com/settings/personal-access-tokens/new) under your user account.
+> 1. [Create a fine-grained Personal Access Token (PAT)](https://github.com/settings/personal-access-tokens/new) under your user account.
 > 2. Under **Permissions → Account permissions**, set **Copilot Requests** to **Read**, then generate the token.
 > 3. Add it as a repository secret from your repository root with `gh secret set COPILOT_GITHUB_TOKEN < /path/to/token.txt`, or use the GitHub UI. See [Authentication](/gh-aw/reference/auth/#copilot_github_token) for more detail.
 >
@@ -94,6 +94,13 @@ The wizard generates a compiled workflow file (`.lock.yml`) automatically — yo
 
 An automated workflow run can take 2-3 minutes.
 
+To watch the run while it's in flight:
+
+- **From the browser**: open the **Actions** tab of your repository and select the most recent workflow run.
+- **From the CLI**: run `gh aw status` to list workflow state, or `gh run watch` to stream the latest run.
+
+When the run succeeds, a new issue titled with "Daily Repo Report" appears in the **Issues** tab of your repository. If the run fails, open the run from the **Actions** tab to view step logs and error output.
+
 Once your initial run is complete, a new issue will be created in your repository with a "Daily Repo Report". The report will be automatically generated and will analyze:
 
 - Recent repository activity (issues, PRs, discussions, releases, code changes)