From fc6837c47c73e9e780aea8a3ff58e12ba16a6989 Mon Sep 17 00:00:00 2001
From: Thomas Hintz <t@thintz.com>
Date: Sun, 26 Jul 2020 12:01:52 -0700
Subject: [PATCH] Trying out different props.

---
 high-performance-react.org | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/high-performance-react.org b/high-performance-react.org
index a92f862..6ca04b7 100644
--- a/high-performance-react.org
+++ b/high-performance-react.org
@@ -569,7 +569,7 @@ and then loop through the current props, setting them accordingly. Of
 course we filter out the ~children~ prop since we use that elsewhere
 and it isn't intended to be set directly.
 
-#+NAME Setting DOM Props
+#+NAME: Setting DOM Props
 #+BEGIN_SRC javascript
 function setDOMProps(element, domElement, prevElement) {
     if (prevElement) {
@@ -587,10 +587,10 @@ function setDOMProps(element, domElement, prevElement) {
 }
 #+END_SRC
 
-#+begin_info
+#+begin_note
 React is more intelligent about only updating or removing props that
 need to be.
-#+end_info
+#+end_note
 
 #+begin_warning
 This algorithm for setting props does not correctly handle events