Incorporate Owen's proofreading changes

Author: bradfrost

_layouts/toc.html

@@ -30,7 +30,7 @@ <h3>Designing Systems</h3>
             <a href="/chapter-2">
                 <span>2.</span>
                 <h3> Atomic Design Methodology</h3>
-                <p>Atoms, Molecules, Organisms, Templates, and Pages</p>
+                <p>Atoms, molecules, organisms, templates, and pages</p>
             </a>
         </li>
         <li>

_site/author/index.html

@@ -5,7 +5,7 @@
   <meta http-equiv="X-UA-Compatible" content="IE=edge">
   <meta name="viewport" content="width=device-width initial-scale=1">
 
-  <title>About the Author | Atomic Design by Brad Frost</title>
+  <title>Testimonials | Atomic Design by Brad Frost</title>
   <meta name="description" content="Atomic design is a methodology for crafting effective design systems
 ">
 
@@ -15,22 +15,22 @@
   <link href="https://fonts.googleapis.com/css?family=Merriweather|Oswald" rel="stylesheet">
 
 <!-- Schema.org markup for Google+ -->
-<meta itemprop="name" content="About the Author | Atomic Design by Brad Frost">
+<meta itemprop="name" content="Testimonials | Atomic Design by Brad Frost">
 <meta itemprop="image" content="http://atomicdesign.bradfrost.com/images/book-cover-thumb.png">
 <meta itemprop="description" content="Atomic design is a methodology for crafting effective design systems
 ">
 
 <!-- Twitter Card data -->
 <meta name="twitter:card" content="summary_large_image">
-<meta name="twitter:title" content="About the Author | Atomic Design by Brad Frost">
+<meta name="twitter:title" content="Testimonials | Atomic Design by Brad Frost">
 <meta name="twitter:description" content="Atomic design is a methodology for crafting effective design systems
 ">
 <meta name="twitter:creator" content="@brad_frost">
 <!-- Twitter summary card with large image must be at least 280x150px -->
 <meta name="twitter:image:src" content="http://atomicdesign.bradfrost.com/images/book-cover-thumb.png/images/book-cover-thumb.png">
 
 <!-- Open Graph data -->
-<meta property="og:title" content="About the Author | Atomic Design by Brad Frost" />
+<meta property="og:title" content="Testimonials | Atomic Design by Brad Frost" />
 <meta property="og:url" content="http://atomicdesign.bradfrost.com/author/" />
 <meta property="og:image" content="http://atomicdesign.bradfrost.com/images/book-cover-thumb.png/images/book-cover-thumb.png" />
 <meta property="og:description" content="Atomic design is a methodology for crafting effective design systems
@@ -42,15 +42,31 @@
         <div class="page-header">
     <div class="page-header-inner">
 
-        <h1 class="page-title">About the Author</h1>
-        <p class="page-subtitle">About Brad Frost</p>
+        <h1 class="page-title">Testimonials</h1>
+        <p class="page-subtitle">What others are saying about Atomic Design</p>
     </div>
 </div>
 
 <div class="text">
-    <p><img src="/images/brad_frost_ffly.png" alt="Brad Frost" /></p>
+    <blockquote>
+To boldly go beyond “pages.” That’s the universe of modern design, and there’s no better guide to exploring it than Brad Frost. In Atomic Design, he replaces our outdated, closed workflows with exciting new collaborative ones, and teaches us to design not just pages but systems. Recommended for all web and interaction designers.
+<cite>Jeffrey Zeldman, author of <em>Designing With Web Standards</em></cite>
+</blockquote>
 
