fix(*): fix PUG syntax errors (#3401)

These errors are being missed by the Jade parser
but the more stringent Pug parser treats them as
errors.

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

@@ -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,7 +789,7 @@ 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.
@@ -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.

public/docs/ts/latest/glossary.jade

@@ -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

public/docs/ts/latest/guide/dependency-injection.jade

@@ -361,7 +361,7 @@ a#prep-for-injection
     Angular injector to inject an instance of
     `HeroService` whenever it creates a new `HeroListComponent`.
 
-#di-metadata
+a#di-metadata
 :marked
   ### Implicit injector creation
 
@@ -382,7 +382,7 @@ a#prep-for-injection
   or after navigating to a component with the [router](./router.html).
   If you let Angular do its job, you'll enjoy the benefits of automated dependency injection.
 
-a:#singleton-services
+a#singleton-services
 :marked
   ### Singleton services
 

public/docs/ts/latest/guide/pipes.jade

@@ -458,7 +458,7 @@ a(id="no-filter-pipe")
 
   The minification hazard is also compelling, if less obvious. Imagine a sorting pipe applied to a list of heroes.
   The list might be sorted by hero `name` and `planet` of origin properties in the following way:
-code-example(language="html")
+code-example(language="html").
   <!-- NOT REAL CODE! -->
   <div *ngFor="let hero of heroes | orderBy:'name,planet'"></div>
 :marked

public/docs/ts/latest/guide/typescript-configuration.jade

@@ -87,7 +87,7 @@ a(id="typings")
   Since the QuickStart is targeting `es5`, you can override the
   list of declaration files to be included:
 
-code-example(format=".")
+code-example(format=".").
   "lib": ["es2015", "dom"]
 
 :marked