fix(*): fix PUG syntax errors

public/docs/ts/latest/cookbook/ngmodule-faq.jade

@@ -75,7 +75,7 @@ a#q-declarable
 :marked
   ## What is a _declarable_?
 
-  Declarables are the class types—components, directives, and pipes—that 
+  Declarables are the class types—components, directives, and pipes—that
   you can add to a module's `declarations` list.
   They're the _only_ classes that you can add to `declarations`.
 
@@ -113,7 +113,7 @@ a#q-why-multiple-mentions
   * `AppComponent` could be declared in this module but not bootstrapped.
   * `AppComponent` could be bootstrapped in this module but declared in a different feature module.
   * `HeroComponent` could be imported from another app module (so you can't declare it) and re-exported by this module.
-  * `HeroComponent` could be exported for inclusion in an external component's template 
+  * `HeroComponent` could be exported for inclusion in an external component's template
   as well as dynamically loaded in a pop-up dialog.
 
 .l-hr
@@ -205,7 +205,7 @@ a#q-what-to-export
   If you don't export a class, it stays _private_, visible only to other component
   declared in this module.
 
-  You _can_ export any declarable class—components, directives, and pipes—whether 
+  You _can_ export any declarable class—components, directives, and pipes—whether
   it's declared in this module or in an imported module.
 
   You _can_ re-export entire imported modules, which effectively re-exports all of their exported classes.
@@ -378,7 +378,7 @@ a#q-component-scoped-providers
   If another module elsewhere in the application also customizes `HttpBackend`
   or merely imports the `HttpModule`, it could override this module's `HttpBackend` provider,
   losing the special header. The server will reject http requests from this module.
-  
+
   To avoid this problem, import the `HttpModule` only in the `AppModule`, the application _root module_.
 
   If you must guard against this kind of "provider corruption", *don't rely on a launch-time module's `providers`.*
@@ -416,7 +416,7 @@ a#q-root-component-or-module
   ## Should I add application-wide providers to the root _AppModule_ or the root _AppComponent_?
 
   Register application-wide providers in the root `AppModule`, not in the `AppComponent`.
-  
+
   Lazy-loaded modules and their components can inject `AppModule` services;
   they can't inject `AppComponent` services.
 
@@ -734,7 +734,7 @@ table
     th(style="vertical-align: top") Feature Module
     th(style="vertical-align: top") Guidelines
   tr
-    td(style="vertical-align: top")<a id="domain-feature-module"></a>Domain
+    td(style="vertical-align: top") <a id="domain-feature-module"></a>Domain
     td
       :marked
         Domain feature modules deliver a user experience *dedicated to a particular application domain*
@@ -761,7 +761,7 @@ table
           For an example, see the [Make _Contact_ a feature module](../guide/ngmodule.html#contact-module-v1)
           section of the [NgModules](../guide/ngmodule.html) page, before routing is introduced.
   tr
-    td(style="vertical-align: top")<a id="routed-feature-module"></a>Routed
+    td(style="vertical-align: top") <a id="routed-feature-module"></a>Routed
     td
       :marked
         _Routed feature modules_ are _domain feature modules_
@@ -789,29 +789,29 @@ table
         Don't provide application-wide singleton services in a routed feature module
         or in a module that the routed module imports.
   tr
-    td(style="vertical-align: top")<a id="routing-module"></a>Routing
+    td(style="vertical-align: top") <a id="routing-module"></a>Routing
     td
       :marked
         A [routing module](../guide/router.html#routing-module) *provides routing configuration* for another module.
 
         A routing module separates routing concerns from its companion module.
-        
+
         A routing module typically does the following:
         * Defines routes.
         * Adds router configuration to the module's `imports`.
         * Re-exports `RouterModule`.
         * Adds guard and resolver service providers to the module's `providers`.
-        
+
         The name of the routing module should parallel the name of its companion module, using the suffix "Routing".
         For example, `FooModule` in `foo.module.ts` has a routing module named `FooRoutingModule`
         in `foo-routing.module.ts`
-        
-        If the companion module is the _root_ `AppModule`, 
-        the `AppRoutingModule` adds router configuration to its `imports` with `RouterModule.forRoot(routes)`. 
+
+        If the companion module is the _root_ `AppModule`,
+        the `AppRoutingModule` adds router configuration to its `imports` with `RouterModule.forRoot(routes)`.
         All other routing modules are children that import `RouterModule.forChild(routes)`.
 
-        A routing module re-exports the `RouterModule` as a convenience 
-        so that components of the companion module have access to 
+        A routing module re-exports the `RouterModule` as a convenience
+        so that components of the companion module have access to
         router directives such as `RouterLink` and `RouterOutlet`.
 
         A routing module *should not have its own `declarations`*.
@@ -827,7 +827,7 @@ table
           [Routing & Navigation](../guide/router.html) page.
 
   tr
-    td(style="vertical-align: top")<a id="service-feature-module"></a>Service
+    td(style="vertical-align: top") <a id="service-feature-module"></a>Service
     td
       :marked
         Service modules *provide utility services* such as data access and messaging.
@@ -840,7 +840,7 @@ table
         Do *not* import service modules in other feature modules.
         If you deviate from this guideline, know what you're doing and why.
   tr
-    td(style="vertical-align: top")<a id="widget-feature-module"></a>Widget
+    td(style="vertical-align: top") <a id="widget-feature-module"></a>Widget
     td
       :marked
         A widget module makes *components, directives, and pipes* available to external modules.
@@ -969,7 +969,7 @@ a#q-template-reference
 .l-main-section
 :marked
   ## How does Angular find components, directives, and pipes in a template?<br>What is a <i><b>template reference</b></i>?
-  
+
   The [Angular compiler](#q-angular-compiler) looks inside component templates
   for other components, directives, and pipes. When it finds one, that's a "template reference".
 

public/docs/ts/latest/glossary.jade

@@ -127,7 +127,7 @@ a#attribute-directives
 .l-sub-section
   block bootstrap-defn-top
     :marked
-      You launch an Angular application by "bootstrapping" it using the application root Angular module (`AppModule`). Bootstrapping identifies an application's top level "root" [component](#component), which is the first component that is loaded for the application. 
+      You launch an Angular application by "bootstrapping" it using the application root Angular module (`AppModule`). Bootstrapping identifies an application's top level "root" [component](#component), which is the first component that is loaded for the application.
       For more information, see the [Setup](!{docsLatest}/guide/setup.html) page.
   :marked
     You can bootstrap multiple apps in the same `index.html`, each app with its own top-level root.
@@ -181,9 +181,9 @@ a#component
   :marked
     Applications display data values to a user and respond to user
     actions (such as clicks, touches, and keystrokes).
-    
-    In data binding, you declare the relationship between an HTML widget and data source 
-    and let the framework handle the details. 
+
+    In data binding, you declare the relationship between an HTML widget and data source
+    and let the framework handle the details.
     Data binding is an alternative to manually pushing application data values into HTML, attaching
     event listeners, pulling changed values from the screen, and
     updating application data values.
@@ -458,12 +458,12 @@ a#jit
        - ES2015 modules, as described in this section.
 
     :marked
-      A cohesive block of code dedicated to a single purpose. 
-      
+      A cohesive block of code dedicated to a single purpose.
+
       Angular apps are modular.
 
       In general, you assemble an application from many modules, both the ones you write and the ones you acquire from others.
-      
+
       A module *exports* something of value in that code, typically one thing such as a class;
       a module that needs that class *imports* it.
 
@@ -712,7 +712,7 @@ a#structural-directives
     The process of transforming code written in one form of JavaScript
     (such as TypeScript) into another form of JavaScript  (such as [ES5](#es5)).
 
- :marked
+:marked
   ## TypeScript
 .l-sub-section
   :marked