docs(fix typos) (#3370)

* docs: fix typos

* docs: enhance consistency

public/docs/ts/latest/cookbook/ajs-quick-reference.jade

@@ -504,7 +504,7 @@ table(width="100%")
       :marked
         ### date
       code-example.
-        <td>{{movie.releaseDate  | date}}</td>
+        <td>{{movie.releaseDate | date}}</td>
       :marked
         Formats a date to a string based on the requested format.
     td
@@ -578,7 +578,7 @@ table(width="100%")
       :marked
         ### number
       code-example.
-        <td>{{movie.starRating  | number}}</td>
+        <td>{{movie.starRating | number}}</td>
       :marked
         Formats a number as text.
     td

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

@@ -774,14 +774,13 @@ a#non-class-dependencies
 p
   | What if the dependency value isn't a class? Sometimes the thing you want to inject is a 
   block non-class-dep-eg
-    span string, function, or object.
+    | span string, function, or object.
 p
   | Applications often define configuration objects with lots of small facts 
-  | (like the title of the application or the address of a web API endpoint)
+  | (like the title of the application or the address of a web API endpoint) 
   block config-obj-maps
-    |  but these configuration objects aren't always instances of a class.
-    | They can be object literals 
-  |  such as this one:
+    | but these configuration objects aren't always instances of a class.
+    | They can be object literals such as this one:
 
 +makeExample('dependency-injection/ts/src/app/app.config.ts','config','src/app/app-config.ts (excerpt)')(format='.')
 

public/docs/ts/latest/guide/template-syntax.jade

@@ -171,7 +171,7 @@ a#expression-context
   The context for terms in an expression is a blend of the _template variables_,
   the directive's _context_ object (if it has one), and the component's _members_.
   If you reference a name that belongs to more than one of these namespaces,
-  the template variable name takes precedence, followed by a name in the directive's' _context_,
+  the template variable name takes precedence, followed by a name in the directive's _context_,
   and, lastly, the component's member names.
 
   The previous example presents such a name collision. The component has a `hero`