Update blog/make-the-change-easy/index.md

blog/make-the-change-easy/index.md

@@ -20,4 +20,4 @@ Me and this mantra are advocating for the second option here. And that’s not t
 By refactoring BEFORE you add a new feature your codebase is getting cleaner and cleaner as you go! As opposed to creating more tech debt with each PR, you can actually clean up your codebase as you go! This will pay for itself in the long run, AND has the benefit of making the work more “predictable”. In a clean, well organized code base there are less chances of running into something unexpected that drastically shifts the timelines for a project.
 In a messy codebase it’s common to find issues buried, or things that take longer to untangle than expected.
 
-Not only does cleaning up the codebase allow you to be more productive, it also helps me more predictable! And predictability is sometimes even more important than raw speed. Something being finished a day or two earlier is often not a deal breaker, but missing an agreed upon deadline because something unexpected came up can cause issues for the organization.
+Not only does cleaning up the codebase allow you to be more productive, it also helps be more predictable! And predictability is sometimes even more important than raw speed. Something being finished a day or two earlier is often not a deal breaker, but missing an agreed upon deadline because something unexpected came up can cause issues for the organization.