     [:article
      [:p
       "One of the big challenges in using React.js and Om is understanding how the code you write "
-      "impacts performance and rendering time. In most cases, you shouldn’t care – React’s diffing model and "
+      "impacts performance and rendering time. In most cases, you shouldn't care - React's diffing model and "
       [:a {:href "https://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs/"}
-       "Om’s handling of immutable data structures"]
+       "Om's handling of immutable data structures"]
       " make hand-tuning mostly superfluous. There will always be places where the defaults are too slow and "
-      "micro-optimizations are required for the sake of performance. In those cases, Om’s global concerns allow "
+      "micro-optimizations are required for the sake of performance. In those cases, Om's global concerns allow "
       "us to create tools to see the bottlenecks and understand the impact of our optimzations."]
-     [:p "I’ll show you how CircleCI leverages Om’s new “descriptor” overrides to understand performance in its "
+     [:p "I'll show you how CircleCI leverages Om's new “descriptor” overrides to understand performance in its "
       [:a {:href "https://github.com/circleci/frontend"} "open-source frontend"] ". "
       [:a {:href "https://circleci.com"} "CircleCI"] " is a hosted Continuous Delivery platform used by teams that "
       "want state-of-the-art CI and deployment."]]

     [:article
      [:p "The console-style instrumentation panel drops down when we hit Ctrl+j and we can see it update in real-time "
       "as components are rendered."]
      [:p "Now it’s easy to identify the bottlenecks and measure the effects of our optimizations on render times."]])})

    [:article
     [:p "This is a nice step forward. Like paint rectangles, it gives us a visual indication of possible "
      "performance bottlenecks. But we can do so much better. Paint rectangles can show us the regions that "
      "are being re-rendered, but that's not how we think of components when we write and use them. Like any "
      "function, we want to refer to them by their name. The paint rectangles also don't tell us how long it "
      "takes to render each region, so we don't know which component to prioritize."]]

    [:article
     [:h3 "Instrumenting components"]
