[css-text] Various editorial trivialities.

Author: fantasai

css-text/Overview.bs

@@ -347,7 +347,7 @@ Languages and Typesetting</h4>
           like ideographic characters.
     </dl>
 
-    <p>The definition of “word“ used for ''capitalize'' is UA-dependent;
+    <p>For ''capitalize'', what constitutes a “word“ is UA-dependent;
       [[!UAX29]] is suggested (but not required) for determining such word
       boundaries. Authors should not expect ''capitalize'' to follow
       language-specific titlecasing conventions (such as skipping articles
@@ -578,13 +578,14 @@ Languages and Typesetting</h4>
     in the text is treated as a <dfn export>segment break</dfn>,
     which is then interpreted for rendering as specified by the 'white-space' property.
 
-  <p class="note">Note that the document parser may have
-    not only normalized any <i>segment breaks</i>,
-    but also collapsed other space characters or
-    otherwise processed white space according to markup rules. Because CSS
-    processing occurs <em>after</em> the parsing stage, it is not possible
-    to restore these characters for styling. Therefore, some of the
-    behavior specified below can be affected by these limitations and
+  <p class="note">Note that a document parser might
+    not only normalize any <i>segment breaks</i>,
+    but also collapse other space characters or
+    otherwise process white space according to markup rules.
+    Because CSS processing occurs <em>after</em> the parsing stage,
+    it is not possible to restore these characters for styling.
+    Therefore, some of the behavior specified below
+    can be affected by these limitations and
     may be user agent dependent.</p>
 
   <p class="note">Note that anonymous blocks consisting entirely of
@@ -635,7 +636,7 @@ Languages and Typesetting</h4>
         <li>Every tab is converted to a space (U+0020).</li>
         <li>Any space immediately following another collapsible space&mdash;even
           one outside the boundary of the inline containing that space,
-          provided they are both within the same inline formatting
+          provided both spaces are within the same inline formatting
           context&mdash;is collapsed to have zero advance width. (It is
           invisible, but retains its <i>soft wrap opportunity</i>, if any.)</li>
       </ol>
@@ -813,7 +814,7 @@ Languages and Typesetting</h4>
     In these systems a line can break anywhere <em>except</em> between certain character combinations.
     Additionally the level of strictness in these restrictions can vary with the typesetting style.</p>
 
-  <p>CSS does not fully define where <i>soft wrap opportunities</i> occur,
+  <p>CSS does not fully define where <i>soft wrap opportunities</i> occur;
     however some controls are provided to distinguish common variations.
 
   <div class="note">
@@ -956,7 +957,7 @@ Line Breaking Details</h3>
         lines may break between any two <i>semantically-perceived letters</i>
         (except where forbidden by the 'line-break' property).
         Hyphenation is not applied. This option is used mostly in a context where
-        the text is predominantly using CJK characters with few non-CJK excerpts
+        the text consists predominantly of CJK characters with only short non-CJK excerpts,
         and it is desired that the text be better distributed on each line.</dd>
 
       <dt><dfn>keep-all</dfn></dt>
@@ -1240,7 +1241,7 @@ Line Breaking Details</h3>
       hyphenation resource.
 
     <p>
-      Such an automatic hyphenation points within a word are ignored
+      Automatic hyphenation points within a word are ignored
       when it contains soft hyphens (&amp;shy; or U+00AD.) 
 
     <p>When shaping scripts such as Arabic are allowed to break within words

css-text/Overview.html

@@ -521,7 +521,7 @@ <h3 class="heading settled heading" data-level=2.1 id=text-transform-property><s
           like ideographic characters.
     </dl>
 
-    <p>The definition of “word“ used for <a class=css data-link-type=maybe href=#valdef-text-transform.capitalize title=capitalize>capitalize</a> is UA-dependent;
+    <p>For <a class=css data-link-type=maybe href=#valdef-text-transform.capitalize title=capitalize>capitalize</a>, what constitutes a “word“ is UA-dependent;
       <a data-biblio-type=normative data-link-type=biblio href=#biblio-uax29 title=biblio-uax29>[UAX29]</a> is suggested (but not required) for determining such word
       boundaries. Authors should not expect <a class=css data-link-type=maybe href=#valdef-text-transform.capitalize title=capitalize>capitalize</a> to follow
       language-specific titlecasing conventions (such as skipping articles
@@ -751,13 +751,14 @@ <h2 class="heading settled heading" data-level=4 id=white-space-processing><span
     in the text is treated as a <dfn data-dfn-type=dfn data-export="" id=segment-break>segment break<a class=self-link href=#segment-break></a></dfn>,
     which is then interpreted for rendering as specified by the <a class=property data-link-type=propdesc href=#propdef-white-space title=white-space>white-space</a> property.
 
-  <p class=note>Note that the document parser may have
-    not only normalized any <a data-link-type=dfn href=#segment-break title="segment breaks">segment breaks</a>,
-    but also collapsed other space characters or
-    otherwise processed white space according to markup rules. Because CSS
-    processing occurs <em>after</em> the parsing stage, it is not possible
-    to restore these characters for styling. Therefore, some of the
-    behavior specified below can be affected by these limitations and
+  <p class=note>Note that a document parser might
+    not only normalize any <a data-link-type=dfn href=#segment-break title="segment breaks">segment breaks</a>,
+    but also collapse other space characters or
+    otherwise process white space according to markup rules.
+    Because CSS processing occurs <em>after</em> the parsing stage,
+    it is not possible to restore these characters for styling.
+    Therefore, some of the behavior specified below
+    can be affected by these limitations and
     may be user agent dependent.</p>
 
   <p class=note>Note that anonymous blocks consisting entirely of
@@ -808,7 +809,7 @@ <h4 class="heading settled heading" data-level=4.1.1 id=white-space-phase-1><spa
         <li>Every tab is converted to a space (U+0020).</li>
         <li>Any space immediately following another collapsible space—even
           one outside the boundary of the inline containing that space,
-          provided they are both within the same inline formatting
+          provided both spaces are within the same inline formatting
           context—is collapsed to have zero advance width. (It is
           invisible, but retains its <a data-link-type=dfn href=#soft-wrap-opportunity title="soft wrap opportunity">soft wrap opportunity</a>, if any.)</li>
       </ol>
@@ -986,7 +987,7 @@ <h2 class="heading settled heading" data-level=5 id=line-breaking><span class=se
     In these systems a line can break anywhere <em>except</em> between certain character combinations.
     Additionally the level of strictness in these restrictions can vary with the typesetting style.</p>
 
-  <p>CSS does not fully define where <a data-link-type=dfn href=#soft-wrap-opportunity title="soft wrap opportunities">soft wrap opportunities</a> occur,
+  <p>CSS does not fully define where <a data-link-type=dfn href=#soft-wrap-opportunity title="soft wrap opportunities">soft wrap opportunities</a> occur;
     however some controls are provided to distinguish common variations.
 
   <div class=note>
@@ -1129,7 +1130,7 @@ <h3 class="heading settled heading" data-level=5.2 id=word-break-property><span
         lines may break between any two <a data-link-type=dfn href=#semantically-perceived-letter title="semantically-perceived letters">semantically-perceived letters</a>
         (except where forbidden by the <a class=property data-link-type=propdesc href=#propdef-line-break title=line-break>line-break</a> property).
         Hyphenation is not applied. This option is used mostly in a context where
-        the text is predominantly using CJK characters with few non-CJK excerpts
+        the text consists predominantly of CJK characters with only short non-CJK excerpts,
         and it is desired that the text be better distributed on each line.</dd>
 
       <dt><dfn class=css-code data-dfn-for=word-break data-dfn-type=value data-export="" id=valdef-word-break.keep-all>keep-all<a class=self-link href=#valdef-word-break.keep-all></a></dfn></dt>
@@ -1402,7 +1403,7 @@ <h3 class="heading settled heading" data-level=6.1 id=hyphens-property><span cla
       hyphenation resource.
 
     <p>
-      Such an automatic hyphenation points within a word are ignored
+      Automatic hyphenation points within a word are ignored
       when it contains soft hyphens (&amp;shy; or U+00AD.) 
 
     <p>When shaping scripts such as Arabic are allowed to break within words