diff --git a/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml b/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
index 4bacdbfe..431817ac 100644
--- a/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
+++ b/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
@@ -10,7 +10,9 @@ body:
 
         **Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
 
-        **What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+        **What you will do:** Clone your own Learning Room repository (this repo) to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+
+        **Your repository URL:** On this repository's main page, select the green **Code** button and copy the HTTPS URL. It looks like `https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git`. You already have write access to this repo, so your push will work without any extra setup.
 
         ### The local workflow
 
@@ -30,7 +32,7 @@ body:
         1. Open VS Code
         2. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette
         3. Type `Git: Clone`
-        4. Paste this repository URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        4. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         5. Choose a folder on your computer where you want to save it
         6. Wait for it to clone (you should see it in the file explorer)
 
@@ -67,7 +69,7 @@ body:
         **Step 1: Clone the repository**
         1. Open GitHub Desktop
         2. Choose File > Clone Repository
-        3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        3. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         4. Choose a folder location
         5. Select Clone
 
@@ -98,19 +100,19 @@ body:
         **Option C: Command Line (CLI)**
 
         ```bash
-        # Step 1: Clone
-        git clone https://github.com/Community-Access/learning-room.git
-        cd learning-room
+        # Step 1: Clone (paste your Learning Room URL from the green Code button)
+        git clone https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git
+        cd learning-room-...-YOUR-USERNAME
 
         # Step 2: Create your branch
         git checkout -b fix/YOUR-USERNAME
 
         # Step 3: Edit a file (use your preferred editor)
-        # Open docs/chapter-XX.md and make a change
+        # Open README.md and improve a sentence or fix a typo
 
         # Step 4: Stage and commit
         git add .
-        git commit -m "fix: correct typo in chapter 5"
+        git commit -m "docs: improve README wording"
 
         # Step 5: Push
         git push -u origin fix/YOUR-USERNAME
@@ -143,7 +145,7 @@ body:
         | Symptom | Try this |
         |---|---|
         | Clone fails with authentication error | See [Appendix D: Git Authentication](https://github.com/Community-Access/git-going-with-github/blob/main/docs/appendix-d-git-authentication.md) for setup help. |
-        | Push fails with permission denied | Make sure you have write access to the repository. Ask your facilitator. |
+        | Push fails with permission denied | Make sure you cloned your own Learning Room repository (this repo), not another repository. If it still fails, ask your facilitator. |
         | I am not sure what to edit | Fix any typo, improve any sentence, or add a helpful comment. The content of the change matters less than the workflow. |
         | VS Code does not show the Source Control panel | Press Ctrl+Shift+G (Cmd+Shift+G on Mac). Make sure you opened the cloned folder as a workspace. |
         | I finished but want to check my work | [View the reference solution](https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-10-go-local.md) |
diff --git a/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml b/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
index 43b7e9e0..6a6b08dd 100644
--- a/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
+++ b/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
@@ -23,7 +23,7 @@ body:
         ### Step-by-step instructions
 
         **Step 1: Check for a notification banner**
-        1. Go to the sci-fi themes repository on GitHub.com
+        1. Go to your Learning Room repository (this repo) on GitHub.com
         2. You may see a notification banner at the top saying "Your branch had recent pushes"
         3. If so, select **Compare & pull request** - this is a shortcut
         4. Skip to Step 3
diff --git a/docs/CHALLENGES.md b/docs/CHALLENGES.md
index de2c3031..7bd2126d 100644
--- a/docs/CHALLENGES.md
+++ b/docs/CHALLENGES.md
@@ -188,7 +188,7 @@ Before moving on, scan the [Challenge 9 solution reference](https://github.com/C
 
 **Chapters:** Ch11-14 | **Evidence:** Comment | **Autograded**
 
-Day 2 moves the same contribution workflow onto your computer. You clone the sci-fi themes repository, create a branch locally, edit `README.md`, commit, and push the branch back to GitHub.
+Day 2 moves the same contribution workflow onto your computer. You clone your own Learning Room repository, create a branch locally, edit `README.md`, commit, and push the branch back to GitHub.
 
 **CLI best practices for this challenge:**
 
@@ -199,7 +199,7 @@ Day 2 moves the same contribution workflow onto your computer. You clone the sci
 
 **What to do:**
 
-- Clone `https://github.com/Community-Access/vscode-sci-fi-themes.git` to your computer with VS Code, GitHub Desktop, or the command line
+- Clone your own Learning Room repository (copy the HTTPS URL from the green **Code** button on its main page) with VS Code, GitHub Desktop, or the command line
 - Create a branch named `fix/YOUR-USERNAME`
 - Edit `README.md`
 - Commit and push the branch to GitHub
