Tagging sample sections.

foundations-high-performance-react.org

@@ -19,7 +19,7 @@
 #+options: toc:nil tags:nil
 
 
-* Preface :frontmatter:
+* Preface :frontmatter: :sample:
   :PROPERTIES:
   :EXPORT_FILE_NAME: manuscript/preface.markua
   :END:
@@ -52,10 +52,9 @@ you better understand how it works, and even more critically, it will
 allow you to play with it and test how the algorithms work with your
 own examples.
 
-Even if you don't write out the code yourself and,instead, read through this
-book more like a novel, I believe the
-fundamentals will still stick with you and provide value in your
-React programs-to-come.
+Even if you don't write out the code yourself and, instead, read
+through this book more like a novel, I believe the fundamentals will
+still stick with you and provide value in your React programs-to-come.
 
 I'm very excited to take you on this journey with me and, so, now it's time
 to learn what lies at the very foundation of React.
@@ -346,7 +345,7 @@ of ~elements~ (surprise).
 That's it. Now we have everything we need to actually begin the
 process of rendering our tree to the DOM!
 
-* Render: Putting Elements on the Screen
+* Render: Putting Elements on the Screen :sample:
   :PROPERTIES:
   :EXPORT_FILE_NAME: manuscript/render.markua
   :END:
@@ -737,12 +736,12 @@ decide how and when to render components are the same. And, when not
 running in Concurrent Mode, the effect is still the same, as React
 still does the render phase in one block. So, using a simplified
 interpretation that doesn't include all the complexities of breaking
-up the process in to chunks enables us to see more clearly how the
+up the process into chunks enables us to see more clearly how the
 process works as a whole. At this point, bottlenecks are much more
 likely to occur from the underlying algorithms and not from the Fibers
 specific details.
 
-* Putting it all together
+* Putting it all together :sample:
   :PROPERTIES:
   :EXPORT_FILE_NAME: manuscript/putting-it-all-together.markua
   :END: