diff --git a/contributors.yml b/contributors.yml
index a64cee96c2b..cfdc4dd98e3 100644
--- a/contributors.yml
+++ b/contributors.yml
@@ -351,3 +351,4 @@
 - zachdtaylor
 - zainfathoni
 - zhe
+- DNLHC
diff --git a/docs/guides/styling.md b/docs/guides/styling.md
index d0f621a5d64..818af851441 100644
--- a/docs/guides/styling.md
+++ b/docs/guides/styling.md
@@ -84,7 +84,7 @@ Remix makes writing plain CSS a viable option even for apps with a lot of UI. In
 
 - how and when to load CSS, so it was usually all loaded on every page
 - if the class names and selectors you were using were accidentally styling other UI in the app
-- if some rules were even used anymore as the CSS source code grew over time
+- if some rules weren't even used anymore as the CSS source code grew over time
 
 Remix alleviates these issues with route-based stylesheets. Nested routes can each add their own stylesheets to the page and Remix will automatically prefetch, load, and unload them with the route. When the scope of concern is limited to just the active routes, the risks of these problems are reduced significantly. The only chances for conflicts are with the parent routes' styles (and even then, you will likely see the conflict since the parent route is also rendering).