Suggestions from January review on §3.4

spec/index.html

@@ -91,7 +91,7 @@
   <p>RDF 1.2 introduces the ability to use an <a>RDF triple</a>
     as a <a>triple term</a>, in the <a>object</a> position of another <a>triple</a>.
     RDF 1.2 also introduces <a>directional language-tagged strings</a>,
-    which contain a <a>base direction</a> element that allows the
+    which contain a <a>base direction</a> component that allows the
     initial text direction to be specified for presentation by a user agent.</p>
 
   <p>RDF 1.2 Concepts introduces key concepts and terminology for RDF 1.2, discusses
@@ -790,8 +790,8 @@ <h3>Literals</h3>
 
     <p>Literals are used for values such as strings, numbers, and dates.</p>
 
-    <p>A <dfn data-local-lt="RDF literal">literal</dfn> in an <a>RDF graph</a> consists of
-      two, three, or four elements, as follow:</p>
+    <p>A <dfn data-local-lt="RDF literal">literal</dfn> consists of
+      two, three, or four components, as below:</p>
 
     <ol>
       <li>A <dfn>lexical form</dfn>, being an <a data-lt="string">RDF string</a>.
@@ -805,7 +805,7 @@ <h3>Literals</h3>
         language tag MUST be well-formed according to
         <a data-cite="bcp47#section-2.2.9">section 2.2.9</a>
         of [[!BCP47]],
-        and MUST be treated accordingly, that is, in a case insensitive manner.
+        and MUST be treated accordingly, that is, in a case-insensitive manner.
         Two [[!BCP47]]-complying strings that differ only by case represent the same [=language tag=].</li>
       <li>If and only if the <a>datatype IRI</a> is
         <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#dirLangString</code>,
@@ -815,10 +815,10 @@ <h3>Literals</h3>
         </ul></li>
     </ol>
 
-    <p>A literal is a <dfn>language-tagged string</dfn> if the third element
-      is present and the fourth element is not present.
+    <p>A literal is a <dfn>language-tagged string</dfn> if the [=language tag=]
+      is present and the [=base direction=] is <em>not</em> present.
       A literal is a <dfn id="dfn-dir-lang-string">directional language-tagged string</dfn>
-      if both the third element and fourth elements are present.
+      if both the [=language tag=] and the [=base direction=] are present.
     </p>
 
     <p><dfn data-local-lt="term-equal">Literal term equality</dfn>:
@@ -901,7 +901,7 @@ <h2>Literal value</h2>
               <a>lexical form</a>.</li>
             <li>Otherwise, the literal is <dfn data-lt-no-plural>ill-typed</dfn> and no literal value can be
                associated with the literal. Such a case produces a semantic
-               inconsistency, but it is not <em>syntactically</em> ill-formed.
+               [=inconsistency=], but it is not <em>syntactically</em> ill-formed.
                Implementations SHOULD accept [=ill-typed=] literals and produce RDF
                graphs from them. Implementations MAY produce warnings when
                encountering [=ill-typed=] literals.</li>
@@ -2290,7 +2290,7 @@ <h2>Changes between RDF 1.1 and RDF 1.2</h2>
       and extended the definition of
       <a>RDF triple</a> to permit triple terms as objects.
       Also defines <a>reifier</a> and <a>reifying triple</a>.</li>
-    <li>Added the <a>base direction</a> element as part of 
+    <li>Added the <a>base direction</a> component as part of
       a <a>literal</a>,
       and a description of its use in <a href="#section-text-direction" class="sectionRef"></a>.</li>
     <li>Improved the use of IRI terminology,