docs(guide/overview): improve grammar and readability

Closes #4639

1 files changed, 8 insertions, 8 deletions

diff --git a/docs/content/guide/overview.ngdoc b/docs/content/guide/overview.ngdoc
index 9dc891bd..91e6e22c 100644
--- a/docs/content/guide/overview.ngdoc
+++ b/docs/content/guide/overview.ngdoc
@@ -55,9 +55,9 @@ 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 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.
+is a good fit for Angular. Angular was built with the CRUD application in mind. Luckily CRUD
+applications represent the majority of web applications. To understand what Angular is
+good at, though, it helps to understand when an app is not a good fit for Angular.
 
 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.
@@ -70,7 +70,7 @@ Below is a typical CRUD application which contains a form. The form values are v
 are used to compute the total, which is formatted to a particular locale. These are some common
 concepts which the application developer may face:
 
-  * attaching data-model to the UI.
+  * attaching a data-model to the UI.
   * writing, reading and validating user input.
   * computing new values based on the model.
   * formatting output in a user specific locale.
@@ -135,7 +135,7 @@ These input widgets look normal enough, but consider these points:
   * Note that the HTML widget {@link api/ng.directive:input input}
     has special powers. The input invalidates itself by turning red when you enter invalid data or
     leave the input fields blank. These new widget behaviors make it easier to implement field
-    validation common in CRUD applications.
+    validation, which is common in CRUD applications.
 
 And finally, the mysterious `{{ double curly braces }}`:
 
@@ -149,7 +149,7 @@ In the example above, the expression in double-curly braces directs Angular to "
 got from the input widgets to the display, multiply them together, and format the resulting number
 into output that looks like money."
 
-Notice that we achieved this application behavior not by calling Angular methods, nor by
+Notice that we achieved this application behavior neither by calling Angular methods, nor by
 implementing application specific behavior as a framework. We achieved the behavior because the
 browser behaved more in line with what is needed for a dynamic web application rather than what is
 needed for a static document. Angular has lowered the impedance mismatch to the point where no
@@ -183,11 +183,11 @@ Angular frees you from the following pains:
     what your application does.
   * **Manipulating HTML DOM programmatically:** Manipulating HTML DOM is a cornerstone of AJAX
     applications, but it's cumbersome and error-prone. By declaratively describing how the UI
-    should change as your application state changes, you are freed from low level DOM manipulation
+    should change as your application state changes, you are freed from low-level DOM manipulation
     tasks. Most applications written with Angular never have to programmatically manipulate the
     DOM, although you can if you want to.
   * **Marshaling data to and from the UI:** CRUD operations make up the majority of AJAX
-    applications. The flow of marshaling data from the server to an internal object to an HTML
+    applications' tasks. The flow of marshaling data from the server to an internal object to an HTML
     form, allowing users to modify the form, validating the form, displaying validation errors,
     returning to an internal model, and then back to the server, creates a lot of boilerplate
     code. Angular eliminates almost all of this boilerplate, leaving code that describes the