addressing PR review items

Author: thelgevold

public/docs/ts/latest/cookbook/third-party-lib.jade

@@ -1,12 +1,12 @@
 include ../_util-fns
 
 :marked
-  Traditionally, third party JavaScript libraries have been published in the form of a single minified JavaScript file.
-  Consumers of the library have then included the minified JavaScript file, "as is", somewhere on the page using a `script` tag.
+  Traditionally, third party JavaScript libraries have been published in the form of a single JavaScript file.
+  Consumers of the library have then included the library, "as is", somewhere on the page using a `script` tag.
 
   Modern web development has changed this process. Instead of publishing a "one size fits all" bundle, developers want to only include the parts of the library they actually need.
 
-  This cookbook will show how to publish a third party library in a way that makes it possible to take advantage of techniques like Ahead of Time Compilation (AoT) and Tree shaking.
+  This cookbook shows how to publish a third party library in a way that makes it possible to take advantage of techniques like Ahead of Time Compilation (AoT) and Tree Shaking.
 
 <a id="toc"></a>
 :marked
@@ -31,7 +31,7 @@ include ../_util-fns
 :marked
   ## Creating a Third Party Library
 
-  This cookbook will show how to create a simple Hero-Profile library and publish it with support for AoT compilation and Tree Shaking. 
+  This cookbook shows how to create a simple Hero-Profile library and publish it with support for AoT compilation and Tree Shaking. 
 
   A version of the library intended for JiT compiled applications will also be included. 
 
@@ -111,7 +111,7 @@ include ../_util-fns
 
   In addition to supporting AoT, the library code should also be "Tree Shakable". 
 
-  Thee Shakers work best with `ES2015` JavaScript. 
+  Tree Shakers work best with `ES2015` JavaScript. 
 
   `ES2015` `import` and `export` statements make it easier to statically analyse the code to determine which modules are in use by the application.
 
@@ -127,7 +127,7 @@ include ../_util-fns
 
   AoT compiled code is the prefered format for production builds, but due to the long compilation time, it may not be practical to use AoT during development.
 
-  To create a more flexible developer experience, a JiT compatible build of the library should be published as well. The format of the JiT bundle is `umd`, which stands for Universal Module Definition. Shipping the bundle as `umd` ensures compatability with most common module loading formats.
+  To create a more flexible developer experience, a JiT compatible build of the library should be published as well. The format of the JiT bundle is `umd`, which stands for Universal Module Definition. Shipping the bundle as `umd` ensures compatibility with most common module loading formats.
 
   The `umd` bundle will ship as a single file containing the JavaScript and inlined versions of any external templates or css. 
 
@@ -154,7 +154,7 @@ include ../_util-fns
   ## Publish
 
 :marked
-  `Rollup` wil create the `umd` bundle, but but prior to bundling, all external templates or css files must be inlined. 
+  `Rollup` outputs the `umd` bundle, but prior to bundling, all external templates or css files must be inlined. 
 
   There are a few options for how to do inlining. This cookbook uses an approach borrowed from `Angular Material 2`.