post-review updates

Author: chalin

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

@@ -24,17 +24,6 @@ block template-expressions-cannot
     imported from `dart:math`. They are restricted to referencing members of
     the expression context.
 
-block array-is-list-in-Dart
-  .callout.is-helpful
-    header Dart difference: Arrays are lists
-    :marked
-      Arrays in JavaScript correspond to lists in Dart
-      (instances of the `List` class).
-      This chapter uses _array_ and _list_ interchangeably.
-      For more information, see
-      [Lists](https://www.dartlang.org/docs/dart-up-and-running/ch02.html#lists)
-      in the [Dart language tour](https://www.dartlang.org/docs/dart-up-and-running/ch02.html).
-
 block statement-context
   :marked
     Template statements can’t refer to static properties on the class, nor to

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

@@ -7,7 +7,7 @@ block includes
   - var __objectAsMap = 'object';
 
 :marked
-  Our Angular application manages what the user sees and it achieves this through the interaction of a Component class instance (the *component*) and its user-facing template.
+  Our Angular application manages what the user sees and can do, achieving this through the interaction of a Component class instance (the *component*) and its user-facing template.
 
   Many of us are familiar with the component/template duality from our experience with model-view-controller (MVC) or model-view-viewmodel (MVVM). In Angular,  the component plays the part of the controller/viewmodel, and the template represents the view.
 
@@ -33,11 +33,11 @@ block includes
   * [Input and output properties](#inputs-outputs)
   * [Template expression operators](#expression-operators)
     * [pipe](#pipe)
-    * ["safe navigation operator" (?.)](#safe-navigation-operator)
-.l-sub-section
-  p.
-    The #[+liveExampleLink2()]
-    demonstrates all of the syntax and code snippets described in this chapter.
+    * [safe navigation operator (?.)](#safe-navigation-operator)
+
+p.
+  The #[+liveExampleLink2()]
+  demonstrates all of the syntax and code snippets described in this chapter.
 
 .l-main-section
 :marked
@@ -99,9 +99,9 @@ code-example(language="html" escape="html").
   We’ll see template expressions again in the [property binding](#property-binding) section,
   appearing in quotes to the right of the `=` symbol as in `[property]="expression"`.
 
-:marked
   We write template expressions in a language that looks like #{_JavaScript}.
   Many #{_JavaScript} expressions are legal template expressions, but not all.
+
   #{_JavaScript} expressions that have or promote side effects are prohibited,
   including:
 
@@ -187,14 +187,10 @@ block template-expressions-cannot
 :marked
   Dependent values should not change during a single turn of the event loop.
   If an idempotent expression returns a string or a number, it returns the same string or number
-  when called twice in a row. If the expression returns an object (including #{_a} `#{_Array}`),
+  when called twice in a row. If the expression returns an object (including #{_an} `#{_Array}`),
   it returns the same object *reference* when called twice in a row.
 
-block array-is-list-in-Dart
-  //- N/A
-
-<a id="template-statements"></a>
-.l-main-section
+.l-main-section#template-statements
 :marked
   ## Template statements
 
@@ -217,7 +213,7 @@ block array-is-list-in-Dart
   Like template expressions, template *statements* use a language that looks like #{_JavaScript}.
   The template statement parser is different than the template expression parser and
   specifically supports both basic assignment (`=`) and chaining expressions 
-  with !{__chaining_op}.
+  (with !{__chaining_op}).
 
   However, certain #{_JavaScript} syntax is not allowed:
   * !{__new_op}
@@ -691,7 +687,7 @@ block dart-class-binding-bug
 
 .l-sub-section
   :marked
-    Note that the _style property_ name can be written in camcel case, such as `fontSize`.
+    Note that the _style property_ name can be written in camelCase, such as `fontSize`.
 
 .l-main-section
 :marked