From 9263bff7ddb56234b7d0d7fc019d24576952088d Mon Sep 17 00:00:00 2001 From: Kelvin Oghenerhoro Omereshone Date: Wed, 27 Apr 2022 16:22:44 +0100 Subject: [PATCH] fix: typo change He's to Here's (#5410) --- handbook/company.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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.