+
{children}
);
diff --git a/beta/src/pages/learn/passing-data-deeply-with-context.md b/beta/src/pages/learn/passing-data-deeply-with-context.md
index 4d5eafd0..dd77575d 100644
--- a/beta/src/pages/learn/passing-data-deeply-with-context.md
+++ b/beta/src/pages/learn/passing-data-deeply-with-context.md
@@ -19,9 +19,24 @@ Usually, you will pass information from a parent component to a child component
## The problem with passing props {/*the-problem-with-passing-props*/}
-[Passing props](/learn/passing-props-to-a-component) is a great way to explicitly pipe data through your UI tree to the components that use it. But it can become verbose and inconvenient when you need to pass some prop deeply through the tree, or if many components need the same prop. The nearest common ancestor could be far removed from the components that need data, and [lifting state up](/learn/sharing-state-between-components) that high can lead to a situation sometimes called "prop drilling."
+[Passing props](/learn/passing-props-to-a-component) is a great way to explicitly pipe data through your UI tree to the components that use it.
-
+But passing props can become verbose and inconvenient when you need to pass some prop deeply through the tree, or if many components need the same prop. The nearest common ancestor could be far removed from the components that need data, and [lifting state up](/learn/sharing-state-between-components) that high can lead to a situation sometimes called "prop drilling."
+
+
+
+
+
+Lifting state up
+
+
+
+
+Prop drilling
+
+
+
+
Wouldn't it be great if there were a way to "teleport" data to the components in the tree that need it without passing props? With React's context feature, there is!
@@ -195,7 +210,21 @@ You can't do it with props alone. This is where context comes into play. You wil
Context lets a parent--even a distant one!--provide some data to the entire tree inside of it.
-
+
+
+
+
+Using context in close children
+
+
+
+
+
+Using context in distant children
+
+
+
+
### Step 1: Create the context {/*step-1-create-the-context*/}
@@ -829,8 +858,6 @@ Context is not limited to static values. If you pass a different value on the ne
In general, if some information is needed by distant components in different parts of the tree, it's a good indication that context will help you.
-
-
* Context lets a component provide some information to the entire tree below it.