diff --git a/01-setup-and-first-steps/README.md b/01-setup-and-first-steps/README.md
index ba53741b..13afdafe 100644
--- a/01-setup-and-first-steps/README.md
+++ b/01-setup-and-first-steps/README.md
@@ -325,7 +325,7 @@ Step 4: Test the flow
 Proceed with implementation? [Y/n]
 ```
 
-**Key insight**: Plan mode lets you review and modify the approach before any code is written. Once a plan is complete, you can even tell Copilot CLI to save it to a file for later reference. For example, "Save this plan to `mark_as_read_plan.md`" would create a markdown file with the plan details.
+**Key insight**: Plan mode lets you review and modify the approach before any code is written. While in plan mode, Copilot CLI is **read-only** and will not edit any files or run commands that change your workspace until you approve and move to implementation. This keeps you safely in the "thinking" stage until you're ready. Once a plan is complete, you can even tell Copilot CLI to save it to a file for later reference. For example, "Save this plan to `mark_as_read_plan.md`" would create a markdown file with the plan details.
 
 > 💡 **Want something more complex?** Try: `/plan Add search and filter capabilities to the book app`. Plan mode scales from simple features to full applications.
 
diff --git a/04-agents-custom-instructions/README.md b/04-agents-custom-instructions/README.md
index 44c93a93..a286a570 100644
--- a/04-agents-custom-instructions/README.md
+++ b/04-agents-custom-instructions/README.md
@@ -107,6 +107,7 @@ What about the Task Agent? It works behind the scenes to manage and track what i
 | ✅ **Success** | Brief summary (e.g., "All 247 tests passed", "Build succeeded") |
 | ❌ **Failure** | Full output with stack traces, compiler errors, and detailed logs |
 
+> 💡 **Multi-turn subagents**: Subagents (background tasks launched by agents) support follow-up messages. While an agent is running in the background, you can open `/tasks` to view it and send follow-up instructions. You don't have to wait for it to finish before guiding it further. Think of it like being able to tap your assistant on the shoulder mid-task to give extra direction.
 
 > 📚 **Official Documentation**: [GitHub Copilot CLI Agents](https://docs.github.com/copilot/how-tos/use-copilot-agents/use-copilot-cli#use-custom-agents)
 
diff --git a/05-skills/README.md b/05-skills/README.md
index 7036d2c7..80e5bad0 100644
--- a/05-skills/README.md
+++ b/05-skills/README.md
@@ -532,10 +532,10 @@ Once you're in an interactive Copilot session, use `/skills` (or its shortcut `/
 # From the terminal (no interactive session needed):
 copilot skill list
 
-Available skills:
+Project skills:
 - security-audit: Security-focused code review checking OWASP Top 10
 - generate-tests: Generate comprehensive unit tests with edge cases
-- code-checklist: Team code quality checklist
+- code-checklist: Team code quality checklist (disabled)
 ...
 
 # Or from inside a Copilot session:
@@ -543,10 +543,10 @@ copilot
 
 > /skills list
 
-Available skills:
+Project skills:
 - security-audit: Security-focused code review checking OWASP Top 10
 - generate-tests: Generate comprehensive unit tests with edge cases
-- code-checklist: Team code quality checklist
+- code-checklist: Team code quality checklist (disabled)
 ...
 
 > /skills info security-audit
@@ -557,6 +557,8 @@ Location: .github/skills/security-audit/SKILL.md
 Description: Security-focused code review checking OWASP Top 10 vulnerabilities
 ```
 
+> 💡 **Disabled skills**: Skills marked as `(disabled)` are installed but not currently active. They won't be triggered by prompts until re-enabled. This can happen if a skill's `SKILL.md` file has a configuration issue, or if the skill was explicitly disabled. You can enable/disable skills by running `/skills`.
+
 ---
 
 <details>