docs(prod-deploy): further clarify how to get npm umd files

Author: wardbell

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

@@ -67,19 +67,27 @@ a#toc
   This alternative version configures _SystemJS_ to load _UMD_ versions of Angular 
   (and other third-party packages) from the web.
 
-  Pay special attention to the `paths` key:
+  Modify `systemjs.config.server.js` as necessary to stay in sync with changes
+  you make to `systemjs.config.js`.
+
+  Notice the `paths` key:
 
 +makeExample('systemjs.config.server.js', 'paths', '')(format=".")
 
 :marked
-  In your usual SystemJS config the `npm` path points at your local `node_modules/`,
-  but on the server config it points at https://unpkg.com/ - a site that hosts NPM packages.
+  In the standard SystemJS config, the `npm` path points to the `node_modules/`.
+  In this server config, it points to 
+  <a href="https://unpkg.com/" target="_blank" title="unpkg.com">https://unpkg.com</a>, 
+  a site that hosts _npm packages_,
+  and loads them from the web directly.
+  There are other service providers that do the same thing.
 
-  This way you can load your node modules from the internet directly. 
-  You can use any other provider you which, as long as it serves the needed files.
+  If you are unwilling or unable to load packages from the open web, 
+  the inventory in `systemjs.config.server.js` identifies the files and folders that 
+  you would copy to a library folder on the server. 
+  Then change the config's  `'npm'` path to point to that folder.
 
-  Modify `systemjs.config.server.js` as necessary to stay in sync with changes
-  you make to `systemjs.config.js`.
+  ### Practice with an example
 
   The following trivial router sample app shows these changes.
 
@@ -102,26 +110,25 @@ a#toc
    app/hero-list.component.ts
   `)
 
-.l-sub-section
-  :marked
-    Practice with this sample before attempting these techniques on your application.
+:marked
+  Practice with this sample before attempting these techniques on your application.
 
-    1. Follow the [setup instructions](../guide/setup.html "Angular QuickStart setup") for creating a new project
-    named <ngio-ex path="simple-deployment"></ngio-ex>.
+  1. Follow the [setup instructions](../guide/setup.html "Angular QuickStart setup") for creating a new project
+  named <ngio-ex path="simple-deployment"></ngio-ex>.
 
-    1. Add the "Simple deployment" sample files shown above.
+  1. Add the "Simple deployment" sample files shown above.
 
-    1. Run it with `npm start` as you would any project.
+  1. Run it with `npm start` as you would any project.
 
-    1. Inspect the network traffic in the browser developer tools. 
-    Notice that it loads all packages from the web.
-    You could delete the `node_modules` folder and the app would still run 
-    (although you wouldn't be able to recompile or launch `lite-server`
-    until you restored it).
+  1. Inspect the network traffic in the browser developer tools. 
+  Notice that it loads all packages from the web.
+  You could delete the `node_modules` folder and the app would still run 
+  (although you wouldn't be able to recompile or launch `lite-server`
+  until you restored it).
 
-    1. Deploy the sample to your server (minus the `node_modules` folder!).
+  1. Deploy the sample to your server (minus the `node_modules` folder!).
 
-    When you have that working, try the same process on your application.
+  When you have that working, try the same process on your application.
 
 a#optimize
 .l-main-section