docs(prod-deploy): more of Ward's copy edits

Author: wardbell

public/docs/ts/latest/guide/production-deploy.jade

@@ -214,28 +214,31 @@ a#angular-configuration
 :marked
   ## Angular configuration
 
-  ## INTRODUCTION NEEDED
+  Angular configuration can make the difference between whether your app launches quickly or doesn't load at all.
 
 a#base-tag
 :marked
   ### The `base` tag
+  
+  The HTML [_<base href="..."/>_](https://angular.io/docs/ts/latest/guide/router.html#!#base-href)
+  specifies a base path for resolving relative URLs to assets such as images, scripts, and style sheets.
+  For example, given the `<base href="/myapp/">`, the browser resolves a URL such as `some/place/foo.jpg` 
+  into a server request for `myapp/some/place/foo.jpg`.
+  During navigation, the Angular router uses the _base href_ as the base path to component, template, and module files.
 
-  ## FIX THIS PROSE
-  There is an important configuration item in the Angular Router that needs to be adjusted for 
-  different environments: 
-  [the `base` tags `href` property](https://angular.io/docs/ts/latest/guide/router.html#!#base-href).
-  This property tells the router what the app root URL is so that the router can match routes.
-
-  On your development server, your app is most likely served at the root: `http://localhost:3000/`.
-  Here you use `<base href="/">`, since `/` is the root of your app.
+.l-sub-section
+  :marked
+    See also the [*APP_BASE_HREF*](../api/common/index/APP_BASE_HREF-let.html "API: APP_BASE_HREF") alternative.
+:marked
+  In development, you typically start the server in the folder that holds `index.html`. 
+  That's your root folder and you'd add `<base href="/">` near the top of `index.html` because `/` is the root of your app.
 
-  But depending on the server setup that you use, the app can be served from a subfolder like
-  `http://localhost:3000/myapp/` or `http://www.mysite.com/myapp/`, where `/myapp/` is the subfolder.
-  In this case you should use `<base href="/myapp/">`, since `/myapp/` is the root of your app and 
-  not `/`.
+  But on your shared or production server, you might serve the app from a subfolder.
+  For example, when the URL to load the app is something like `http://www.mysite.com/myapp/`, 
+  the subfolder is `myapp/` and you should add `<base href="/myapp/">` to the server version of the `index.html`.
 
-  When your `base` tag is misconfigured your browser console will show several errors in the console,
-  from missing files on wrong paths to router errors about missing routes.
+  When your `base` tag is misconfigured, the app fails to load and the browser console displays `404 - Not Found` errors
+  for the missing files. Look at where it _tried_ to find those files and adjust the base tag appropriately.
 
 a#enableProdMode
 :marked
@@ -297,6 +300,8 @@ a#server-configuration
 
   ### Why fallback to `index.html`?
 
+a#deep-link
+:marked
   A routed application should support "deep links".
   A _deep link_ is a URL that specifies a path to a component inside the app.
   For example, `http://www.mysite.com/heroes/42` is a _deep link_ to the hero detail page