generated version

Author: alexmog1

css3-flexbox/Overview.html

@@ -29,11 +29,11 @@
 
    <h1 id=head-box-flexible>CSS Flexible Box Layout Module</h1>
 
-   <h2 class="no-num no-toc" id=w3c-working>Editor's Draft, 9 March 2012</h2>
+   <h2 class="no-num no-toc" id=w3c-working>Editor's Draft, 12 March 2012</h2>
 
    <dl>
     <dt>This version:
-     <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-flexbox-20120309/">http://www.w3.org/TR/2012/ED-css3-flexbox-20120309/</a>-->
+     <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-flexbox-20120312/">http://www.w3.org/TR/2012/ED-css3-flexbox-20120312/</a>-->
 
 
     <dd><a
@@ -577,7 +577,7 @@ <h2 id=flex-items><span class=secno>4. </span> Flexbox Items</h2>
 
    <p>Notice that block element "not-an-item6.3" is not a separate flexbox
     item, because it is contained inside an inline element which is being
-    wrapped into an anonymous flex item. Similarly, the block element
+    wrapped into an anonymous flexbox item. Similarly, the block element
     "not-an-item1.5" is not a flexbox item, because it's absolutely
     positioned and thus out of flow.</p>
   </div>
@@ -2077,7 +2077,7 @@ <h2 id=layout-algorithm><span class=secno>9. </span> Flexbox Layout
      <li>If the free space is negative, but step 1 chose positive
       flexibility, do nothing
 
-     <li>Add a portion of free space to each flexible item, proportinal to
+     <li>Add a portion of free space to each flexible item, proportional to
       item's flexibility
     </ol>
 
@@ -2172,10 +2172,10 @@ <h2 id=pagination><span class=secno>10. </span> Page breaks in flexbox</h2>
      <li>Otherwise, it may be broken, according to breaking rules and
       algorithms applicable to its display type.
 
-     <li>Forced breaks inside flex item content are handled normally, but in
-      row-direction flexbox they don&#39;t affect layout of sibling flex
-      items (e.g. a forced break inside an item doesn&#39;t prevent its next
-      sibling from appearing on the same page)
+     <li>Forced breaks inside flexbox item content are handled normally, but
+      in row-direction flexbox they don&#39;t affect layout of sibling
+      flexbox items (e.g. a forced break inside an item doesn&#39;t prevent
+      its next sibling from appearing on the same page)
     </ol>
 
    <li> <b>Column-direction flexbox: single-line</b>
@@ -2191,7 +2191,7 @@ <h2 id=pagination><span class=secno>10. </span> Page breaks in flexbox</h2>
        flexbox.</p>
 
      <li>Set of items that will fit on current page is determined by adding
-      main-axis sizes of items until total size exceeds availalble space or a
+      main-axis sizes of items until total size exceeds available space or a
       forced break is encountered.
 
      <li>If border box of an item doesn’t fit in available space, a break
@@ -2207,7 +2207,7 @@ <h2 id=pagination><span class=secno>10. </span> Page breaks in flexbox</h2>
     </ol>
 
     <p class=note>It is the intent of this spec that column-direction
-     single-line flexbox paginates very simlarly to block flow. As a test of
+     single-line flexbox paginates very similarly to block flow. As a test of
      the intent, a flexbox with "flex-pack:start" and no flexible items
      should paginate identically to a block with non-floating children with
      same content, same used size and same used margins. This rule is
@@ -2326,7 +2326,7 @@ <h2 id=pagination><span class=secno>10. </span> Page breaks in flexbox</h2>
      <li>Line packing is done on each page, with content on the page
     </ol>
 
-    <p class=issue>TODO: combine breaking algorigthms for multiline in both
+    <p class=issue>TODO: combine breaking algorithms for multiline in both
      directions. If breaks inside items are not allowed the algorithm is
      almost same.</p>
   </ul>
@@ -2436,7 +2436,7 @@ <h3 id=testing><span class=secno>11.5. </span> Non-experimental
    implementations</h3>
 
   <p>Once a specification reaches the Candidate Recommendation stage,
-   non-experimental implementations are possible, and implementors should
+   non-experimental implementations are possible, and implementers should
    release an unprefixed implementation of any CR-level feature they can
    demonstrate to be correctly implemented according to spec.
 
@@ -2506,9 +2506,12 @@ <h3 id=cr-exit-criteria><span class=secno>11.6. </span> CR exit criteria</h3>
 
   <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
 
-  <p>[This section will contain further acknowledgments.]
-
-  <p>Thanks for feedback from James Elmore and Shinichiro Hamaji.
+  <p>Thanks for feedback and contributions to Andrew Fedoniouk, Arron
+   Eicholz, James Elmore, Ben Horst, Boris Zbarsky, Brad Kemper, Brian
+   Heuston, Christian Stockwell, Christoph Päper, Daniel Holbert, Erik
+   Anderson, Eugene Veselov, Fantasai, John Jansen, Markus Mielke, Ning
+   Rogers, Ojan Vafai, Peter Salas, Phil Cupp, Robert O'Callahan, Rossen
+   Atanassov, Shinichiro Hamaji, Tony Chang.
 
   <h2 class=no-num id=references>References</h2>