diff --git a/content/doc/flex/using/flx_mxmlSyntax_sy.html b/content/doc/flex/using/flx_mxmlSyntax_sy.html
index 3d4d93dee..32e7054b2 100644
--- a/content/doc/flex/using/flx_mxmlSyntax_sy.html
+++ b/content/doc/flex/using/flx_mxmlSyntax_sy.html
@@ -114,8 +114,8 @@ <h3 class="topictitle3">Naming MXML files</h3>
                </li>
 
                <li>
-                  <p>Filenames must not be the same as ActionScript class names,
-component <samp class="codeph">id</samp> values, or the word <em>application</em>.
+                  <p>Filenames must not be the same as ActionScript class names or
+component <samp class="codeph">id</samp> values in the application, or use the word <em>application</em>.
 Do not use filenames that match the names of MXML tags that are
 in the <samp class="codeph">fx:</samp>, <samp class="codeph">s:</samp>, or <samp class="codeph">mx:</samp> namespace.</p>
 
@@ -141,7 +141,7 @@ <h3 class="topictitle3">Using tags that represent ActionScript
             <p>An MXML tag that corresponds to an ActionScript
 class uses the same naming conventions as the ActionScript class.
 Class names begin with a capital letter, and capital letters separate
-the words in class names. For example, when a tag corresponds to
+the words in class names. When a tag corresponds to
 an ActionScript class, its properties correspond to the properties
 and events of that class.</p>
 
@@ -233,8 +233,7 @@ <h2 class="topictitle2">Setting component properties</h2>
 
          </ul>
 
-         <p>It's best to assign scalar values using tag attributes, and that
-you assign complex types, such as ActionScript objects, by using
+         <p>It's best to assign scalar values using tag attributes, and to assign complex types, such as ActionScript objects, by using
 child tags.</p>
 
       </div>
@@ -260,7 +259,7 @@ <h3 class="topictitle3">Setting properties using constants</h3>
          
          <div>
             <p>The valid values of many component properties are defined
-by static constants, where these static constants are defined in
+by static constants which are defined in
 an ActionScript class. In MXML, you can either use the static constant
 to set the property value, or use the value of the static constant,
 as the following example shows:</p>
@@ -394,7 +393,7 @@ <h3 class="topictitle3">Escaping characters using the backslash
     xmlns:mx="library://ns.adobe.com/flex/mx" 
     xmlns:s="library://ns.adobe.com/flex/spark"&gt; 
  
-    &lt;s:Label text="\{\}"/&gt; 
+    &lt;s:Label text="\{ \}"/&gt; 
  
 &lt;/s:Application&gt;</pre>
 
@@ -488,7 +487,7 @@ <h3 class="topictitle3">Including a newline character in
 the <a href="https://flex.apache.org/asdoc/spark/components/TextArea.html" target="_blank">TextArea</a> control
 to a value that includes a newline character.</p>
 
-            <p>Notice that this example includes the <samp class="codeph">[Bindable]</samp> metadata
+            <p>Note that this example includes the <samp class="codeph">[Bindable]</samp> metadata
 tag before the property definition. This metadata tag specifies
 that the <samp class="codeph">myText</samp> property can be used as the source
 of a data binding expression. Data binding automatically copies
@@ -825,7 +824,7 @@ <h3 class="topictitle3">Populating a Vector</h3>
             <p>The first example defines a Vector with a base type of String.
 The second example defines a Vector of Vectors of type String. Notice
 that you use the HTML escape characters <samp class="codeph">&amp;lt;</samp> and <samp class="codeph">&amp;gt;</samp> ,
-instead of &lt; and &gt;, in the nested Vector. This syntax is necessary
+instead of &lt; and &gt;, in the nested Vector. This is necessary
 to conform to XML syntax rules. </p>
 
          </div>
@@ -1204,4 +1203,4 @@ <h3 class="topictitle3">MXML tag rules</h3>
 
 
 </body>
-</html>
\ No newline at end of file
+</html>