line breaks

Author: filipesilva

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

@@ -2,16 +2,21 @@ include ../_util-fns
 
 :marked
   Libraries are the backbone of the Angular ecosystem.
-  They add functionality that would otherwise take a long time to implement from scratch and keep it up to date.
+  They add functionality that would otherwise take a long time to implement from scratch and keep 
+  up to date.
   Everyone benefits from a healthy library ecosystem.
 
-  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.
+  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 and in the format they need it in.
+  Instead of publishing a "one size fits all" bundle, developers want to only include the parts of 
+  the library they actually need and in the format they need it in.
 
-  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.
+  This cookbook shows how to publish a third party library in a way that makes it possible to 
+  fully benefit from techniques like Ahead of Time Compilation (AOT) and Tree Shaking.
 
 .alert.is-important
   :marked
@@ -357,7 +362,8 @@ code-example(language="json").
   Only code written in TypeScript can be AOT compiled.
 
   Before publishing the library must first be compiled using the `ngc` compiler. 
-  `ngc` extends the `tsc` compiler by adding extensions to support AOT compilation in addition to regular TypeScript compilation.   
+  `ngc` extends the `tsc` compiler by adding extensions to support AOT compilation in addition to
+  regular TypeScript compilation.   
 
   AOT compilation outputs three files that must be included in order to be compatible with AOT.
 
@@ -367,8 +373,8 @@ code-example(language="json").
 
   *Typings files*
 
-  JavaScript has no way of representing typings. In order to preserve the original typings, `ngc`
-  will generate `.d.ts` typings files.
+  JavaScript has no way of representing typings. 
+  In order to preserve the original typings, `ngc` will generate `.d.ts` typings files.
 
   *Meta Data JSON files*
 
@@ -405,11 +411,16 @@ code-example(language="json").
 :marked
   ## Appendix: Supporting JIT
 
-  AOT compiled code is the preferred format for production builds, but due to the long compilation time, it may not be practical to use AOT during development.
+  AOT compiled code is the preferred 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 compatibility 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 ES5 JavaScript and inlined versions of any external templates or css. 
+  The `umd` bundle will ship as a single file containing ES5 JavaScript and inlined versions of 
+  any external templates or css. 
 
 
 .l-main-section