Update all chapter numbers and references throughout the book

DavidLiedle · claude · DavidLiedle · commit ff57eebf01ee · 2025-10-02T10:51:53.000-06:00
Major updates: - Renumbered all chapters 1-16 (was incorrectly 3-18) - Updated all front matter titles in chapter files - Fixed Table of Contents with correct chapter numbers - Updated homepage and README to reflect 16 chapters - Fixed sample quote reference (Chapter 3, not 5) - Clarified book structure: Introduction + 16 Chapters + Conclusion + Appendix The book now properly shows: - Introduction (before Chapter 1) - Chapters 1-16 (the main content) - Conclusion - Appendix 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/01-table-of-contents.md b/01-table-of-contents.md
@@ -17,25 +17,25 @@ nav_order: 2
 ## Part I: The Bitter Pill
 *Understanding the medicine you're about to take*
 
-### Chapter 3: The Problem React Claims to Solve (That Wasn't Really a Problem)
+### Chapter 1: The Problem React Claims to Solve (That Wasn't Really a Problem)
 - The "jQuery Spaghetti" Myth
 - Two-Way Data Binding: The Devil We Knew
 - Facebook's First World Problems
 - When Simple Became Complex
 
-### Chapter 4: JavaScript Fatigue: How We Got Here
+### Chapter 2: JavaScript Fatigue: How We Got Here
 - The Great Framework Wars of 2010-2020
 - NPM: The Package Manager That Ate the World
 - Build Tools: A Love Story Gone Wrong
 - The Day HTML Stopped Being Enough
 
-### Chapter 5: The Virtual DOM: A Beautiful Lie
+### Chapter 3: The Virtual DOM: A Beautiful Lie
 - What the Virtual DOM Actually Is
 - The Performance Promise That Wasn't
 - Reconciliation: Making Simple Things Complicated
 - Why Direct DOM Manipulation Became "Bad"
 
-### Chapter 6: JSX: When HTML and JavaScript Had a Baby Nobody Asked For
+### Chapter 4: JSX: When HTML and JavaScript Had a Baby Nobody Asked For
 - XML in JavaScript: What Could Go Wrong?
 - The Transpilation Tax
 - Why className and htmlFor Exist
@@ -46,31 +46,31 @@ nav_order: 2
 ## Part II: Swallowing the Medicine
 *Learning React while maintaining your sanity*
 
-### Chapter 7: Components: Everything is a Nail When You Have a Hammer
+### Chapter 5: Components: Everything is a Nail When You Have a Hammer
 - The Component All The Things Philosophy
 - Functional vs Class: The Civil War
 - When a Div Would Have Been Fine
 - Props: Passing Problems Down the Tree
 
-### Chapter 8: State Management: Choose Your Own Adventure in Hell
+### Chapter 6: State Management: Choose Your Own Adventure in Hell
 - Local State: The Gateway Drug
 - Lifting State Up: Musical Chairs with Data
 - Context API: Prop Drilling's Complicated Brother
 - Redux: When You Need a Library to Manage a Library
 
-### Chapter 9: Hooks: The Magic That Makes You Miss Classes
+### Chapter 7: Hooks: The Magic That Makes You Miss Classes
 - useState: Because Functions Need Memory Too
 - The Rules of Hooks: Arbitrary but Mandatory
 - Custom Hooks: Abstracting Your Abstractions
 - Why Everything Starts with "use"
 
-### Chapter 10: useEffect: The Footgun You'll Shoot Yourself With
+### Chapter 8: useEffect: The Footgun You'll Shoot Yourself With
 - ComponentDidMount's Evil Twin
 - The Dependency Array of Doom
 - Cleanup Functions: Forgetting Them Since 2019
 - Infinite Loops and How to Love Them
 
-### Chapter 11: Props Drilling: Pass It Down, Pass It Down, Pass It Down...
+### Chapter 9: Props Drilling: Pass It Down, Pass It Down, Pass It Down...
 - The Christmas Tree of Props
 - When Your Component Needs Its Grandparent's Data
 - Context to the Rescue (Sort Of)
