Fixed typo (being/begin), and fixed wording.

Closes #2
Closes #3

Author: Tim Statler

index.html

@@ -105,7 +105,7 @@ <h1>
                             <li>A next-generation web application framework built upon these core technologies called the <strong><em>Toolkit</em></strong>.</li>
                         </ul>
 
-                        <p>As browsers being to implement these features natively (Chrome 25 will support Shadow DOM, for example), this platform layer will be removed leaving the core Toolkit .</p>
+                        <p>As browsers begin to implement these features natively (Chrome 25 will support Shadow DOM, for example), this platform layer will be removed leaving the core Toolkit .</p>
 
                     <p>
                         <img src="images/architecture.png" alt="Image">
@@ -117,7 +117,7 @@ <h2>
                         The overall aim of the toolkit is to manage complexity. It does this through two main principles:
                     </p>
                     <p>
-                        <strong>Everything is a component</strong>—Encapsulation is the key to creating scalable, maintainable applications. All Toolkit resources are components, even ones that are non-visual. To construct an app, a developer creates new components, or uses ones the Toolkit provides, and assembles them together. Focusing on individual, composable building blocks allows developers to "think locally" about their application, reducing complexity. With this divide-and-conquer approach, applications can be both extremely simple and arbitrarily complicated.</p>
+                        <strong>Everything is a component</strong>—Encapsulation is the key to creating scalable, maintainable applications. All Toolkit resources are components, even ones that are non-visual. To construct an app, a developer creates new components, or uses ones the Toolkit provides, and assembles them together. Focusing on individual, composable building blocks allows developers to "think locally" about their application, reducing complexity. With this divide-and-conquer approach, applications can simultaneously be simple and arbitrarily complicated.</p>
                     </p>
                     <p>
                         <strong>Extreme pragmatism</strong>—Developers should write the <em>minimum</em> amount of code possible to create their application. Anything repetitive should be re-factored into a component, handled by the Toolkit itself, or added into the browser platform itself. The Toolkit provides simple syntax without reducing features, and avoids boilerplate wherever possible.
@@ -159,4 +159,4 @@ <h3>
         <script src="./index_files/jquery.js" type="text/javascript"></script>
         <script src="./index_files/bootstrap-scrollspy.js" type="text/javascript"></script>
     </body>
-</html>
+</html>