@@ -214,7 +214,7 @@ The [Challenge 10 solution reference](https://github.com/Community-Access/git-go
 
 **Chapters:** Ch14-15 | **Evidence:** Comment
 
-This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to the sci-fi themes repository, open a PR, and explain the change for reviewers.
+This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to your Learning Room repository, open a PR, and explain the change for reviewers.
 
 **CLI best practices for this challenge:**
 
diff --git a/html/docs/CHALLENGES.html b/html/docs/CHALLENGES.html
index bb25c84f..7a55ce61 100644
--- a/html/docs/CHALLENGES.html
+++ b/html/docs/CHALLENGES.html
@@ -374,7 +374,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 <summary>Challenge 10: Go Local</summary>
 
 <p><strong>Chapters:</strong> Ch11-14 | <strong>Evidence:</strong> Comment | <strong>Autograded</strong></p>
-<p>Day 2 moves the same contribution workflow onto your computer. You clone the sci-fi themes repository, create a branch locally, edit <code>README.md</code>, commit, and push the branch back to GitHub.</p>
+<p>Day 2 moves the same contribution workflow onto your computer. You clone your own Learning Room repository, create a branch locally, edit <code>README.md</code>, commit, and push the branch back to GitHub.</p>
 <p><strong>CLI best practices for this challenge:</strong></p>
 <ul>
 <li>Run <code>git status</code> before and after each step.</li>
@@ -384,7 +384,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 </ul>
 <p><strong>What to do:</strong></p>
 <ul>
-<li>Clone <code>https://github.com/Community-Access/vscode-sci-fi-themes.git</code> to your computer with VS Code, GitHub Desktop, or the command line</li>
+<li>Clone your own Learning Room repository (copy the HTTPS URL from the green <strong>Code</strong> button on its main page) with VS Code, GitHub Desktop, or the command line</li>
 <li>Create a branch named <code>fix/YOUR-USERNAME</code></li>
 <li>Edit <code>README.md</code></li>
 <li>Commit and push the branch to GitHub</li>
@@ -397,7 +397,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 <summary>Challenge 11: Open a Day 2 PR</summary>
 
 <p><strong>Chapters:</strong> Ch14-15 | <strong>Evidence:</strong> Comment</p>
-<p>This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to the sci-fi themes repository, open a PR, and explain the change for reviewers.</p>
+<p>This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to your Learning Room repository, open a PR, and explain the change for reviewers.</p>
 <p><strong>CLI best practices for this challenge:</strong></p>
 <ul>
 <li>Build the PR body in clear plain text first, including <code>Closes #XX</code>.</li>
diff --git a/html/search-index.json b/html/search-index.json
index 5e6ef669..9970be8e 100644
--- a/html/search-index.json
+++ b/html/search-index.json
@@ -275,12 +275,6 @@
     "url": "docs/22-what-comes-next.html",
     "body": "What Comes Next: Your Developer Journey Related appendices: Appendix X: Resources | Appendix Z: GitHub Skills | Appendix Y: Workshop Materials Authoritative sources: GitHub Skills | GitHub Docs: Getting started Day 2, Closing Material Congratulations -- you have completed the Git Going with GitHub workshop. This chapter is your graduation guide: what you accomplished, where to go next, how to build your portfolio, and how to stay connected with the community. If you are following the companion audio path, this lesson is intentionally the final stop. Reference episodes may help you look up details, but this chapter brings you back to the bigger question: what will you do next with the skills you now have? Table of Contents What You Built in Two Days Your New Skills Inventory Building Your Developer Portfolio Continued Learning Roadmap GitHub Skills Courses to Try Next Staying Connected Contributing Back to This Workshop Final Words 1. What You Built in Two Days Take a moment to appreciate what you accomplished. This is not a list of what you were taught -- it is a list of what you did. Day 1: You Can Navigate This Created and configured a GitHub account with accessibility settings Navigated repositories, files, and folders using your screen reader, keyboard, or preferred tools Filed issues with descriptive titles, labels, and context Created branches, edited files, and opened pull requests Responded to bot feedback and passed automated checks Resolved a merge conflict Reviewed someone else&#39;s code and gave constructive feedback Explored labels, milestones, and project boards Managed notifications Day 2: You Can Build This Installed and configured VS Code with accessibility settings Cloned a repository and worked with Git locally Understood the mental model: working directory, staging area, repository Created branches, staged changes, committed, and pushed from the command line Explored GitHub Copilot: code suggestions, chat, and code review Created an issue template Forked a repository and contributed using the open source workflow Explored the accessibility agents ecosystem Completed a capstone contribution path by designing or improving an agentic asset for Accessibility Agents, GLOW, or another repository The evidence Your GitHub profile now contains real activity: issues filed, pull requests merged, code reviewed, and capstone evidence prepared for a real repository. This is not a certificate. It is a commit history. 2. Your New Skills Inventory The following table maps what you learned to where it applies beyond this workshop. Every skill transfers directly to real-world development. Skill Where you learned it Where it applies Repository navigation Chapters 2-3 Every GitHub project, every job that uses GitHub Issue tracking Chapter 5 Bug reports, feature requests, project management Pull request workflow Chapters 6, 15 Code contribution at any company or open source project Merge conflict resolution Chapter 7 Any team project with multiple contributors Git fundamentals Chapters 13-14 Every software project that uses version control VS Code proficiency Chapters 11-12 Daily development work in any language Code review Chapter 15 Peer review, quality assurance, team collaboration Fork workflow Chapter 18 Open source contribution, cross-team collaboration AI-assisted development Chapters 16, 19-20 GitHub Copilot, AI agents, and future AI tools Accessibility awareness Entire workshop Building inclusive software, WCAG compliance Skills you may not have noticed Reading documentation: You navigated technical guides, followed step-by-step instructions, and troubleshot problems using written references. This is the most important developer skill. Asking for help effectively: You posted on issues with context, error messages, and what you tried. This is how experienced developers communicate. Learning tools by doing: You did not read a manual cover to cover. You tried things, hit problems, and figured them out. This is how real tool learning works. 3. Building Your Developer Portfolio See also: Appendix X: Resources has links to every tool and resource mentioned in this course. Your GitHub profile is your portfolio. Here is how to make what you built visible. Pin your best repositories Go to github.com/settings/profile . Scroll to &quot;Pinned repositories.&quot; Pin the repositories that show your best work. Consider: Your fork of the accessibility-agents repository (shows open source contribution) Any personal projects you create after the workshop Write a profile README Your profile README is the first thing people see when they visit your GitHub profile. Create a repository with the same name as your username (e.g., your-username/your-username ) and add a README.md : # Hi, I am [Your Name] I am a developer focused on [your interests]. ## Recent work - Prepared a capstone contribution for Accessibility Agents, GLOW, or another repository - Completed the Git Going with GitHub workshop ## What I am learning - "
   },