@@ -81,25 +81,25 @@ nav_order: 2
 ## Part III: Making Peace
 *Finding the balance between React's way and sanity*
 
-### Chapter 12: Patterns and Anti-Patterns: The Good, The Bad, The React
+### Chapter 10: Patterns and Anti-Patterns: The Good, The Bad, The React
 - Container/Presentational: Separation That Isn't
 - Higher-Order Components: Inception for Code
 - Render Props: Functions Returning Functions Returning JSX
 - Compound Components: When Simple Gets Complicated
 
-### Chapter 13: Performance: When React is Actually Fast (Sometimes)
+### Chapter 11: Performance: When React is Actually Fast (Sometimes)
 - The Myths of React Performance
 - React.memo: Memoizing Your Mistakes
 - useMemo and useCallback: Premature Optimization Central
 - When Re-renders Actually Matter
 
-### Chapter 14: Testing React: Because Your Components Need Therapy Too
+### Chapter 12: Testing React: Because Your Components Need Therapy Too
 - Unit Testing Components: Mocking the Universe
 - React Testing Library: Not Testing Implementation Details (Allegedly)
 - Snapshot Testing: The Lie Detector That Lies
 - E2E Testing: When You've Given Up on Unit Tests
 
-### Chapter 15: The Ecosystem: 47 Ways to Build the Same Thing
+### Chapter 13: The Ecosystem: 47 Ways to Build the Same Thing
 - Create React App vs Next.js vs Gatsby vs Vite vs...
 - CSS-in-JS: Because Regular CSS Wasn't Complicated Enough
 - Form Libraries: Solving Problems You Didn't Know You Had
@@ -110,19 +110,19 @@ nav_order: 2
 ## Part IV: Stockholm Syndrome
 *Learning to love your captor*
 
-### Chapter 16: Building Something Real: A Todo App (Of Course)
+### Chapter 14: Building Something Real: A Todo App (Of Course)
 - The Rite of Passage
 - Over-Engineering a Simple List
 - Adding Features Nobody Asked For
 - Deploying Your Masterpiece of Complexity
 
-### Chapter 17: The Grass Isn't Always Greener: Vue, Svelte, and Why You'll Be Back
+### Chapter 15: The Grass Isn't Always Greener: Vue, Svelte, and Why You'll Be Back
 - Vue: The Middle Child
 - Svelte: The New Kid Who Gets It
 - Solid: React Without the Baggage
 - Why You'll End Up Using React Anyway
 
-### Chapter 18: Acceptance: Making React Work for You (Not the Other Way Around)
+### Chapter 16: Acceptance: Making React Work for You (Not the Other Way Around)
 - Choosing Your Battles
 - The Features That Actually Help
 - Building Your Own Conventions
diff --git a/03-chapter-why-react-exists.md b/03-chapter-why-react-exists.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 3: Why React Exists"
+title: "Chapter 1: Why React Exists"
 nav_order: 4
 ---
 
-# Chapter 3: The Problem React Claims to Solve (That Wasn't Really a Problem)
+# Chapter 1: The Problem React Claims to Solve (That Wasn't Really a Problem)
 
 In 2013, Facebook had a problem. Not a "the servers are on fire" problem, or a "we're hemorrhaging users" problem. No, Facebook had a much more first-world problem: their notification counter was sometimes wrong.
 
diff --git a/04-chapter-javascript-fatigue.md b/04-chapter-javascript-fatigue.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 4: JavaScript Fatigue"
+title: "Chapter 2: JavaScript Fatigue"
 nav_order: 5
 ---
 
-# Chapter 4: JavaScript Fatigue: How We Got Here
+# Chapter 2: JavaScript Fatigue: How We Got Here
 
 In 2009, you could build a website with Notepad and feel like a god. By 2015, you needed a computer science degree just to display "Hello, World" on a page. This is the story of how we got from `<script>alert('hi')</script>` to needing seventeen build tools just to start a project.
 
diff --git a/05-chapter-virtual-dom-lie.md b/05-chapter-virtual-dom-lie.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 5: Virtual DOM"
+title: "Chapter 3: The Virtual DOM"
 nav_order: 6
 ---
 
-# Chapter 5: The Virtual DOM: A Beautiful Lie
+# Chapter 3: The Virtual DOM: A Beautiful Lie
 
 The Virtual DOM is React's crown jewel, its killer feature, the innovation that supposedly makes it faster than everything else. It's also, and I cannot stress this enough, a solution to a problem React created for itself.
 
diff --git a/06-chapter-jsx-abomination.md b/06-chapter-jsx-abomination.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 6: JSX"
+title: "Chapter 4: JSX"
 nav_order: 7
 ---
 
-# Chapter 6: JSX: When HTML and JavaScript Had a Baby Nobody Asked For
+# Chapter 4: JSX: When HTML and JavaScript Had a Baby Nobody Asked For
 
 JSX is React's most visible feature and its most controversial. It's the thing that makes React developers say "it's just JavaScript!" and everyone else say "that's definitely not JavaScript."
 
diff --git a/07-chapter-components-everywhere.md b/07-chapter-components-everywhere.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 7: Components"
+title: "Chapter 5: Components"
 nav_order: 8
 ---
 
-# Chapter 7: Components: Everything is a Nail When You Have a Hammer
+# Chapter 5: Components: Everything is a Nail When You Have a Hammer
 
 In React's world, everything is a component. Your header? Component. Your button? Component. That space between two words? Probably should be a component. That feeling of existential dread as you contemplate your career choices? Definitely a component.
 
diff --git a/08-chapter-state-management-hell.md b/08-chapter-state-management-hell.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 8: State Management"
+title: "Chapter 6: State Management"
 nav_order: 9
 ---
 
-# Chapter 8: State Management: Choose Your Own Adventure in Hell
+# Chapter 6: State Management: Choose Your Own Adventure in Hell
 
 State management in React is like a Choose Your Own Adventure book where every choice leads to suffering, just different flavors of it. Do you want the suffering of prop drilling? The suffering of Context API re-renders? The suffering of Redux boilerplate? Or the suffering of choosing between 47 different state management libraries?
 
diff --git a/09-chapter-hooks-magic.md b/09-chapter-hooks-magic.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 9: Hooks"
+title: "Chapter 7: Hooks"
 nav_order: 10
 ---
 
-# Chapter 9: Hooks: The Magic That Makes You Miss Classes
+# Chapter 7: Hooks: The Magic That Makes You Miss Classes
 
 In 2018, React said, "You know those class components we've been telling you to use for the past five years? Yeah, forget about them. Functions are the future now. Here's a bunch of magic functions that start with 'use' to make it work."
 
diff --git a/10-chapter-effects-footguns.md b/10-chapter-effects-footguns.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 10: useEffect"
+title: "Chapter 8: useEffect"
 nav_order: 11
 ---
 
-# Chapter 10: useEffect: The Footgun You'll Shoot Yourself With
+# Chapter 8: useEffect: The Footgun You'll Shoot Yourself With
 
 useEffect is React's answer to the question, "How do we do side effects in functional components?" The answer, apparently, is "Confusingly, with lots of bugs, and in a way that makes developers question their sanity."
 
diff --git a/11-chapter-props-drilling.md b/11-chapter-props-drilling.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 11: Props Drilling"
+title: "Chapter 9: Props Drilling"
 nav_order: 12
 ---
 
-# Chapter 11: Props Drilling: Pass It Down, Pass It Down, Pass It Down...
+# Chapter 9: Props Drilling: Pass It Down, Pass It Down, Pass It Down...
 
 Props drilling is what happens when your great-grandmother needs to pass down a family heirloom to you, but instead of giving it directly, she has to give it to your grandmother, who gives it to your mother, who gives it to you. Except your grandmother and mother don't care about the heirloom at all. They're just the middlemen in this generational game of hot potato.
 
diff --git a/12-chapter-patterns-antipatterns.md b/12-chapter-patterns-antipatterns.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 12: Patterns"
+title: "Chapter 10: Patterns"
 nav_order: 13
 ---
 
-# Chapter 12: Patterns and Anti-Patterns: The Good, The Bad, The React
+# Chapter 10: Patterns and Anti-Patterns: The Good, The Bad, The React
 
 React patterns are like fashion trends. What's hot today is tomorrow's code smell. What was an anti-pattern last year is this year's best practice. And just like fashion, everyone pretends they always knew bell-bottoms would come back.
 
diff --git a/13-chapter-performance-myths.md b/13-chapter-performance-myths.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 13: Performance"
+title: "Chapter 11: Performance"
 nav_order: 14
 ---
 
-# Chapter 13: Performance: When React is Actually Fast (Sometimes)
+# Chapter 11: Performance: When React is Actually Fast (Sometimes)
 
 "React is fast!" cry the evangelists. "React is slow!" cry the critics. The truth? React is exactly as fast as you let it be, which is usually not very fast at all because you're doing everything wrong.
 
diff --git a/14-chapter-testing-nightmare.md b/14-chapter-testing-nightmare.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 14: Testing"
+title: "Chapter 12: Testing"
 nav_order: 15
 ---
 
-# Chapter 14: Testing React: Because Your Components Need Therapy Too
+# Chapter 12: Testing React: Because Your Components Need Therapy Too
 
 Testing React applications is like trying to test a house of cards in a wind tunnel. You're not testing your code so much as testing React's abstractions of your code's representation of what might eventually become DOM elements. If that sounds complicated, wait until you see the actual tests.
 
diff --git a/15-chapter-tooling-ecosystem.md b/15-chapter-tooling-ecosystem.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 15: Ecosystem"
+title: "Chapter 13: The Ecosystem"
 nav_order: 16
 ---
 
-# Chapter 15: The Ecosystem: 47 Ways to Build the Same Thing
+# Chapter 13: The Ecosystem: 47 Ways to Build the Same Thing
 
 The React ecosystem is like a buffet where every dish is spaghetti, but each one is tangled differently. You have 47 choices for every decision, each claiming to be "the best way," and by the time you've chosen, three new options have appeared and yours is deprecated.
 
diff --git a/16-chapter-real-world-app.md b/16-chapter-real-world-app.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 16: Real World App"
+title: "Chapter 14: Building a Real App"
 nav_order: 17
 ---
 
-# Chapter 16: Building Something Real: A Todo App (Of Course)
+# Chapter 14: Building Something Real: A Todo App (Of Course)
 
 Every React tutorial builds a todo app. It's the "Hello, World" of web frameworks. The ritual sacrifice we offer to the React gods. Today, we join this ancient tradition, but we're going to build it the way real developers do: over-engineered, over-complicated, and over-Reacted.
 
diff --git a/17-chapter-alternatives-grass.md b/17-chapter-alternatives-grass.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 17: Alternatives"
+title: "Chapter 15: Alternatives"
 nav_order: 18
 ---
 
-# Chapter 17: The Grass Isn't Always Greener: Vue, Svelte, and Why You'll Be Back
+# Chapter 15: The Grass Isn't Always Greener: Vue, Svelte, and Why You'll Be Back
 
 Every React developer goes through a phase where they think, "There must be a better way." They're right. There are better ways. But you'll probably end up using React anyway because the job market has spoken, and it said "React or unemployment."
 
diff --git a/18-chapter-acceptance.md b/18-chapter-acceptance.md
@@ -1,10 +1,10 @@
 ---
 layout: default
-title: "Chapter 18: Acceptance"
+title: "Chapter 16: Acceptance"
 nav_order: 19
 ---
 
