post-review updates

Author: chalin

public/docs/ts/_cache/tutorial/toh-pt6.jade

@@ -97,10 +97,12 @@ block backend
     The  `InMemoryWebApiModule` replaces the default `Http` client backend —
     the supporting service that talks to the remote server —
     with an  _in-memory web API alternative service_.
+
   +makeExcerpt(_appModuleTsVsMainTs, 'in-mem-web-api', '')
+
   :marked
     The `forRoot` configuration method takes an `InMemoryDataService` class
-    that will prime the in-memory database as follows:
+    that primes the in-memory database as follows:
 
 +makeExample('app/in-memory-data.service.ts', 'init')(format='.')
 
@@ -126,7 +128,7 @@ block dont-be-distracted-by-backend-subst
 
 :marked
   We returned a !{_Promise} resolved with mock heroes.
-  It may have seemed like an overkill at the time, but we were anticipating the
+  It may have seemed like overkill at the time, but we were anticipating the
   day when we fetched heroes with an HTTP client and we knew that would have to be an asynchronous operation.
 
   That day has arrived! Let's convert `getHeroes()` to use HTTP.
@@ -140,7 +142,7 @@ block dont-be-distracted-by-backend-subst
 
 - var _h3id = `http-${_promise}`
 :marked
-  Refresh the browser and the hero data should be successfully loaded from the
+  Refresh the browser, and the hero data should be successfully loaded from the
   mock server.
 
   <h3 id="!{_h3id}">HTTP !{_Promise}</h3>
@@ -217,23 +219,21 @@ block get-heroes-details
   Although we made significant *internal* changes to `getHeroes()`, the public signature did not change.
   We still return a !{_Promise}. We won't have to update any of the components that call `getHeroes()`.
 
-  ### Add, edit, delete heroes
+  Our stakeholders are incredibly pleased with the added flexibility from the API integration, but it doesn't stop there. Next, we want the ability to create new heroes and delete heroes.
 
-  Our stakeholders are incredibly pleased with the added flexibility from the API integration, but it doesn't stop there. Next we want to add the capability to add, edit and delete heroes.
+  But first, let's see what happens now when we try to update a hero's details.
 
-  We'll start with the edit feature since we have most of the capabilities already.
-
-.l-main-section#edit
+.l-main-section
 :marked
-  ## Persist name changes to the server
+  ## Update hero details
 
   The hero detail view already allows us to edit a hero's name. Go ahead, try
   it now. As we type, the hero name is updated in the view heading, but
-  notice what happens when we hit the `Back` button: the edits are lost!
+  notice what happens when we hit the `Back` button: the changes are lost!
 
 .l-sub-section
   :marked
-    Changes weren't lost before, what's happening?
+    Updates weren't lost before, what's happening?
     When the app used a list of mock heroes, changes were made directly to the
     hero objects in the single, app-wide shared list. Now that we are fetching data
     from a server, if we want changes to persist, we'll need to write them back to
@@ -336,7 +336,7 @@ block get-heroes-details
 :marked
   ### Hero service `delete` method
 
-  The delete HTTP method will be used to delete heroes and its invocation is like to `put` except for the method name:
+  The hero service's `delete` method uses the _delete_ HTTP method to remove the hero from the server:
 
 +makeExcerpt('app/hero.service.ts', 'delete')
 
@@ -509,7 +509,8 @@ block observable-transformers
 - var _declarations = _docsFor == 'dart' ? 'directives' : 'declarations'
 - var declFile = _docsFor == 'dart' ? 'app/dashboard.component.ts' : 'app/app.module.ts'
 :marked
-  And finally, we import the `HeroSearchComponent` from `'./hero-search.component.ts'`
+  And finally, we import `HeroSearchComponent` from 
+  <span ngio-ex>hero-search.component.ts</span>
   and add it to the `!{_declarations}` !{_array}:
 
 +makeExcerpt(declFile, 'search')