-  {
-    "id": "docs/CHALLENGES.html",
-    "title": "Challenge Hub",
-    "url": "docs/CHALLENGES.html",
-    "body": "Challenge Hub Welcome to the Challenge Hub - your guide to all 16 core challenges and 5 bonus challenges. The challenges are the practice path for the course. Each one asks you to do a small piece of real GitHub work, leave evidence of what you did, and then close the issue so the next challenge can open. The goal is not speed. The goal is to build a contributor rhythm you can trust: orient yourself, make the move, verify the result, and ask for help with clear facts when something feels off. Prefer the exact issue-style flow? Open the consolidated issue walkthrough: Issue-Style Challenge Walkthrough . How Challenges Work Start in your private Learning Room repository, not in the public curriculum repository. Open the Issues tab, find the challenge issue assigned to you, and read the issue body before acting. Each issue explains the task, the evidence prompt, and any buddy check or automated check that applies. When a challenge asks for evidence, post it as a comment on that challenge issue. Evidence can be a link, a short reflection, the name of a branch, a pull request number, or a note about what you tried and what happened. After you post the evidence, close the challenge issue. The Student Progression Bot uses that closed issue as the signal to open the next challenge. Every challenge below includes a reference solution. Treat those files as worked examples, not answer keys. Your exact branch name, issue number, wording, or file count may differ. What matters is whether you practiced the skill and can explain the result. Day 1: You Belong Here (Challenges 1-9) Challenge 1: Find Your Way Around Chapters: Ch02-04 | Evidence: Comment This first challenge is about orientation. Before you edit anything, you learn how a repository is organized: where the Code tab lives, where Issues live, how the file tree behaves, and how the README gives a project its front door. What to do: Find the Code tab and count the files or folders in the repository root Open the Issues tab and identify at least one issue or confirm the tab exists Navigate to docs/welcome.md and read the opening paragraph Find the repository description and the rendered README Evidence to post: Describe what you found and name one navigation shortcut or screen reader technique that helped. Compare your result with the Challenge 1 solution reference when you want a second view of the same exploration path. Challenge 2: File Your First Issue Chapter: Ch05 | Evidence: Comment Issues are how maintainers turn observations into trackable work. In this challenge, you find a small TODO in the Learning Room and write an issue that another person could understand without being in the room with you. What to do: Open docs/welcome.md and search for TODO Create a new issue with a specific title Explain what needs to change, where it is, and why the change would help Evidence to post: Link to the issue you created and include one sentence about why your title is clear. If you want to compare tone and structure, read the Challenge 2 solution reference . Challenge 3: Join the Conversation Chapter: Ch05 | Evidence: Comment Open source is conversation as much as code. This challenge teaches you how to participate in an issue thread with an @mention, a reaction, and a comment that moves the work forward. What to do: Find your buddy&#39;s Challenge 2 issue or a facilitator-provided peer simulation issue Leave a meaningful comment with an @mention Add a reaction to the original issue or a helpful comment Evidence to post: Link to your comment and describe what made it useful, kind, or specific. The Challenge 3 solution reference shows one way to make a short comment feel genuinely collaborative. Challenge 4: Branch Out Chapter: Ch06 | Evidence: Comment A branch is a safe workspace. It lets you try a change without rewriting the main version of the project. In this challenge, you create your own branch and confirm that you know where your work will happen. What to do: Find the branch selector on the Code tab Create a branch named learn/YOUR-USERNAME from main Confirm the branch selector now names your branch Evidence to post: Write the branch name you created and how you confirmed you were on it. Use the Challenge 4 solution reference if you want to check your branch mental model. Challenge 5: Make Your Mark Chapter: Ch06 | Evidence: Comment This is your first small content change. You edit a file, replace a TODO with real text, and commit the change with a message that explains what happened. What to do: Switch to your learn/YOUR-USERNAME branch Edit docs/welcome.md to replace the TODO with useful content Write a commit message that explains the change in plain language Evidence to post: Share your commit message and the file you edited. For a worked example of a focused commit, compare with the Challenge 5 solution reference . Challenge 6: Open Your First Pull Request Chapter: Ch06 | Evidence: Comment A pull request is the conversation around a proposed change. It lets"
-  },
   {
     "id": "docs/Home.html",
     "title": "GIT Going with GitHub Wiki",
@@ -497,6 +491,12 @@
     "url": "docs/get-going.html",
     "body": "Get Going with GitHub Start here if you are new, unsure, or joining from a workshop link. This guide walks you from &quot;I have the link&quot; to &quot;I know where I am, what to do next, and how to ask for help.&quot; You do not need to know Git, GitHub, VS Code, or the command line before you begin. What This Guide Does This workshop is designed so you are never left guessing what comes next. You will have: An enrollment link from the facilitator to create your Learning Room Your own private Learning Room repository Challenge issues that tell you exactly what to do Evidence prompts that tell you what to post when you finish Gandalf bot feedback on pull requests Reference solutions you can compare against after you try Multiple tool paths, so you can work in the browser, VS Code, GitHub Desktop, or the command line when appropriate The goal is not to rush. The goal is to build confidence one checkable step at a time. When Tools or Pages Change GitHub.com, VS Code, GitHub Copilot, github.dev, browser extensions, and agent tools change often. This course is actively maintained, and we use official sources and live checks wherever possible, but your screen may not always match the exact wording in a step. When that happens, do not assume you are failing. Use the same exploration skills the workshop teaches: Check the URL and browser tab title. Move by headings, landmarks, tabs, and button names instead of relying only on visual order. Open keyboard shortcut help ( ? on GitHub) or the VS Code Command Palette when a shortcut or control differs. Read the surrounding labels before activating a control. Ask a facilitator or file a curriculum issue with the page link, the step that differed, and what you heard or observed. The durable skill is not memorizing one layout. The durable skill is learning how to orient, verify, and continue when a tool changes. Step 1 - Know Your Starting Place Before Day 1 starts, complete Chapter 00: Pre-Workshop Setup . That chapter helps you create or verify your GitHub account, configure accessibility settings, choose a browser, install Git and VS Code, and confirm your screen reader setup. If you cannot finish every setup step before the workshop, tell a facilitator early. Setup problems are normal, and the workshop is designed with time and support for recovery. Step 2 - Complete Your Enrollment At the start of the workshop, the facilitator shares an enrollment link. Complete the form to create your private Learning Room repository. Day 2 challenges automatically unlock after you complete Day 1. Open the enrollment link in the browser where you are signed in to GitHub. Complete the enrollment form with your details. An issue will be created in your account. Reply with acknowledgement ( ack ). Automation will provision your private Learning Room repository. Wait for the invitation email from GitHub, then open and bookmark your repository. Your repository name usually looks like learning-room-your-username . This is your personal practice space for the workshop. Step 3 - Understand the Learning Room The Learning Room is a private repository created from a template. Everyone starts from the same materials, but your work belongs to you. You can safely practice there because: You have your own issues, branches, commits, and pull requests Other students do not see your work unless the facilitator intentionally pairs you Mistakes are expected and recoverable Bot feedback is educational, not punitive Challenge issues unlock in sequence so you always know the next step Think of the Learning Room as a guided practice studio. It is real GitHub, but the room is set up so you can learn without fear of damaging a public project. Step 4 - Find Challenge 1 After your Learning Room repository is created, the Student Progression Bot creates your first challenge issue. Open your Learning Room repository. Navigate to the Issues tab. On GitHub, the keyboard shortcut is G then I . Find an issue titled Challenge 1: Find Your Way Around . Open the issue and read the body from top to bottom. Follow the checklist in the issue. Post your evidence in the evidence field or as the requested comment. Close the challenge issue when the instructions tell you to close it. When you close a challenge issue, the next challenge opens. You do not need to hunt through the whole curriculum to know what is next. Step 5 - Choose the Tool That Fits the Moment There is no single correct way to use GitHub. The workshop teaches the workflow first, then offers tool paths. Use this plain-language guide to decide where to start: GitHub.com in the browser: Best for Day 1, issues, pull requests, repository navigation, and reviews. github.dev: Best when you want a VS Code-style editor in the browser without installing anything. Press the period key from many repository pages to open it. VS Code desktop: Best for Day 2, local Git, Copilot, extensions, and deeper editing work. GitHub Desktop: Best if you want a desktop Git workflow w"
   },
