Community-Access · sam-cal1 · Mar 30, 2026 · Mar 30, 2026 · Mar 30, 2026 · Mar 31, 2026
diff --git a/docs/keyboard-shortcuts.md b/docs/keyboard-shortcuts.md
@@ -7,7 +7,7 @@ This reference lists keyboard shortcuts for navigating GitHub with a screen read
 
 #### NVDA (Windows)
 
-NVDA is a free, open source screen reader for Windows. Download it from [nvaccess.org](htps://nvaccess.org).
+NVDA is a free, open source screen reader for Windows. Download it from [nvaccess.org](https://nvaccess.org).
 
 #### Single-Key Navigation (Browse Mode)
 
@@ -37,8 +37,8 @@ Use these keys to jump to specific element types on any GitHub page.
 
 | Key | Action |
 |-----|--------|
-| NVDA+↓ desktop layout (NVDA+`a` laptop layout) | Start reading from cursor (Say All) |
-| NVDA+↑ | Read current line |
+ NVDA+↓ desktop layout (NVDA+`a` laptop layout) | Start reading from cursor (Say All) |
+| NVDA+↑ desktop layout (NVDA+l laptop layout)| Read current line |
 | Ctrl | Stop reading |
 
 ---

diff --git a/docs/samples/chapter-6-conflict-practice-sample.md b/docs/samples/chapter-6-conflict-practice-sample.md
@@ -4,16 +4,6 @@ Use this sample to understand what conflict markers look like and what the resol
 
 ## Conflict Marker Example
 
-```text
-<<<<<<< HEAD
-Use Command Palette to open settings.
-=======
-Open settings from the gear icon.
->>>>>>> feature/chapter-6-example
-```
-
-## Resolved Version Example
-
 ```text
 Open settings from Command Palette or the gear icon.
 ```

diff --git a/docs/setup-guide.md b/docs/setup-guide.md
@@ -20,7 +20,7 @@ If you don't already have a GitHub account, create one at [github.com/join](http
 
 GitHub has several accessibility settings that make navigation significantly easier with a screen reader. These settings are per-account and sync across devices.
 
-1. Navigate to [github.com/settings/accessibility](htps://github.com/settings/accessibility)
+1. Navigate to [github.com/settings/accessibility](https://github.com/settings/accessibility)
 2. Under "Motion", disable any animated effects if motion causes you difficulty
 3. Under "Tab size", set to your preferred number of spaces
 4. Confirm the page reads "Accessibility settings saved" before leaving
@@ -79,7 +79,7 @@ GitHub's hovercards appear when your mouse hovers over a username or repository.
 
 To make your own contributions, you need your own copy of the repository.
 
-1. Navigate to the workshop repository: [TODO: Add link to workshop repository here]
+1. Navigate to the workshop repository: [Community-Access/learning-room](https://github.com/Community-Access/learning-room)
 2. Find the "Fork" button in the top-right area of the page (navigate by button: B)
 3. Choose your GitHub account as the destination
 4. GitHub creates a fork: a copy of the repository that belongs to you

diff --git a/docs/welcome.md b/docs/welcome.md
@@ -21,7 +21,7 @@ You do not need to be a professional developer to contribute. Documentation, acc
 
 ## Who Can Contribute?
 
-[TODO: Add a paragraph explaining that contributors come from all backgrounds, skill levels, and countries. Emphasize that using assistive technology is not a barrier to contribution - in fact, AT users bring a perspective that improves projects for everyone.]
+ It is worth to say, that contributors come from all backgrounds, skill levels, and countries. And we have to emphasize that using assistive technology is not a barrier to contribution - in fact, AT users bring a perspective that improves projects for everyone.
 
 Everybody can contribute open source projects. Contributors come from all backgrounds, skill levels, and countries. Using assistive technologies is not a barrier to contributions. In fact, AT users bring a perspective which improves projects for everyone.
 
@@ -47,7 +47,7 @@ Most open source projects label issues that are suitable for new contributors. L
 - `help wanted`
 - `beginner`
 
-[TODO: Add two or three sentences about how to read an issue to decide if it is right for you. What questions should you ask yourself? Is the description clear enough? Is anyone else already working on it?]
+If we want to take an issue to work on it, we should first make sure that no one is working on it, and before that the description of the issue should be obvious, and we feel we have interest for it,  and we have the knowledge to fix it.
 
 ---
 
@@ -69,8 +69,8 @@ When your pull request is merged:
 - The issue you fixed is closed
 - You are officially listed as a contributor to this project
 
-[TODO: Add a sentence or two about what this means for someone's GitHub profile and open source portfolio.]
+Contributing to open source projects on GitHub not only strengthens your technical skills but also enhances your public profile, showcasing your collaboration and problem‑solving abilities. Each contribution becomes part of your open source portfolio, demonstrating your commitment to community‑driven development and making your work visible to potential employers, collaborators, and the wider developer community.  
 
 ---
 
-*Last reviewed: [DATE]*
+*Last reviewed: 2026-03-30*