diff options
| -rw-r--r-- | docs/content/guide/overview.ngdoc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/content/guide/overview.ngdoc b/docs/content/guide/overview.ngdoc index 8e555bf2..6f51bf7d 100644 --- a/docs/content/guide/overview.ngdoc +++ b/docs/content/guide/overview.ngdoc @@ -56,12 +56,12 @@ starting point you can easily change. Angular comes with the following out-of-th Angular simplifies application development by presenting a higher level of abstraction to the developer. Like any abstraction, it comes at a cost of flexibility. In other words not every app is a good fit for Angular. Angular was built for the CRUD application in mind. Luckily CRUD -applications represent at least 90% of the web applications. But to understand what Angular is +applications represent the majority of web applications. But to understand what Angular is good at one also has to understand when an app is not a good fit for Angular. -Games, and GUI editors are examples of very intensive and tricky DOM manipulation. These kinds of -apps are different from CRUD apps, and as a result are not a good fit for Angular. In these cases -using something closer to bare metal such as `jQuery` may be a better fit. +Games and GUI editors are examples of applications with intensive and tricky DOM manipulation. +These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular. +In these cases it may be better to use a library with a lower level of abstraction, such as `jQuery`. # An Introductory Angular Example @@ -175,7 +175,7 @@ expressing business logic. -Angular frees you from the following pain: +Angular frees you from the following pains: * **Registering callbacks:** Registering callbacks clutters your code, making it hard to see the forest for the trees. Removing common boilerplate code such as callbacks is a good thing. It |