+  {
+    "id": "docs/CHALLENGES.html",
+    "title": "Challenge Hub",
+    "url": "docs/CHALLENGES.html",
+    "body": "Challenge Hub Welcome to the Challenge Hub - your guide to all 16 core challenges and 5 bonus challenges. The challenges are the practice path for the course. Each one asks you to do a small piece of real GitHub work, leave evidence of what you did, and then close the issue so the next challenge can open. The goal is not speed. The goal is to build a contributor rhythm you can trust: orient yourself, make the move, verify the result, and ask for help with clear facts when something feels off. Prefer the exact issue-style flow? Open the consolidated issue walkthrough: Issue-Style Challenge Walkthrough . How Challenges Work Start in your private Learning Room repository, not in the public curriculum repository. Open the Issues tab, find the challenge issue assigned to you, and read the issue body before acting. Each issue explains the task, the evidence prompt, and any buddy check or automated check that applies. When a challenge asks for evidence, post it as a comment on that challenge issue. Evidence can be a link, a short reflection, the name of a branch, a pull request number, or a note about what you tried and what happened. After you post the evidence, close the challenge issue. The Student Progression Bot uses that closed issue as the signal to open the next challenge. Every challenge below includes a reference solution. Treat those files as worked examples, not answer keys. Your exact branch name, issue number, wording, or file count may differ. What matters is whether you practiced the skill and can explain the result. Day 1: You Belong Here (Challenges 1-9) Challenge 1: Find Your Way Around Chapters: Ch02-04 | Evidence: Comment This first challenge is about orientation. Before you edit anything, you learn how a repository is organized: where the Code tab lives, where Issues live, how the file tree behaves, and how the README gives a project its front door. What to do: Find the Code tab and count the files or folders in the repository root Open the Issues tab and identify at least one issue or confirm the tab exists Navigate to docs/welcome.md and read the opening paragraph Find the repository description and the rendered README Evidence to post: Describe what you found and name one navigation shortcut or screen reader technique that helped. Compare your result with the Challenge 1 solution reference when you want a second view of the same exploration path. Challenge 2: File Your First Issue Chapter: Ch05 | Evidence: Comment Issues are how maintainers turn observations into trackable work. In this challenge, you find a small TODO in the Learning Room and write an issue that another person could understand without being in the room with you. What to do: Open docs/welcome.md and search for TODO Create a new issue with a specific title Explain what needs to change, where it is, and why the change would help Evidence to post: Link to the issue you created and include one sentence about why your title is clear. If you want to compare tone and structure, read the Challenge 2 solution reference . Challenge 3: Join the Conversation Chapter: Ch05 | Evidence: Comment Open source is conversation as much as code. This challenge teaches you how to participate in an issue thread with an @mention, a reaction, and a comment that moves the work forward. What to do: Find your buddy&#39;s Challenge 2 issue or a facilitator-provided peer simulation issue Leave a meaningful comment with an @mention Add a reaction to the original issue or a helpful comment Evidence to post: Link to your comment and describe what made it useful, kind, or specific. The Challenge 3 solution reference shows one way to make a short comment feel genuinely collaborative. Challenge 4: Branch Out Chapter: Ch06 | Evidence: Comment A branch is a safe workspace. It lets you try a change without rewriting the main version of the project. In this challenge, you create your own branch and confirm that you know where your work will happen. What to do: Find the branch selector on the Code tab Create a branch named learn/YOUR-USERNAME from main Confirm the branch selector now names your branch Evidence to post: Write the branch name you created and how you confirmed you were on it. Use the Challenge 4 solution reference if you want to check your branch mental model. Challenge 5: Make Your Mark Chapter: Ch06 | Evidence: Comment This is your first small content change. You edit a file, replace a TODO with real text, and commit the change with a message that explains what happened. What to do: Switch to your learn/YOUR-USERNAME branch Edit docs/welcome.md to replace the TODO with useful content Write a commit message that explains the change in plain language Evidence to post: Share your commit message and the file you edited. For a worked example of a focused commit, compare with the Challenge 5 solution reference . Challenge 6: Open Your First Pull Request Chapter: Ch06 | Evidence: Comment A pull request is the conversation around a proposed change. It lets"
+  },
   {
     "id": "agents/image alt text agent/agents/image-alt-text.agent.html",
     "title": "image-alt-text.agent",
diff --git a/html/work.html b/html/work.html
index 40506eae..b5940212 100644
--- a/html/work.html
+++ b/html/work.html
@@ -935,7 +935,8 @@ <h4 id="if-you-get-stuck">If you get stuck</h4>
 <h3 id="challenge-10-go-local">Challenge 10: Go Local</h3>
 <p>Source template: <a href="https://github.com/Community-Access/git-going-with-github/blob/main/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml">challenge-10-go-local.yml</a></p>
 <p><strong>Chapters:</strong> <a href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md">Ch11: VS Code Interface</a> | <a href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md">Ch13: How Git Works</a> | <a href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md">Ch14: Git in Practice</a></p>
-<p><strong>What you will do:</strong> Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.</p>
+<p><strong>What you will do:</strong> Clone your own Learning Room repository (this repo) to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.</p>
+<p><strong>Your repository URL:</strong> On this repository&#39;s main page, select the green <strong>Code</strong> button and copy the HTTPS URL. It looks like <code>https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git</code>. You already have write access to this repo, so your push will work without any extra setup.</p>
 <h4 id="the-local-workflow">The local workflow</h4>
 <p>This is the professional Git workflow you will use for the rest of your career:</p>
 <ol>
@@ -952,7 +953,7 @@ <h4 id="step-1-clone-the-repository">Step 1: Clone the repository</h4>
 <li>Open VS Code</li>
 <li>Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette</li>
 <li>Type <code>Git: Clone</code></li>
-<li>Paste this repository URL: <code>https://github.com/Community-Access/vscode-sci-fi-themes.git</code></li>
+<li>Paste your Learning Room repository URL (copied from the green <strong>Code</strong> button on this repo)</li>
 <li>Choose a folder on your computer where you want to save it</li>
 <li>Wait for it to clone (you should see it in the file explorer)</li>
 </ol>
@@ -992,7 +993,7 @@ <h4 id="step-4-commit-your-change">Step 4: Commit your change</h4>
 #### Step 1: Clone the repository
 1. Open GitHub Desktop
 2. Choose File &gt; Clone Repository
-3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+3. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
 4. Choose a folder location
 5. Select Clone
 
@@ -1023,19 +1024,19 @@ <h4 id="step-4-commit-your-change">Step 4: Commit your change</h4>
 #### Option C: Command Line (CLI)
 
 ```bash
-## Step 1: Clone
-git clone https://github.com/Community-Access/learning-room.git
-cd learning-room
+## Step 1: Clone (paste your Learning Room URL from the green Code button)
+git clone https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git
+cd learning-room-...-YOUR-USERNAME
 
 ## Step 2: Create your branch
 git checkout -b fix/YOUR-USERNAME
 
 ## Step 3: Edit a file (use your preferred editor)
-## Open docs/chapter-XX.md and make a change
+## Open README.md and improve a sentence or fix a typo
 
 ## Step 4: Stage and commit
 git add .
-git commit -m &quot;fix: correct typo in chapter 5&quot;
+git commit -m &quot;docs: improve README wording&quot;
 
 ## Step 5: Push
 git push -u origin fix/YOUR-USERNAME
@@ -1069,7 +1070,7 @@ <h4 id="if-you-get-stuck">If you get stuck</h4>
 </tr>
 <tr>
 <td>Push fails with permission denied</td>
-<td>Make sure you have write access to the repository. Ask your facilitator.</td>
+<td>Make sure you cloned your own Learning Room repository (this repo), not another repository. If it still fails, ask your facilitator.</td>
 </tr>
 <tr>
 <td>I am not sure what to edit</td>
@@ -1099,7 +1100,7 @@ <h4 id="the-workflow-pattern">The workflow pattern</h4>
 <h4 id="step-by-step-instructions">Step-by-step instructions</h4>
 <h4 id="step-1-check-for-a-notification-banner">Step 1: Check for a notification banner</h4>
 <ol>
-<li>Go to the sci-fi themes repository on GitHub.com</li>
+<li>Go to your Learning Room repository (this repo) on GitHub.com</li>
 <li>You may see a notification banner at the top saying &quot;Your branch had recent pushes&quot;</li>
 <li>If so, select <strong>Compare &amp; pull request</strong> - this is a shortcut</li>
 <li>Skip to Step 3</li>
diff --git a/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml b/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
index 4bacdbfe..431817ac 100644
--- a/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
+++ b/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
@@ -10,7 +10,9 @@ body:
 
         **Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
 
-        **What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+        **What you will do:** Clone your own Learning Room repository (this repo) to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+
+        **Your repository URL:** On this repository's main page, select the green **Code** button and copy the HTTPS URL. It looks like `https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git`. You already have write access to this repo, so your push will work without any extra setup.
 
         ### The local workflow
 
@@ -30,7 +32,7 @@ body:
         1. Open VS Code
         2. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette
         3. Type `Git: Clone`
-        4. Paste this repository URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        4. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         5. Choose a folder on your computer where you want to save it
         6. Wait for it to clone (you should see it in the file explorer)
 
@@ -67,7 +69,7 @@ body:
         **Step 1: Clone the repository**
         1. Open GitHub Desktop
         2. Choose File > Clone Repository
-        3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        3. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         4. Choose a folder location
         5. Select Clone
 
@@ -98,19 +100,19 @@ body:
         **Option C: Command Line (CLI)**
 
         ```bash
-        # Step 1: Clone
-        git clone https://github.com/Community-Access/learning-room.git
-        cd learning-room
+        # Step 1: Clone (paste your Learning Room URL from the green Code button)
+        git clone https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git
+        cd learning-room-...-YOUR-USERNAME
 
         # Step 2: Create your branch
         git checkout -b fix/YOUR-USERNAME
 
         # Step 3: Edit a file (use your preferred editor)
-        # Open docs/chapter-XX.md and make a change
+        # Open README.md and improve a sentence or fix a typo
 
         # Step 4: Stage and commit
         git add .
-        git commit -m "fix: correct typo in chapter 5"
+        git commit -m "docs: improve README wording"
 
         # Step 5: Push
         git push -u origin fix/YOUR-USERNAME
@@ -143,7 +145,7 @@ body:
         | Symptom | Try this |
         |---|---|
         | Clone fails with authentication error | See [Appendix D: Git Authentication](https://github.com/Community-Access/git-going-with-github/blob/main/docs/appendix-d-git-authentication.md) for setup help. |
-        | Push fails with permission denied | Make sure you have write access to the repository. Ask your facilitator. |
+        | Push fails with permission denied | Make sure you cloned your own Learning Room repository (this repo), not another repository. If it still fails, ask your facilitator. |
         | I am not sure what to edit | Fix any typo, improve any sentence, or add a helpful comment. The content of the change matters less than the workflow. |
         | VS Code does not show the Source Control panel | Press Ctrl+Shift+G (Cmd+Shift+G on Mac). Make sure you opened the cloned folder as a workspace. |
         | I finished but want to check my work | [View the reference solution](https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-10-go-local.md) |
diff --git a/learning-room/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml b/learning-room/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
index 43b7e9e0..6a6b08dd 100644
--- a/learning-room/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
+++ b/learning-room/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml
@@ -23,7 +23,7 @@ body:
         ### Step-by-step instructions
 
         **Step 1: Check for a notification banner**
-        1. Go to the sci-fi themes repository on GitHub.com
+        1. Go to your Learning Room repository (this repo) on GitHub.com
         2. You may see a notification banner at the top saying "Your branch had recent pushes"
         3. If so, select **Compare & pull request** - this is a shortcut
         4. Skip to Step 3
diff --git a/work.md b/work.md
index 653b447f..2100e16d 100644
--- a/work.md
+++ b/work.md
@@ -639,7 +639,9 @@ Source template: [challenge-10-go-local.yml](https://github.com/Community-Access
 
 **Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
 
-**What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+**What you will do:** Clone your own Learning Room repository (this repo) to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+
+**Your repository URL:** On this repository's main page, select the green **Code** button and copy the HTTPS URL. It looks like `https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git`. You already have write access to this repo, so your push will work without any extra setup.
 
 #### The local workflow
 
@@ -659,7 +661,7 @@ This is the professional Git workflow you will use for the rest of your career:
 1. Open VS Code
 2. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette
 3. Type `Git: Clone`
-4. Paste this repository URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+4. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
 5. Choose a folder on your computer where you want to save it
 6. Wait for it to clone (you should see it in the file explorer)
 
@@ -696,7 +698,7 @@ This is the professional Git workflow you will use for the rest of your career:
 #### Step 1: Clone the repository
 1. Open GitHub Desktop
 2. Choose File > Clone Repository
-3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+3. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
 4. Choose a folder location
 5. Select Clone
 
@@ -727,19 +729,19 @@ This is the professional Git workflow you will use for the rest of your career:
 #### Option C: Command Line (CLI)
 
 ```bash
-## Step 1: Clone
-git clone https://github.com/Community-Access/learning-room.git
-cd learning-room
+## Step 1: Clone (paste your Learning Room URL from the green Code button)
+git clone https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git
+cd learning-room-...-YOUR-USERNAME
 
 ## Step 2: Create your branch
 git checkout -b fix/YOUR-USERNAME
 
 ## Step 3: Edit a file (use your preferred editor)
-## Open docs/chapter-XX.md and make a change
+## Open README.md and improve a sentence or fix a typo
 
 ## Step 4: Stage and commit
 git add .
-git commit -m "fix: correct typo in chapter 5"
+git commit -m "docs: improve README wording"
 
 ## Step 5: Push
 git push -u origin fix/YOUR-USERNAME
@@ -769,7 +771,7 @@ Compare your local tool choice with the peer-simulation PR notes or with a real
 | Symptom | Try this |
 |---|---|
 | Clone fails with authentication error | See [Appendix D: Git Authentication](https://github.com/Community-Access/git-going-with-github/blob/main/docs/appendix-d-git-authentication.md) for setup help. |
-| Push fails with permission denied | Make sure you have write access to the repository. Ask your facilitator. |
+| Push fails with permission denied | Make sure you cloned your own Learning Room repository (this repo), not another repository. If it still fails, ask your facilitator. |
 | I am not sure what to edit | Fix any typo, improve any sentence, or add a helpful comment. The content of the change matters less than the workflow. |
 | VS Code does not show the Source Control panel | Press Ctrl+Shift+G (Cmd+Shift+G on Mac). Make sure you opened the cloned folder as a workspace. |
 | I finished but want to check my work | [View the reference solution](https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-10-go-local.md) |
@@ -795,7 +797,7 @@ The PR creation step is the same. Git just moves you between locations.
 #### Step-by-step instructions
 
 #### Step 1: Check for a notification banner
-1. Go to the sci-fi themes repository on GitHub.com
+1. Go to your Learning Room repository (this repo) on GitHub.com
 2. You may see a notification banner at the top saying "Your branch had recent pushes"
 3. If so, select **Compare & pull request** - this is a shortcut
 4. Skip to Step 3