@@ -220,9 +220,9 @@ <h3>Pre-Workshop Setup</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/ch-01-pre-workshop-setup.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-01-pre-workshop-setup.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep01-pre-workshop-setup.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome to Git Going with GitHub. Before the workshop really begins, this episode is about getting everything ready so Day 1 can start with learning, not troubleshooting.</p><p><strong>Jamie:</strong> And that matters a lot for this audience, right? Because setup is never just setup. It can include browser quirks, screen reader settings, account security, and a bunch of little choices that affect whether GitHub feels smooth or frustrating.</p><p><strong>Alex:</strong> Exactly. This is a Community Access workshop, and the core message is: please do this at least one day before the event. If something goes wrong, use the Community Access support repository and support discussions so help can happen before class time.</p><p><strong>Jamie:</strong> I also noticed a big theme here: tools change.</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. This episode is all about getting ready before Day 1, so the workshop can start with learning instead of setup problems. Please try to finish this at least one day before the event, and if you want the bigger map first, the Get Going with GitHub guide explains GitHub Classroom, your Learning Room repository, Challenge 1, evidence prompts, and tool choices.</p><p><strong>Jamie:</strong> I like that this is pre-work, but not busy work. It&#39;s the stuff that keeps you from getting stuck when everyone else is opening issues, making commits, and trying their first pull request.</p><p><strong>Alex:</strong> Exactly. You&#39;ll want a Windows or macOS computer, a reliable internet connection, and headphones if you&#39;re using screen reader audio during group sessions. Linux users can still follow the Git installation path, but the workshop hardware guidance focuses on Windows and macOS.</p><p><strong>Jamie:</strong> And the software side is a modern browser, a screen reader, and a GitHub account, right? Chrome or Firefox are recommended for GitHub, Edge is fine on Windows, and Safari is usually the best match for VoiceOver on macOS.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">
 
@@ -220,9 +220,9 @@ <h3>Choose Your Tools</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/agents-04-choose-your-tools.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/agents-04-choose-your-tools.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep44-choose-your-tools.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Before anyone writes code or worries about commands, we need a map of the tools. This lesson is a guided tour of five different ways to work with GitHub: the website, a browser-based editor, a desktop editor, a desktop Git app, and the command line.</p><p><strong>Jamie:</strong> So the big idea is not, pick one forever. It&#39;s, learn the landscape so later instructions make sense.</p><p><strong>Alex:</strong> Exactly. And that matters because there is no single right way to use GitHub. Some people prefer the browser. Some want a visual desktop app. Some love a terminal. Many people switch tools depending on the task.</p><p><strong>Jamie:</strong> That feels especially important for accessibility. If one path works better with your screen reader or your low vision setup, that path is valid.</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re doing something that can save a lot of frustration later: choosing the tool that fits the job, instead of assuming there is one correct way to use GitHub.</p><p><strong>Jamie:</strong> I like that framing, because people can feel behind before they even start. One person is in a browser, someone else is in VS Code, someone else is using a terminal, and it can sound like they are all in different workshops.</p><p><strong>Alex:</strong> They are using different doors into the same work. The workshop supports multiple tool paths because real teams do that too. A chapter might say, &quot;open the file,&quot; and your job is to know whether that means the GitHub website, github.dev, VS Code, GitHub Desktop, or the GitHub CLI for you.</p><p><strong>Jamie:</strong> So we are not choosing a tool forever. We are learning what each one is good at, what it cannot do, and how it feels with a screen reader or low vision setup.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">
 
@@ -220,9 +220,9 @@ <h3>Understanding GitHub on the Web</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/ch-02-github-web-structure.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-02-github-web-structure.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep02-github-web-structure.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Before we do deeper GitHub work, we need a mental map. If GitHub has ever felt like a maze of tabs, sidebars, and pages that all blur together, this lesson is here to fix that.</p><p><strong>Jamie:</strong> And this is especially important for learners using screen readers, magnification, zoom, high contrast themes, or just anyone who wants a reliable way to know, where am I, and what kind of page is this?</p><p><strong>Alex:</strong> Exactly. And one quick administrative note before we begin: this lesson pairs with an audio episode and with two appendices, a glossary and a screen reader cheat sheet. It also points learners to GitHub&#39;s own docs and GitHub accessibility documentation as the authoritative references.</p><p><strong>Jamie:</strong> So this is not just theory. It&#39;s the orientation system for everything that comes next.</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re building the map you use before you click anything on GitHub. GitHub can feel like one giant website, but it makes more sense when you know what level you&#39;re on and what landmarks are always nearby.</p><p><strong>Jamie:</strong> I like starting there, because the confusing moment is usually not, &quot;What button do I press?&quot; It&#39;s, &quot;Where am I, and what kind of page is this?&quot;</p><p><strong>Alex:</strong> Exactly. GitHub has three nested levels. Level one is your own account area, like your profile, settings, and notifications. Level two is a user or organization space, such as github.com/github or github.com/community-access. Level three is a repository, and that is where issues, pull requests, code, actions, branches, and files live.</p><p><strong>Jamie:</strong> So when a workshop says, &quot;go to the repo,&quot; it usually means that third level. And for Challenge 01, Find Your Way Around, learners will practice that inside their own Learning Room repository, which is provisioned for each learner.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">
 