public/docs/ts/latest/tutorial/toh-pt6.jade

@@ -97,10 +97,12 @@ block backend
     The  `InMemoryWebApiModule` replaces the default `Http` client backend —
     the supporting service that talks to the remote server —
     with an  _in-memory web API alternative service_.
+
   +makeExcerpt(_appModuleTsVsMainTs, 'in-mem-web-api', '')
+
   :marked
     The `forRoot` configuration method takes an `InMemoryDataService` class
-    that will prime the in-memory database as follows:
+    that primes the in-memory database as follows:
 
 +makeExample('app/in-memory-data.service.ts', 'init')(format='.')
 
@@ -126,7 +128,7 @@ block dont-be-distracted-by-backend-subst
 
 :marked
   We returned a !{_Promise} resolved with mock heroes.
-  It may have seemed like an overkill at the time, but we were anticipating the
+  It may have seemed like overkill at the time, but we were anticipating the
   day when we fetched heroes with an HTTP client and we knew that would have to be an asynchronous operation.
 
   That day has arrived! Let's convert `getHeroes()` to use HTTP.
@@ -140,7 +142,7 @@ block dont-be-distracted-by-backend-subst
 
 - var _h3id = `http-${_promise}`
 :marked
-  Refresh the browser and the hero data should be successfully loaded from the
+  Refresh the browser, and the hero data should be successfully loaded from the
   mock server.
 
   <h3 id="!{_h3id}">HTTP !{_Promise}</h3>
@@ -217,23 +219,21 @@ block get-heroes-details
   Although we made significant *internal* changes to `getHeroes()`, the public signature did not change.
   We still return a !{_Promise}. We won't have to update any of the components that call `getHeroes()`.
 
-  ### Add, edit, delete heroes
+  Our stakeholders are incredibly pleased with the added flexibility from the API integration, but it doesn't stop there. Next, we want the ability to create new heroes and delete heroes.
 
-  Our stakeholders are incredibly pleased with the added flexibility from the API integration, but it doesn't stop there. Next we want to add the capability to add, edit and delete heroes.
+  But first, let's see what happens now when we try to update a hero's details.
 
-  We'll start with the edit feature since we have most of the capabilities already.
-
-.l-main-section#edit
+.l-main-section
 :marked
-  ## Persist name changes to the server
+  ## Update hero details
 
   The hero detail view already allows us to edit a hero's name. Go ahead, try
   it now. As we type, the hero name is updated in the view heading, but
-  notice what happens when we hit the `Back` button: the edits are lost!
+  notice what happens when we hit the `Back` button: the changes are lost!
 
 .l-sub-section
   :marked
-    Changes weren't lost before, what's happening?
+    Updates weren't lost before, what's happening?
     When the app used a list of mock heroes, changes were made directly to the
     hero objects in the single, app-wide shared list. Now that we are fetching data
     from a server, if we want changes to persist, we'll need to write them back to
@@ -336,7 +336,7 @@ block get-heroes-details
 :marked
   ### Hero service `delete` method
 
-  The delete HTTP method will be used to delete heroes and its invocation is like to `put` except for the method name:
+  The hero service's `delete` method uses the _delete_ HTTP method to remove the hero from the server:
 
 +makeExcerpt('app/hero.service.ts', 'delete')
 
@@ -509,7 +509,8 @@ block observable-transformers
 - var _declarations = _docsFor == 'dart' ? 'directives' : 'declarations'
 - var declFile = _docsFor == 'dart' ? 'app/dashboard.component.ts' : 'app/app.module.ts'
 :marked
-  And finally, we import the `HeroSearchComponent` from `'./hero-search.component.ts'`
+  And finally, we import `HeroSearchComponent` from 
+  <span ngio-ex>hero-search.component.ts</span>
   and add it to the `!{_declarations}` !{_array}:
 
 +makeExcerpt(declFile, 'search')