From 72e7547ef0fa69c5360cc4bd64c03a7ea8287ae4 Mon Sep 17 00:00:00 2001
From: Daniel Bird <danielsbird@gmail.com>
Date: Sat, 13 Jan 2018 13:50:24 -0500
Subject: [PATCH] Embed examples using gatsby-remark-embed-snippet

---
 content/docs/rendering-elements.md            | 25 ++-----------------
 .../update-rendered-element.js                |  1 +
 2 files changed, 3 insertions(+), 23 deletions(-)

diff --git a/content/docs/rendering-elements.md b/content/docs/rendering-elements.md
index d0c1caf04..7ed7aed67 100644
--- a/content/docs/rendering-elements.md
+++ b/content/docs/rendering-elements.md
@@ -35,13 +35,7 @@ Applications built with just React usually have a single root DOM node. If you a
 
 To render a React element into a root DOM node, pass both to `ReactDOM.render()`:
 
-```js
-const element = <h1>Hello, world</h1>;
-ReactDOM.render(
-  element,
-  document.getElementById('root')
-);
-```
+`embed:rendering-elements/render-an-element.js`
 
 [](codepen://rendering-elements/render-an-element)
 
@@ -55,22 +49,7 @@ With our knowledge so far, the only way to update the UI is to create a new elem
 
 Consider this ticking clock example:
 
-```js{8-11}
-function tick() {
-  const element = (
-    <div>
-      <h1>Hello, world!</h1>
-      <h2>It is {new Date().toLocaleTimeString()}.</h2>
-    </div>
-  );
-  ReactDOM.render(
-    element,
-    document.getElementById('root')
-  );
-}
-
-setInterval(tick, 1000);
-```
+`embed:rendering-elements/update-rendered-element.js`
 
 [](codepen://rendering-elements/update-rendered-element)
 
diff --git a/examples/rendering-elements/update-rendered-element.js b/examples/rendering-elements/update-rendered-element.js
index 3ed32d25b..f16ddcc11 100644
--- a/examples/rendering-elements/update-rendered-element.js
+++ b/examples/rendering-elements/update-rendered-element.js
@@ -8,6 +8,7 @@ function tick() {
       </h2>
     </div>
   );
+  // highlight-range{1-4}
   ReactDOM.render(
     element,
     document.getElementById('root')