Merge pull request #4 from opencomponents/copy-review

A few copy updates

Author: nickbalestra

components/landing-page/package.json

@@ -1,7 +1,7 @@
 {
   "name": "landing-page",
   "description": "",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "oc": {
     "files": {
       "data": "server.js",

components/landing-page/template.hbs

@@ -19,8 +19,8 @@
       <h1>Building web applications together, faster.</h1>
     </header>
     <p>While microservice architectures allowed teams to scale delivery of independently deployable services, most frontend layers are still run as monolithic applications. Similar to server-side applications, frontend layers often grow into large monoliths that are difficult to maintain and evolve.</p>
-    <p>The idea behind <a href="https://www.thoughtworks.com/radar/techniques/micro-frontends" target="_blank">micro frontends</a> is to enable multiple teams to seamless work together by fostering end-to-end ownership of independently developed, tested and deployed features.</p>
-    <p>Think about UI as the composition of features which are maintained by independent teams. These teams could be cross functional allowing them to develop such features end-to-end, from a database to user interface and independently deploy them.</p>
+    <p>The idea behind <a href="https://www.thoughtworks.com/radar/techniques/micro-frontends" target="_blank">micro frontends</a> is to enable multiple teams to work seamlessy together by fostering end-to-end ownership of independently developed, tested and deployed features.</p>
+    <p>Think about UI as the composition of features which are maintained by independent teams. These teams could be cross-functional allowing them to develop such features end-to-end, from a database to user interface and independently deploy them.</p>
   </article>
 
   <div class="hr">
@@ -31,7 +31,7 @@
     <header>
       <h1>The OpenComponents framework</h1>
     </header>
-    <p>OpenComponents is an opensource, "batteries included" micro frontends framework. Born at OpenTable in 2014, it matured over the years into a battle tested solution currently used to deliver micro frontends at scale by fast growing companies around the world.</p>
+    <p>OpenComponents is an open-source, "batteries included" micro frontends framework. Born at OpenTable in 2014, it matured over the years into a battle tested solution currently used to deliver micro frontends at scale by fast growing companies around the world.</p>
     <div class="block">
       <img src="{{staticPath}}img/components.png" />
       <div>
@@ -50,21 +50,21 @@
       <img src="{{staticPath}}img/registry.png" />
       <div>
         <h2>Registry</h2>
-        <p>The registry provides a rest API to consume, retrieve, and publish components to a library. When components depend on static resources (such as images, css files, etc.) these are stored, during packaging and publishing, in a publicly-exposed part of the library that serves as CDN. <a href="https://github.com/opentable/oc/wiki/Registry" target="_blank">Learn more</a></p>
+        <p>The registry provides a rest API to consume, retrieve, and publish components to a library. When components depend on static resources (such as images, css files, etc.) these are stored, during packaging and publishing, in a publicly-exposed part of the library that serves as a CDN. <a href="https://github.com/opentable/oc/wiki/Registry" target="_blank">Learn more</a></p>
       </div>
     </div>
     <div class="block img-right">
       <img src="{{staticPath}}img/cli.png" />
       <div>
         <h2>CLI</h2>
-        <p>The CLI tool allows developers to create, develop, and test components locally. It also allows publishing components to your registry. <a href="https://github.com/opentable/oc/wiki/Cli" target="_blank">Learn more</a></p>
+        <p>The CLI tool allows developers to create, develop, and test components locally. It also allows publishing of components to your registry. <a href="https://github.com/opentable/oc/wiki/Cli" target="_blank">Learn more</a></p>
       </div>
     </div>
      <div class="block">
       <img src="{{staticPath}}img/clients.png" />
       <div>
         <h2>Client libraries</h2>
-        <p>Multiple libraries are available, allowing to consume components on different environment and platforms. Depending on the library, clients are normally able to consume both unrendered components and rendered components. <a href="https://github.com/opencomponents/oc-client-node#oc-client" target="_blank">Learn more</a></p>
+        <p>Multiple libraries are available, allowing clients to consume components on different environments and platforms. Depending on the library, clients are normally able to consume both unrendered components and rendered components. <a href="https://github.com/opencomponents/oc-client-node#oc-client" target="_blank">Learn more</a></p>
       </div>
     </div>
   </article>