docs: hyperlink repo name mentions to their GitHub URLs

learning-room, accessibility-agents, git-going-with-github, and
vscode-sci-fi-themes backtick mentions replaced with markdown links.
63 replacements across 20 files. Code blocks and shell examples untouched.

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

Author: taylorarndt

docs/02-navigating-repositories.md

@@ -640,7 +640,7 @@ Navigate to the [Accessibility Agents repository](https://github.com/community-a
 
 > ### Day 2 Amplifier - Accessibility Agents: `@daily-briefing`
 >
-> **Navigate every folder of `accessibility-agents` manually today before using any agent.** Find `.github/agents/`, open a `.agent.md` file, and read it - that file is how an agent knows what to do. You must understand the structure before you can evaluate whether an agent understood it correctly.
+> **Navigate every folder of [accessibility-agents](https://github.com/Community-Access/accessibility-agents) manually today before using any agent.** Find `.github/agents/`, open a `.agent.md` file, and read it - that file is how an agent knows what to do. You must understand the structure before you can evaluate whether an agent understood it correctly.
 >
 > Once you have mastered manual repository navigation:
 >

docs/03-the-learning-room.md

@@ -55,7 +55,7 @@ Throughout Day 1, you work on **two parallel learning tracks**:
 - **Block 5:** Your first real contribution (you and 5-20 other students contributing simultaneously)
 - **Block 6:** Community tools (labels, milestones, notifications)
 
-**Scope:** The shared `learning-room` repository (one repo, visible to everyone)  
+**Scope:** The shared [learning-room](https://github.com/Community-Access/learning-room) repository (one repo, visible to everyone)  
 **Bot:** The Learning Room automation bot validates PRs and tracks progress  
 **Pace:** Structured by facilitator; synchronized with workshop schedule  
 **Purpose:** Collaborative practice of the full workflow (issue → branch → PR → review → merge)

docs/04-working-with-issues.md

@@ -44,9 +44,9 @@ Chapter 4 is the first **issue-based challenge chapter** with short, confidence-
 
 **Goal:** File a new issue in the Learning Room repository with a specific title and a meaningful description.
 
-**Where you are working:** the Issues tab of the `learning-room` repository on GitHub.com.
+**Where you are working:** the Issues tab of the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com.
 
-1. Open the `learning-room` repository in your browser.
+1. Open the [learning-room](https://github.com/Community-Access/learning-room) repository in your browser.
 2. Navigate to the **Issues** tab (press `G` then `I` to jump there with keyboard shortcuts, or find the "Issues" link in the repository navigation).
 3. Activate the **New issue** button.
 4. If a template picker appears, select **Open a blank issue** (or choose a template if one fits).
@@ -67,9 +67,9 @@ Chapter 4 is the first **issue-based challenge chapter** with short, confidence-
 
 **Goal:** Leave a comment on another student's issue and use an @mention to notify them.
 
-**Where you are working:** the Issues tab of the `learning-room` repository on GitHub.com.
+**Where you are working:** the Issues tab of the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com.
 
-1. Open the **Issues** tab in the `learning-room` repository.
+1. Open the **Issues** tab in the [learning-room](https://github.com/Community-Access/learning-room) repository.
 2. Find an issue created by a classmate (look for issues from Challenge 4.1, or browse recent open issues).
 3. Open the issue by activating its title link.
 4. Read the issue description to understand what they reported.
@@ -204,7 +204,7 @@ An issue is a discussion thread attached to a repository. Issues are used for:
 
 Every issue has a **number** (`#42`), a **state** (Open or Closed), a **title**, a **description**, and a **comment thread**. Issues are public by default on public repositories.
 
-> **Learning Room connection:** In the `learning-room` repo, every challenge from `docs/CHALLENGES.md` becomes an issue. For example, Challenge 1 ("Fix Broken Link") is filed as an issue pointing to `docs/welcome.md`, describing the broken link and linking to the challenge success criteria. When you open a PR to fix it, you reference the issue with `Closes #XX` to automatically close it on merge.
+> **Learning Room connection:** In the [learning-room](https://github.com/Community-Access/learning-room) repo, every challenge from `docs/CHALLENGES.md` becomes an issue. For example, Challenge 1 ("Fix Broken Link") is filed as an issue pointing to `docs/welcome.md`, describing the broken link and linking to the challenge success criteria. When you open a PR to fix it, you reference the issue with `Closes #XX` to automatically close it on merge.
 
 
 ## Navigating to the Issues List
@@ -1060,7 +1060,7 @@ Go to the Learning Room repository and file a real issue:
 > Once you have mastered manual issue management:
 >
 > - **In VS Code** - `@issue-tracker find open issues labeled good-first-issue` searches cross-repository with community sentiment scoring, release-awareness prioritization, and batch-reply capability across every repo you have access to
-> - **In your repo** - The issue templates in `accessibility-agents/.github/ISSUE_TEMPLATE/` structure both human filing and automated triage; fork `accessibility-agents` and that structure travels into any project you lead
+> - **In your repo** - The issue templates in `accessibility-agents/.github/ISSUE_TEMPLATE/` structure both human filing and automated triage; fork [accessibility-agents](https://github.com/Community-Access/accessibility-agents) and that structure travels into any project you lead
 > - **In the cloud** - GitHub Agentic Workflows triage new issues the moment they are opened: applying labels, posting first-response comments, adding to Project boards - the same triage actions you practiced manually today, running at scale
 >
 > *Today you are the triage engine. On Day 2, you understand the engine well enough to direct it.*

docs/05-vscode-accessibility.md

@@ -32,7 +32,7 @@ For this workshop, Chapter 5 is a **guided setup chapter** with a lightweight co
 
 **Estimated time:** 10-15 minutes.
 
-1. Open the `learning-room` repository on GitHub.com.
+1. Open the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com.
 2. Press `.` (the period key) on your keyboard. This launches **github.dev** - a full VS Code editor running in your browser. Wait a few seconds for it to load.
 3. Enable screen reader mode:
    - **Windows (NVDA/JAWS):** Press `Shift+Alt+F1`. You should hear an announcement confirming screen reader mode is on.
@@ -136,7 +136,7 @@ GitHub's browser interface is excellent for reviewing, discussing, and triaging.
 | Run Accessibility Agents | Not available | Copilot Chat with agent files |
 | See errors in your contribution | After push | Real-time as you type |
 
-For Markdown contributions (which is most of what `accessibility-agents` needs), VS Code gives you Copilot assistance, live preview, and the same Git workflow - with less tab switching and with agents available on every file you open.
+For Markdown contributions (which is most of what [accessibility-agents](https://github.com/Community-Access/accessibility-agents) needs), VS Code gives you Copilot assistance, live preview, and the same Git workflow - with less tab switching and with agents available on every file you open.
 
 
 ---

docs/06-working-with-pull-requests.md

@@ -47,7 +47,7 @@ Chapter 6 is the first **PR-validated chapter** where students convert issue wor
 
 **Goal:** Edit one of the practice files and save your change on a new branch.
 
-**Where you are working:** the `learning-room` repository on GitHub.com, using the web editor.
+**Where you are working:** the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com, using the web editor.
 
 **Before you start:** Open your **assigned Chapter 6.1 challenge issue** (the one titled "Chapter 6.1: Create One Small Branch Change (@yourname)"). The issue description tells you which file to edit and what to fix.
 
@@ -63,7 +63,7 @@ The following table summarizes the practice files in the learning-room, what eac
 
 **Steps using the web editor:**
 
-1. In the `learning-room` repository, navigate to the file specified in your issue. Use the file tree or the "Go to file" button (`T` keyboard shortcut).
+1. In the [learning-room](https://github.com/Community-Access/learning-room) repository, navigate to the file specified in your issue. Use the file tree or the "Go to file" button (`T` keyboard shortcut).
 2. Open the file and activate the **pencil icon** (Edit this file) button.
    - Screen reader users (NVDA/JAWS): Press `B` to navigate buttons, find "Edit this file," and press `Enter`.
    - VoiceOver users: Press `VO+U`, open Buttons rotor, find "Edit this file," and press `VO+Space`.
@@ -1240,7 +1240,7 @@ Go to the Learning Room repository's Pull Requests tab and find any open or rece
 > Once you have mastered manual pull request review:
 >
 > - **In VS Code** - `@pr-review review PR #N` generates line-numbered diffs with change maps, risk assessment, before/after snapshots, CI results, and suggested inline comments - a documented starting point for your own review, not a replacement for it
-> - **In your repo** - Accessibility Agents' review capabilities work across every repository you have access to by default; fork `accessibility-agents` and those capabilities travel with your project from day one
+> - **In your repo** - Accessibility Agents' review capabilities work across every repository you have access to by default; fork [accessibility-agents](https://github.com/Community-Access/accessibility-agents) and those capabilities travel with your project from day one
 > - **In the cloud** - GitHub Agentic Workflows can auto-generate PR descriptions, verify linked issues, and post accessibility impact summaries on a `pull_request` trigger - running the moment a PR is opened, whether or not anyone is watching
 >
 > *The agent documents the diff. You bring the context that no diff can contain.*

docs/07-merge-conflicts.md

@@ -26,7 +26,7 @@ Chapter 7 uses **one controlled practice challenge** so students can learn confl
 
 **Goal:** Identify the three types of conflict markers in a practice file, decide which content to keep, remove the markers, and submit a clean PR.
 
-**Where you are working:** the `learning-room` repository on GitHub.com (web editor) or in VS Code if you cloned locally.
+**Where you are working:** the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com (web editor) or in VS Code if you cloned locally.
 
 **Before you start:** Open your **assigned Chapter 7 challenge issue** (the one titled "Chapter 7.1: Resolve Conflict Markers (@yourname)"). The issue description tells you which practice file contains the conflict markers.
 

docs/08-culture-etiquette.md

@@ -24,7 +24,7 @@ Chapter 8 is a **communication and culture chapter**.
 
 **Goal:** Identify three concrete communication behaviors you will practice during the rest of the workshop.
 
-**Where you are working:** your assigned Chapter 8 challenge issue in the `learning-room` repository on GitHub.com.
+**Where you are working:** your assigned Chapter 8 challenge issue in the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com.
 
 1. Read through the chapter content below, paying attention to the sections on GitHub Flow, constructive feedback, and asking for help.
 2. As you read, think about one situation from Day 1 where communication helped (or could have helped) you.

docs/09-labels-milestones-projects.md

@@ -24,9 +24,9 @@ Chapter 9 is a **guided triage chapter** focused on organization skills.
 
 **Goal:** Read the details of a Learning Room issue and post a structured triage recommendation that a maintainer could act on immediately.
 
-**Where you are working:** your assigned Chapter 9 challenge issue in the `learning-room` repository on GitHub.com, plus one other open issue you will triage.
+**Where you are working:** your assigned Chapter 9 challenge issue in the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com, plus one other open issue you will triage.
 
-1. Open the **Issues** tab in the `learning-room` repository.
+1. Open the **Issues** tab in the [learning-room](https://github.com/Community-Access/learning-room) repository.
 2. Find any **open issue** that does not already have labels applied (or pick one your facilitator assigns).
 3. Read the issue title and full description carefully. Note:
    - What type of work is it? (documentation fix, bug report, accessibility improvement, new content)
@@ -488,7 +488,7 @@ Or from within a project:
 
 ## Practical Organization Strategy for the Hackathon
 
-Here is a recommended structure for the `learning-room` sandbox project:
+Here is a recommended structure for the [learning-room](https://github.com/Community-Access/learning-room) sandbox project:
 
 ### Labels to create
 

docs/10-notifications.md

@@ -24,11 +24,11 @@ For this workshop, Chapter 10 is a **guided practice chapter**, not a graded aut
 
 **Goal:** Set up a useful notification workflow so you can keep up with reviews, mentions, and assignments without inbox overload.
 
-**Where you are working:** the GitHub.com notifications page and the `learning-room` repository settings.
+**Where you are working:** the GitHub.com notifications page and the [learning-room](https://github.com/Community-Access/learning-room) repository settings.
 
 **Estimated time:** 5-8 minutes.
 
-1. Open the `learning-room` repository on GitHub.com.
+1. Open the [learning-room](https://github.com/Community-Access/learning-room) repository on GitHub.com.
 2. Find the **Watch** button near the top-right of the repository page (next to Star and Fork).
 3. Activate the **Watch** dropdown and select **Participating and @mentions**. This means you only get notified when someone @mentions you or you are directly participating in a thread.
 4. Open the notifications inbox by navigating to `https://github.com/notifications` (or activate the bell icon in the GitHub header).
@@ -454,7 +454,7 @@ Go to [github.com/notifications](https://github.com/notifications) and practice:
 > Once you have mastered manual notification management:
 >
 > - **In VS Code** - `@daily-briefing morning briefing` delivers the same information as your notification inbox, organized by priority and actionability, with the ability to reply, close, and merge from inside Copilot Chat
-> - **In your repo** - Fork `accessibility-agents` and every collaborator on your project can run `@daily-briefing` against your shared repository; the whole team stays aligned from a single command with no inbox required
+> - **In your repo** - Fork [accessibility-agents](https://github.com/Community-Access/accessibility-agents) and every collaborator on your project can run `@daily-briefing` against your shared repository; the whole team stays aligned from a single command with no inbox required
 > - **In the cloud** - GitHub Agentic Workflows can run on a schedule and post a team digest to a designated issue each morning, surfacing what needs attention before anyone opens their notifications
 >
 > *Your notification discipline today becomes the standard the agent enforces at scale tomorrow.*

docs/11-git-source-control.md

@@ -24,13 +24,13 @@ Chapter 11 is the first **local Git workflow chapter** with hands-on repository
 
 ### Chapter 11 Challenge Set
 
-1. **Clone the sci-fi themes repository** - clone `vscode-sci-fi-themes` to your local machine using VS Code.
+1. **Clone the sci-fi themes repository** - clone [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes) to your local machine using VS Code.
 2. **Create a branch and make one commit** - create a named branch, edit a theme file, stage, write a clear commit message, and commit locally.
 3. **Push and open a linked PR** - push your branch and open a PR that references your challenge issue.
 
 ### Challenge 11.1 Step-by-Step: Clone the Sci-Fi Themes Repository
 
-**Goal:** Get a local copy of the `vscode-sci-fi-themes` repository on your machine using VS Code.
+**Goal:** Get a local copy of the [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes) repository on your machine using VS Code.
 
 **Where you are working:** VS Code desktop (or github.dev if you cannot install desktop VS Code).
 
@@ -47,7 +47,7 @@ This repo contains custom Copilot Chat loading phrases from three sci-fi univers
 
 **Screen reader tip:** After step 6, VS Code shows a progress notification. NVDA reads this automatically. If you hear nothing for 30 seconds, open the Command Palette and run `Notifications: Focus Notification Toast` to check status.
 
-**You are done when:** The `vscode-sci-fi-themes` folder is open in VS Code and you can see the `themes/` folder with its three JSON files (star-trek, hitchhikers, star-wars) in the Explorer panel.
+**You are done when:** The [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes) folder is open in VS Code and you can see the `themes/` folder with its three JSON files (star-trek, hitchhikers, star-wars) in the Explorer panel.
 
 > **After cloning: check what branches exist.** A fresh clone only checks out the default branch (usually `main`), but the remote may have other branches. Run `git branch -a` in the terminal (`Ctrl+`` `) to see all branches - local and remote:
 >
@@ -70,7 +70,7 @@ This repo contains custom Copilot Chat loading phrases from three sci-fi univers
 
 **Goal:** Create a properly named branch, edit a theme file, stage the change, and commit with a clear message.
 
-**Where you are working:** VS Code with the cloned `vscode-sci-fi-themes` repository open.
+**Where you are working:** VS Code with the cloned [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes) repository open.
 
 1. Open the Command Palette: `Ctrl+Shift+P` (Mac: `Cmd+Shift+P`).
 2. Type `git create branch` and select **Git: Create Branch...**
@@ -105,13 +105,13 @@ This repo contains custom Copilot Chat loading phrases from three sci-fi univers
 
 **Screen reader tip:** The "Compare & pull request" banner is a standard link element near the top of the repository page. If your screen reader does not find it, use the heading navigation to jump to the Pull Requests tab instead.
 
-**Cross-repo linking:** Because your challenge issue lives in `learning-room` but your PR is in `vscode-sci-fi-themes`, you use the full format `Closes Community-Access/learning-room#XX` instead of just `Closes #XX`. GitHub resolves cross-repo references automatically.
+**Cross-repo linking:** Because your challenge issue lives in [learning-room](https://github.com/Community-Access/learning-room) but your PR is in [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes), you use the full format `Closes Community-Access/learning-room#XX` instead of just `Closes #XX`. GitHub resolves cross-repo references automatically.
 
-**You are done when:** Your PR appears on the Pull requests tab of `vscode-sci-fi-themes`, shows your branch name, and the description contains the cross-repo reference to your challenge issue.
+**You are done when:** Your PR appears on the Pull requests tab of [vscode-sci-fi-themes](https://github.com/Community-Access/vscode-sci-fi-themes), shows your branch name, and the description contains the cross-repo reference to your challenge issue.
 
 ### Completing Chapter 11: Submit Your Evidence
 
-Open your **assigned Chapter 11.3 challenge issue** in the `learning-room` repo and post a completion comment:
+Open your **assigned Chapter 11.3 challenge issue** in the [learning-room](https://github.com/Community-Access/learning-room) repo and post a completion comment:
 
 ```text
 Chapter 11 completed: