diff --git a/handbook/company.md b/handbook/company.md
index 2604d49569..04a6dbda49 100644
--- a/handbook/company.md
+++ b/handbook/company.md
@@ -192,7 +192,7 @@ Between overthinking and rushing, there is a [golden mean](https://en.wikipedia.
 ### Why do we use a wireframe-first approach?
 Wireframing (or "drafting," as we often refer to it at Fleet) provides a clear overview of page layout, information architecture, user flow, and functionality. The wireframe-first approach extends beyond what users see on their screens. Wireframe-first is also excellent for drafting APIs, config settings, CLI options, and even business processes. 
 
-He's why we use a wireframe-first approach at Fleet.
+Here's why we use a wireframe-first approach at Fleet.
 
 - We create a wireframe for every change we make and favor small, iterative changes to deliver value quickly. 
 - We can think through the functionality and user experience more deeply by wireframing before committing any code. As a result, our coding decisions are clearer, and our code is cleaner and easier to maintain.