Improved the processing model example section

Author: vhardy

css3-exclusions/Exclusions.src.html

@@ -187,11 +187,11 @@ <h2 id="intro">Introduction</h2>
 
     <h2 id="definitions">Definitions</h2>
 
-    <dfn>Exclusion element</dfn>
+    <dfn>Exclusion box</dfn>
 
     <p>
-        An element that defines an <span>exclusion area</span> for other elements. The 'wrap-flow'
-        property is used to make an element an exclusion element. An exclusion element contributes
+        An box that defines an <span>exclusion area</span> for other boxes. The 'wrap-flow'
+        property is used to make an element's generated box an exclusion box. An exclusion box contributes
         its <span>exclusion area</span> to its <a href="http://www.w3.org/TR/CSS2/visudet.html#containing-block-details">
         containing block's</a> <span>wrapping context</span>
     </p>
@@ -222,22 +222,22 @@ <h2 id="definitions">Definitions</h2>
     </div>
 
     <p>
-        The wrapping context of an element is a collection of 'exclusion areas'. The wrapping
-        context is used to wrap around inline flow content during layout. An element will
+        The wrapping context of an box is a collection of 'exclusion areas'. The wrapping
+        context is used to wrap around inline flow content during layout. A box will
         wrap its inline flow content in the area that corresponds to the subtraction of
         its wrapping context from its own <span>content area</span>.
     </p>
 
     <p>
-        An element inherits its 
+        A box inherits its 
         <a href="http://www.w3.org/TR/CSS2/visudet.html#containing-block-details">containing block's</a> 
         wrapping context unless it specifically 
         resets it using the 'wrap-through' property.
     </p>
 
     <dfn>Content area</dfn>
     <p>
-        The area used for layout of the inline flow content of an element. By default the
+        The area used for layout of the inline flow content of a box. By default the
         area is equivalent to the <a href="http://www.w3.org/TR/CSS2/box.html#box-dimensions">content box</a>. 
         This specification's 'shape-inside' property can define arbitrary, non-rectangular content areas.
     </p>
@@ -786,7 +786,7 @@ <h4 id="exclusions-processing-model-example">Example</h4>
 
 
         <p>The code snippet in the following example has two exclusions affecting 
-            the document's in-line content.</p>
+            the document's inline content.</p>
 
         <div class="example">
         <pre class="code idl">
@@ -810,23 +810,17 @@ <h4 id="exclusions-processing-model-example">Example</h4>
 
         <ul>
             <li>the document's DOM tree</li>
-            <li>the boxes generated by block elements in the tree</li>
-            <li>the layout tree for block boxes</p>
+            <li>the layout tree of generated block boxes</p>
         </ul>
 
         <div class="figure">
             <img src="images/processing-model-example-dom.svg" width="200" />
             <p class="caption">DOM tree</p>
         </div>
 
-        <div class="figure">
-            <img src="images/processing-model-example-block-boxes.svg" width="400" />
-            <p class="caption">Boxes of block elements</p>
-        </div>
-
         <div class="figure">
             <img src="images/processing-model-example-layout-tree.svg" width="250" />
-            <p class="caption">Layout tree for block boxes</p>
+            <p class="caption">Layout tree of generated block boxes</p>
         </div>
 
         <p>The figures illustrate how the boxes corresponding to the element sometimes
@@ -841,7 +835,7 @@ <h4 id="exclusions-processing-model-example">Example</h4>
         <h5>Step 1: resolve exclusion boxes belonging to each wrapping context</h5>
 
         <p>As a result of the computation of containing blocks for the tree, the boxes belonging 
-            to the wrapping contexts of all the elements can be computed:</p>
+            to the wrapping contexts of all the elements can be determined:</p>
 
         <ul>
             <li>The wrapping context for the html element contains the <code class="idl">e2</code> box: WC-1 (Wrapping Context 1)</li>
@@ -865,8 +859,7 @@ <h5>Step 2: resolve wrapping contexts and layout containing blocks</h5>
 
         <p>In our example, this breaks down to:</p>
         <ol>
-            <li>resolve the position and size of the exclusions belonging to the wrapping context. We call this 
-                step 'resolve the wrapping context'. Let's call the initial containing block's wrapping context RWC-1 (Resolved Wrapping Context 1).</li>
+            <li>resolve the position and size of the exclusions belonging to WC-1: RWC-1 (Resolved Wrapping Context 1).</li>
             <li>layout the initial containing block (i.e., layout its content):
                 <ol>
                     <li>resolve the html element's wrapping context: RWC-1</li>
@@ -887,35 +880,35 @@ <h5>Step 2: resolve wrapping contexts and layout containing blocks</h5>
                 </li>
         </ol>
 
-        <h6>Computing RWC-1</h6>
+        <h6>Resolving RWC-1</h6>
 
-        <p>The top most wrapping context, in the layout tree, contains the <code class="idl">e2</code>
-            exclusion. Its position and size needs to be computed. In general, computing an 
+        <p>The top-most wrapping context in the layout tree contains the <code class="idl">e2</code>
+            exclusion. Its position and size needs to be resolved. In general, computing an 
             exclusion's position and size may or may not require laying out other content.
-            In our example, no content needs to be laid out to compute the <code class="idl">e2</code>
-            exclusion's position because it is absolutely positioned and its size can be computed
-            without layout either. At this point, RWC-1 is resolved and can be used during 
-            layout of inline content.</p>
+            In our example, no content needs to be laid out to resolve the <code class="idl">e2</code>
+            exclusion's position because it is absolutely positioned and its size can be resolved
+            without layout either. At this point, RWC-1 is resolved and can be used when
+            laying inline content out.</p>
 
-        <h6>Computing RWC-2</h6>
+        <h6>Resolving RWC-2</h6>
 
         <p>The process is similar: the position of the 
-            <code class="idl">e1</code>exclusion needs to be computed. Again, computing the exclusion's 
+            <code class="idl">e1</code>exclusion needs to be resolved. Again, resolving the exclusion's 
             position and size may require processing the containing block (d1 here). 
             It is the case here because the size and position of
             <code class="idl">e1</code> depend on resolving the percentage lengths. The percentages are relative 
             to the size of 
-            <code class="idl">d1</code>'s box. As a result, in order to compute
+            <code class="idl">d1</code>'s box. As a result, in order to resolve
             a size for <code class="idl">d1</code>'s box, a first layout of <code class="idl">d1</code>
-            is done with an empty wrapping context. The layout yields a 
+            is done without any wrapping context (i.e., no exclusions applied). The layout yields a 
             position and size for <code class="idl">e1</code>'s box. 
         </p>
         <p>At this point, RWC-2 is resolved because the position and size of both 
-            e1 and e2 and computed.</p>
+            e1 and e2 are resolved.</p>
 
         <p class="note">The important aspect of the above processing example is that once an element's wrapping context
-            is resolved (by computing its exclusions' position and size), the position and size of the
-            exclusions are not recomputed if the element's size changes between the layout that may be done with 
+            is resolved (by resolving its exclusions' position and size), the position and size of the
+            exclusions are not re-processed if the element's size changes between the layout that may be done with 
             an empty wrapping context (as for RWC-2) and the layout done with the resolved wrapping context. 
             This is what breaks the possible circular dependency between the resolution of wrapping contexts
             and the layout of containing blocks.</p>