-<p><a href="http://bradfrost.com">Brad Frost</a> is a web designer, speaker, consultant, and musician located in beautiful Pittsburgh, PA. He’s passionate about creating web experiences that look and function beautifully on a never-ending stream of connected devices, and loves helping others do the same. He’s helped create several tools and resources for web designers, including <a href="http://patternlab.io/">Pattern Lab</a> (with Dave Olsen and Brian Muenzenmeyer), <a href="http://styleguides.io/">Styleguides.io</a> (with Anna Debenham), <a href="https://bradfrost.github.io/this-is-responsive/">This Is Responsive</a>, <a href="http://wtfmobileweb.com/">WTF Mobile Web</a> (with Jen Simmons), and Mobile Web Best Practices.</p>
+<blockquote>
+"This book is itself an excellent example of Atomic Design. Brad takes on a big intimidating topic—design systems the web—and breaks it down into its constituent parts, making it easy to understand and implement."
+<cite>Jeremy Keith, author <em>HTML5 for Web Designers</em></cite>
+</blockquote>
+
+<blockquote>
+Brad describes not only the atomic design methodology, but also the process involved in making it successful. With the knowledge and experience of working on big and small websites, he'll equip you with the skills needed to build a comprehensive design system that works for your organisation, that is easy to update, and that lives on for months and years to come.
+<cite>Anna Debenham, author of <em>Front-end Style Guides</em></cite>
+</blockquote>
+
+<blockquote>
+Brad is suggesting that we'd be better web designers if we thought of what we're building as a system. A hierarchical system that fits together to form larger parts. Because, spoiler alert, it is and we would be.
+<cite>Chris Coyier, CSS Tricks</cite>
+</blockquote>
 
 
 

_site/chapter-1/index.html

@@ -172,7 +172,7 @@ <h3 id="modularizing-content-im-on-team-chunk">Modularizing content: I’m on Te
 <h3 id="classy-code">Classy code</h3>
 <p>Modularity has long been a staple principle in the world of computer science, as we discussed earlier. While this principle existed long before the web was invented, it has taken some time for modularity to become engrained in the minds and hearts of web developers.</p>
 
-<p>Despite being around since 1995, JavaScript, the programming language of the web, first had to endure some growing pains to mature into the capable, respected language it is today. Now that JavaScript has grown up, developers can now apply those tried-and-true computer science principles to their web development workflows. As a result, we’re seeing folks develop sophisticated <a href="http://addyosmani.com/resources/essentialjsdesignpatterns/book/">JavaScript patterns</a> and architectures.</p>
+<p>Despite being around since 1995, JavaScript, the programming language of the web, first had to endure some growing pains to mature into the capable, respected language it is today. Now that JavaScript has grown up, developers can apply those tried-and-true computer science principles to their web development workflows. As a result, we’re seeing folks develop sophisticated <a href="http://addyosmani.com/resources/essentialjsdesignpatterns/book/">JavaScript patterns</a> and architectures.</p>
 
 <p>Applying modular programming principles to JavaScript is a bit of a no-brainer, since JavaScript is itself a programming language. But object-oriented thinking is weaving its way into other aspects of the web as well, including CSS, the styling language of the web. Methodologies like <a href="http://oocss.org/">OOCSS</a>, <a href="https://smacss.com/">SMACSS</a>, and <a href="http://csswizardry.com/2013/01/mindbemding-getting-your-head-round-bem-syntax">BEM</a> have cropped up to help web designers create and maintain modular CSS architectures.</p>
 
@@ -206,7 +206,7 @@ <h3 id="systematic-ui-design">Systematic UI design</h3>
 
 <p>What is an interface made of? What are our Lego bricks? What are our Subway sandwich pieces that we combine into millions of delicious combinations? It’s these questions that we’ve been asking ourselves more and more now that we’re sending our interfaces to more and more places.</p>
 
-<p>A few years ago Ethan Marcotte introduced us to the idea of <a href="http://alistapart.com/article/responsive-web-design">responsive web design</a> and its three core tenets: fluid grids, flexible media, and CSS media queries. These three ingredients provided a much needed foundation for designers to create flexible layouts that smartly adapt to any screen size. Perhaps more importantly, responsive design helped get designers excited about creating thoughtful, adaptable, multi-device web experiences.</p>
+<p>A few years ago Ethan Marcotte introduced us to the idea of <a href="http://alistapart.com/article/responsive-web-design">responsive web design</a> and its three core tenets: fluid grids, flexible media, and CSS media queries. These three ingredients provided a much-needed foundation for designers to create flexible layouts that smartly adapt to any screen size. Perhaps more importantly, responsive design helped get designers excited about creating thoughtful, adaptable, multi-device web experiences.</p>
 
 <p>As designers quickly discovered, creating multi-device web experiences involves a lot more than creating squishy pages. Each individual piece of an interface contains its own unique challenges and opportunities in order for it to look and function beautifully across many screen sizes and environments.</p>
 
