docs(graphql-cookbook): Fix @kapunahelewong review

Author: Urigo

public/docs/ts/latest/cookbook/graphql.jade

@@ -6,10 +6,10 @@ include ../_util-fns
 
 .l-sub-section
   :marked
-    GraphQL is a replacement or enhancement for REST and can be used in conjunction with it.
+    The GraphQL interface is a replacement or enhancement for REST and can be used in conjunction with it.
 
 :marked
-  GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
+  It provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
 
 
 <a id="toc"></a>
@@ -43,18 +43,18 @@ include ../_util-fns
 :marked
   ## What is GraphQL?
 
-  GraphQL is an API query language, helping your Angular app:
+  GraphQL is an API query language, that helps your Angular app do the following:
 
   - Fetch exactly the information it needs from the server.
   - Add type safety to your API.
   - Merge multiple dependencies into one single response from the server.
   - Handle server data dependency in a component structure.
 
-  It’s also important to understand that:
+  It’s also important to understand these key points:
 
   - **GraphQL is not a data source**. The GraphQL runtime works on top of any data source&mdash;SQL,
-  NoSql, REST, Queues, .NET servers, Java servers or any other technology or data source.
-  - GraphQL solves the need of sending multiple requests for multiple resources to the server and
+  NoSql, REST, Queues, .NET servers, Java servers, or any other technology or data source.
+  - GraphQL solves the need of sending multiple requests to the server for different resources and
   then running complex joins on the client&mdash;without the need to create a custom endpoint like REST does.
   - The GraphQL specification also includes protocols for real-time push updates from the server to the client.
 
@@ -67,8 +67,8 @@ include ../_util-fns
 
 .l-sub-section
   :marked
-    For a summary of this section, see [Faster modern apps with Angular and GraphQL](https://www.youtube.com/watch?v=Xx39bv-5ojA&t=1s) 
-    presented by [Jeff Cross](https://twitter.com/jeffbcross) and [Uri Goldshtein](https://twitter.com/UriGoldshtein).
+    For a summary of this section, see the following [video](https://www.youtube.com/watch?v=Xx39bv-5ojA&t=1s) 
+    by [Jeff Cross](https://twitter.com/jeffbcross) and [Uri Goldshtein](https://twitter.com/UriGoldshtein).
 
 iframe(type='text/html' width='560' height='315'
     src='https://www.youtube.com/embed/Xx39bv-5ojA'
@@ -86,13 +86,15 @@ iframe(type='text/html' width='560' height='315'
   3. Fetching data at the parent component and passing it down the component tree.
 
   While these solutions are valid, they have their limitations.
+  
+  The following three sections cover each of these in turn.
 
   #### Using the HTTP service in the Component
 
   There are two potential issues with this approach:
 
   1. Multiple redundant requests; when you render multiple components,
-  for example, through `ngFor` with many components, each sends its own
+  such as an `ngFor` with many components, each sends its own
   HTTP call.
   2. Inconsistent data; if two components fetch the same data but in different requests,
   the data might change and not be consistent across the app.
@@ -118,7 +120,7 @@ a#http-heroes
 :marked
   #### Fetching data at the parent component and passing it down the component tree
 
-  Consider an example of the second possibility:
+  Consider an example of the third possibility:
 
 +makeExample('toh-4/ts/src/app/hero.ts','','Declare the API type')
 +makeExample('toh-4/ts/src/app/hero-detail.component.ts','declaring-conponent-input','Declare the input')
@@ -127,7 +129,7 @@ a#http-heroes
 :marked
   This works until you change the API of the component, which means you need to change
   its parent components _all the way to the top_.
-  Again, this creates a dependency. This time it is with the child component
+  Again, this creates a dependency. This time the dependency is with the child component
   all the way up to the fetching component
   and _all the components in between_.
 
@@ -145,12 +147,12 @@ a#http-heroes
   Now, a single component contains all of its own data dependency changes.
 
 :marked
-  The `watchQuery` function tells the Apollo Client what data 
-  this component needs. The Apollo Client then returns the 
+  The `watchQuery` function tells the Apollo Client, the GraphQL client that lets you use GraphQL in your Angular app,
+  what data this component needs. The Apollo Client then returns the 
   necessary data to the component as an Observable.
   For example, adding an `age` field to the app is 
   simple because you only change the component (you cover 
-  this syntax [later](#querying) in the cookbook) And then modify the template accordingly:
+  this syntax [later](#querying) in the cookbook) and then modify the template accordingly:
 
 +makeExample('heroes-graphql/ts/src/app/hero-detail.component.1.ts','graphql-query-new-field','Adding an `age` field to the component')
 +makeExample('heroes-graphql/ts/src/app/hero-detail.component.1.html','template-new-field','Adding an `age` field to the template')
@@ -169,7 +171,7 @@ a#http-heroes
   calls `getHeroes` to fetch all heroes and their information.
 
 :marked
-  That might work for simple cases but the problem here is that `getHeroes` might fetch
+  That might work for simple cases but but as your app grows `getHeroes` might fetch
   more information than the app really needs for each hero.
   This approach also creates a dependency between the server endpoint and the UI
   component&mdash;if you change or limit the amount of information you send on the
@@ -196,7 +198,7 @@ a#http-heroes
     and migrate gradually from them.
 
 :marked
-  ### Typed API, tooling and auto documentation
+  ### Typed API, tooling and, auto documentation
 
   Just as TypeScript provides tooling to increase productivity and best practices,
   GraphQL provides a similar solution for working with APIs.