From b1c10ac43222aa52d5a9a93d1a44409fecd1a21e Mon Sep 17 00:00:00 2001 From: Tim Statler Date: Thu, 14 Feb 2013 13:46:08 -0800 Subject: [PATCH] Fixed typo (being/begin), and fixed wording. Closes #2 Closes #3 --- index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index ab5304df5b..9f49943d86 100644 --- a/index.html +++ b/index.html @@ -105,7 +105,7 @@

  • A next-generation web application framework built upon these core technologies called the Toolkit.
  • -

    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 .

    +

    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 .

    Image @@ -117,7 +117,7 @@

    The overall aim of the toolkit is to manage complexity. It does this through two main principles:

    - Everything is a component—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.

    + Everything is a component—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.

    Extreme pragmatism—Developers should write the minimum 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 @@

    - \ No newline at end of file +