From 70f2c487c6559ccbadfbbf94267ce72f2a402bc3 Mon Sep 17 00:00:00 2001
From: Facundo Perez Montalvo <66702127+facuperezm@users.noreply.github.com>
Date: Thu, 7 Nov 2024 02:40:58 -0300
Subject: [PATCH] small typo (#130)

---
 exercises/01.elements/03.problem.context/README.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exercises/01.elements/03.problem.context/README.mdx b/exercises/01.elements/03.problem.context/README.mdx
index 5541a0cb..6fc64999 100644
--- a/exercises/01.elements/03.problem.context/README.mdx
+++ b/exercises/01.elements/03.problem.context/README.mdx
@@ -6,7 +6,7 @@
 incremented, we trigger a rerender of the `Footer` component! Have we lost the
 ability to take advantage of React's element optimization? No!
 
-Instead of accepting the `color` via props, we can place it in a context provier
+Instead of accepting the `color` via props, we can place it in a context provider
 that the `Footer` can consume. And with that, the `footer` no longer accepts any
 dynamic props so we can move it outside the `App` component again, which means
 the only way it can be rerendered is if the context changes (which is exactly