@@ -220,9 +220,9 @@ <h3>Navigating Repositories</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/ch-03-navigating-repositories.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-03-navigating-repositories.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep03-navigating-repositories.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting comfortable inside GitHub repositories: how they&#39;re laid out, how to orient yourself quickly with a screen reader or keyboard, and how to move from, &quot;I found a repo,&quot; to, &quot;I actually know where things are.&quot;</p><p><strong>Jamie:</strong> And this is one of those chapters where the goal is not speed, right? It&#39;s confidence.</p><p><strong>Alex:</strong> Exactly. This is a foundation lesson. There are no challenge tasks here, no automation checks. The point is to build a reliable mental map before later chapters ask you to work with issues, pull requests, and traceable contributions.</p><p><strong>Jamie:</strong> So if someone&#39;s feeling pressure to perform already, this is a good place to exhale.</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting comfortable inside a GitHub repository, which is the place most of your collaboration work starts.</p><p><strong>Jamie:</strong> And repository is one of those words people hear constantly, but it can still feel fuzzy. What is it, in plain language?</p><p><strong>Alex:</strong> A repository is a project folder tracked by Git. It can hold code, documents, images, configuration files, and the history of changes to all of those files. On GitHub, the repository page is the web view of that project.</p><p><strong>Jamie:</strong> So when I open a repo, I&#39;m not just looking at a file cabinet. I&#39;m looking at the current project plus its memory.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">
 
@@ -220,9 +220,9 @@ <h3>The Learning Room</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/ch-04-the-learning-room.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-04-the-learning-room.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep04-the-learning-room.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting oriented to something you&#39;ll use constantly in the workshop: your Learning Room. Think of it as your personal practice repository on GitHub, built so you can learn the full workflow safely and realistically.</p><p><strong>Jamie:</strong> So this is not just a folder somewhere. It&#39;s an actual GitHub repository with issues, branches, pull requests, and automation?</p><p><strong>Alex:</strong> Exactly. When you accept the GitHub Classroom assignment, GitHub makes a private copy of the workshop template repository for you. That copy lives in the workshop organization and is named something like learning-room-your-username. You get write access to that repo. You can create branches there, open pull requests there, and receive automated feedback there.</p><p><strong>Jamie:</strong> And just to clear up a very common beginner question: am I supposed to work in the original template repository?</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting oriented in the Learning Room, which is your private practice repository for Day 1 of the workshop.</p><p><strong>Jamie:</strong> I like starting there, because a new GitHub repository can feel like walking into a room with a lot of unlabeled doors.</p><p><strong>Alex:</strong> Exactly. The Learning Room is a GitHub repo created for you through GitHub Classroom. It starts from the Community-Access/learning-room-template repository, but your copy lives in the workshop organization with a name like &lt;workshop-org&gt;/learning-room-&lt;your-username&gt;.</p><p><strong>Jamie:</strong> So I am not editing the template repository itself.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">
 
@@ -220,9 +220,9 @@ <h3>Working with Issues</h3>
       <p class="companion-links">
         <a href="https://lp.csedesigns.com/ggg/media/ch-05-working-with-issues.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-05-working-with-issues.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep05-working-with-issues.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
-      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re working with one of the most important parts of GitHub: issues.</p><p><strong>Jamie:</strong> And for a lot of learners, this is where GitHub starts to feel social, right? Not just files and commits, but conversation.</p><p><strong>Alex:</strong> Exactly. Issues are where people report bugs, request features, ask for clarification, track chores, and coordinate work. In open source, a lot of collaboration begins there.</p><p><strong>Alex:</strong> Before we get into the mechanics, a few support notes matter here. This chapter pairs well with the official GitHub documentation about issues, GitHub&#39;s accessibility guide for issues, and the GitHub Accessibility Lab CLI guide. There are also related appendices on advanced search, GitHub Mobile, and a screen reader cheat sheet.</p></details>
+      <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re working with GitHub issues, which are often where collaboration starts.</p><p><strong>Jamie:</strong> And an issue can be a bug report, but it&#39;s not only bugs, right?</p><p><strong>Alex:</strong> Right. An issue is a trackable unit of work. It might be a bug, a feature request, a question, a documentation chore, or a note that says, something needs attention here.</p><p><strong>Jamie:</strong> So it is the shared place where people agree on what needs to happen before anyone starts changing files.</p></details>
     </article>
   </section>
       <nav id="on-this-page" class="onpage-nav" aria-label="On this page">