diff --git a/website/blog/2026-06-08-copilot-config-files-guide.md b/website/blog/2026-06-08-copilot-config-files-guide.md
index 5ffa6eb..b4f81d8 100644
--- a/website/blog/2026-06-08-copilot-config-files-guide.md
+++ b/website/blog/2026-06-08-copilot-config-files-guide.md
@@ -51,8 +51,6 @@ This guide is my attempt to create that mental model. I want to know what each f
 
 *The folder-house metaphor emphasizes that these files live together, but each room has a different job.*
 
-<!-- truncate -->
-
 Those are the most commonly confused files. There are also `AGENTS.md` (an OpenAI/Anthropic agent convention — not a GitHub Copilot feature), hooks, and MCP configs. 
 
 ## The Copilot Instructions File: Governance Layer
diff --git a/website/blog/2026-06-20-squad-first-impressions.md b/website/blog/2026-06-20-squad-first-impressions.md
index 9e51326..386bed0 100644
--- a/website/blog/2026-06-20-squad-first-impressions.md
+++ b/website/blog/2026-06-20-squad-first-impressions.md
@@ -35,8 +35,6 @@ This post came from a coworker asking me, "Why Squad?"
 
 ![Watercolor illustration of a sunlit woodworking workshop with a team working on projects.](./media/2026-06-20-squad-first-impressions/2026-06-20-squad-first-impressions-watercolor-1-hero.png)
 
-<!-- truncate -->
-
 ## Why Squad feels different from Copilot
 
 Before Squad, my workflow was simple: open Copilot and ask one agent for everything. That works well for plenty of tasks, but it is still one perspective.