@@ -316,9 +316,9 @@ <h3 id="voice-and-tone">Voice and tone</h3>
 <p>Voice and tone guidelines get into the weeds by articulating how the company’s voice and tone should shift across a variety of scenarios. <a href="http://voiceandtone.com/">MailChimp’s brilliant voice and tone guidelines</a> define how the brand’s tone changes across content types, so that when a user’s credit card is declined, writers know to shift away from their generally cheeky and playful tone of voice and adopt a more serious tone instead.</p>
 
 <figure>
-    <img src="../images/content/styleguide-voiceandtone.png" alt="Mailchimp’s Voice and Tone guidelines" />
+    <img src="../images/content/styleguide-voiceandtone.png" alt="MailChimp’s Voice and Tone guidelines" />
 	<figcaption>
-	    Mailchimp’s Voice and Tone guidelines
+	    MailChimp’s Voice and Tone guidelines
 	</figcaption>
 </figure>
 
@@ -366,7 +366,7 @@ <h2 id="style-guide-benefits">Style guide benefits</h2>
 
 <h3 id="consistently-awesome">Consistently awesome</h3>
 
-<p><strong>Web style guides promote consistency and cohesion</strong> across a user interface. This consistency benefits both the people who create these interfaces but also their users.</p>
+<p><strong>Web style guides promote consistency and cohesion</strong> across a user interface. This consistency benefits both the people who create these interfaces and also their users.</p>
 
 <p>I recently visited my health insurance provider’s website to pay my bill. In the course of five clicks, I was hit with four distinct interface designs, some of which looked like they were last touched in 1999. This inconsistent experience put the burden on me, the user, to figure out what went where and how to interpret disparate interface elements. By the time I got to the payment form, I felt like I couldn’t trust the company to successfully and securely process my payment.</p>
 
@@ -382,9 +382,9 @@ <h3 id="a-shared-vocabulary">A shared vocabulary</h3>
 <p>As the number of people working on a project increases, it becomes all too easy for communication breakdowns to occur. It’s not uncommon for different disciplines to have different names for the same module, and for individuals to go rogue and invent their own naming conventions. For true collaboration to occur, it’s essential for teams to speak a common language. Style guides are there to help establish that shared vocabulary.</p>
 
 <figure>
-    <img src="../images/content/starbucks-blocks-3up.png" alt="Giving names to patterns like 'Blocks 3-Up' in Starbucks' style guide helps team members speak the same language." />
+    <img src="../images/content/starbucks-blocks-3up.png" alt="Giving names to patterns like 'Blocks Three-Up' in Starbucks' style guide helps team members speak the same language." />
 	<figcaption>
-	    Giving names to patterns like 'Blocks 3-Up' in Starbucks' style guide helps team members speak the same language.
+	    Giving names to patterns like 'Blocks Three-Up' in Starbucks' style guide helps team members speak the same language.
 	</figcaption>
 </figure>
 
@@ -404,7 +404,7 @@ <h3 id="education">Education</h3>
 <h3 id="an-empathetic-workflow">An empathetic workflow</h3>
 <p>Education isn’t just important for clients and stakeholders. A good style guide helps inform designers and developers of the tools they have in their toolbox, and provides rules and best practices for how to use them properly.</p>
 
-<p>By making a style guide a cornerstone of your workflow (which we’ll detail in chapter 4), <strong>designers and developers are forced to think about how their decisions affect the broader design system</strong>. It becomes harder to go rogue and becomes easier to think of the greater good. And this is exactly where you want team members to be.</p>
+<p>By making a style guide a cornerstone of your workflow (which we’ll detail in chapter 4), <strong>designers and developers are forced to think about how their decisions affect the broader design system</strong>. It becomes harder to go rogue and easier to think of the greater good. And this is exactly where you want team members to be.</p>
 
 <p>A style guide provides a home for each discipline to contribute their respective considerations and concerns for patterns. By collecting all these considerations under one roof, the style guide becomes a hub for everyone involved in the project, which helps each discipline better understand the design system from many perspectives.</p>