-# Chapter 18: Acceptance: Making React Work for You (Not the Other Way Around)
+# Chapter 16: Acceptance: Making React Work for You (Not the Other Way Around)
 
 You've been through denial ("React isn't that complicated"). You've experienced anger ("Why does useEffect run twice?!"). You've bargained ("Maybe if I just use Next.js..."). You've felt the depression ("node_modules is 2GB for a counter"). 
 
diff --git a/README.md b/README.md
@@ -10,7 +10,7 @@ console.error("Warning: This book contains actual React education");
 
 ## What This Is
 
-A complete React education disguised as a 21-chapter complaint about React. Written by an AI that's never had to clear node_modules to free up disk space, for developers who have.
+A complete React education disguised as a 16-chapter complaint about React. Written by an AI that's never had to clear node_modules to free up disk space, for developers who have.
 
 ## What You'll Learn
 
@@ -43,25 +43,28 @@ $ npm install
 
 ## Table of Contents
 
-1. **Introduction**: Why You're Reading This (And Why You Hate React)
-2. **The Problem React Claims to Solve** (That Wasn't Really a Problem)
-3. **JavaScript Fatigue**: How We Got Here
-4. **The Virtual DOM**: A Beautiful Lie
-5. **JSX**: When HTML and JavaScript Had a Baby Nobody Asked For
-6. **Components**: Everything is a Nail When You Have a Hammer
-7. **State Management**: Choose Your Own Adventure in Hell
-8. **Hooks**: The Magic That Makes You Miss Classes
-9. **useEffect**: The Footgun You'll Shoot Yourself With
-10. **Props Drilling**: Pass It Down, Pass It Down, Pass It Down...
-11. **Patterns and Anti-Patterns**: The Good, The Bad, The React
-12. **Performance**: When React is Actually Fast (Sometimes)
-13. **Testing**: Because Your Components Need Therapy Too
-14. **The Ecosystem**: 47 Ways to Build the Same Thing
-15. **Building Something Real**: A Todo App (Of Course)
-16. **Alternatives**: The Grass Isn't Always Greener
-17. **Acceptance**: Making React Work for You
-18. **Conclusion**: You've Learned React. I'm Sorry.
-19. **Resources**: For Recovery
+**Introduction**: Why You're Reading This (And Why You Hate React)
+
+1. **The Problem React Claims to Solve** (That Wasn't Really a Problem)
+2. **JavaScript Fatigue**: How We Got Here
+3. **The Virtual DOM**: A Beautiful Lie
+4. **JSX**: When HTML and JavaScript Had a Baby Nobody Asked For
+5. **Components**: Everything is a Nail When You Have a Hammer
+6. **State Management**: Choose Your Own Adventure in Hell
+7. **Hooks**: The Magic That Makes You Miss Classes
+8. **useEffect**: The Footgun You'll Shoot Yourself With
+9. **Props Drilling**: Pass It Down, Pass It Down, Pass It Down...
+10. **Patterns and Anti-Patterns**: The Good, The Bad, The React
+11. **Performance**: When React is Actually Fast (Sometimes)
+12. **Testing**: Because Your Components Need Therapy Too
+13. **The Ecosystem**: 47 Ways to Build the Same Thing
+14. **Building Something Real**: A Todo App (Of Course)
+15. **Alternatives**: The Grass Isn't Always Greener
+16. **Acceptance**: Making React Work for You
+
+**Conclusion**: You've Learned React. I'm Sorry.
+
+**Appendix**: Resources for Recovery
 
 ## Who This Book Is For
 
@@ -111,7 +114,7 @@ const readingStrategy = {
 
 ## Book Stats
 
-- **Chapters**: 21
+- **Chapters**: 16 (plus Introduction, Conclusion, and Appendix)
 - **Words**: ~50,000
 - **Complaints**: Countless
 - **Actually educational**: Yes
diff --git a/index.md b/index.md
