diff --git a/contributors.yml b/contributors.yml
index 6e77890da7..e957cdaa95 100644
--- a/contributors.yml
+++ b/contributors.yml
@@ -60,6 +60,7 @@
 - david-bezero
 - david-crespo
 - decadentsavant
+- dgrijuela
 - DigitalNaut
 - dmitrytarassov
 - dokeet
diff --git a/docs/route/loader.md b/docs/route/loader.md
index f3aaf73cc3..9c5351e93e 100644
--- a/docs/route/loader.md
+++ b/docs/route/loader.md
@@ -87,7 +87,7 @@ Note that the APIs here are not React Router specific, but rather standard web o
 
 ## `loader.hydrate`
 
-If you are [Server-Side Rendering][ssr] and leveraging the `fututre.v7_partialHydration` flag for [Partial Hydration][partialhydration], then you may wish to opt-into running a route `loader` on initial hydration _even though it has hydration data_ (for example, to let a user prime a cache with the hydration data). To force a `loader` to run on hydration in a partial hydration scenario, you can set a `hydrate` property on the `loader` function:
+If you are [Server-Side Rendering][ssr] and leveraging the `future.v7_partialHydration` flag for [Partial Hydration][partialhydration], then you may wish to opt-into running a route `loader` on initial hydration _even though it has hydration data_ (for example, to let a user prime a cache with the hydration data). To force a `loader` to run on hydration in a partial hydration scenario, you can set a `hydrate` property on the `loader` function:
 
 ## Returning Responses