Fix munificent#49.

Author: munificent

book/component.markdown

@@ -690,7 +690,7 @@ communication paths if you need them.
     got them laid out in memory in the most efficient way for your
     CPU to read them.
 
-    This is a rare hat trick in architecture: your code is both more
+    This is a rare win-win in architecture: your code is both more
     maintainable *and* faster.
 
 *   The open source <a href="http://www.delta3d.org/">Delta3D</a>

book/singleton.markdown

@@ -72,11 +72,10 @@ instance. All together, the classic implementation looks like this:
 The static `instance_` member holds an instance of the class, and the
 private constructor ensures that it is the *only* one. The public
 static `instance()` method grants access to the instance from anywhere
-in the codebase. It is also responsible for creating the instance
-using lazy initialization: it instantiates the Singleton the first
-time someone asks for it.
+in the codebase. It is also responsible for instantiating the
+singleton instance lazily the first time someone asks for it.
 
-A more modern update on this is like so:
+A modern take looks like this:
 
 ^code local-static
 

html/component.html

@@ -1010,7 +1010,7 @@ <h2><a href="#see-also" name="see-also">See Also</a></h2>
     components of the same type and put them in an array, now you&#x2019;ve
     got them laid out in memory in the most efficient way for your
     CPU to read them.</p>
-<p>This is a rare hat trick in architecture: your code is both more
+<p>This is a rare win-win in architecture: your code is both more
 maintainable <em>and</em> faster.</p>
 </li>
 <li>

html/singleton.html

@@ -136,10 +136,9 @@ <h3><a href="#providing-a-global-point-of-access" name="providing-a-global-point
 <p>The static <code>instance_</code> member holds an instance of the class, and the
 private constructor ensures that it is the <em>only</em> one. The public
 static <code>instance()</code> method grants access to the instance from anywhere
-in the codebase. It is also responsible for creating the instance
-using lazy initialization: it instantiates the Singleton the first
-time someone asks for it.</p>
-<p>A more modern update on this is like so:</p>
+in the codebase. It is also responsible for instantiating the
+singleton instance lazily the first time someone asks for it.</p>
+<p>A modern take looks like this:</p>
 <div class="codehilite"><pre><span class="k">class</span> <span class="nc">FileSystem</span>
 <span class="p">{</span>
 <span class="nl">public:</span>