[css-contain][css-display] Move "becoming a FC" back to css-contain

As resolved in w3c#1457

Author: frivoal

css-contain/Overview.bs

@@ -319,6 +319,20 @@ Paint Containment</h3>
 	3. Because they are guaranteed to be stacking contexts,
 		scrolling elements can be painted into a single GPU layer.
 
+<h2 id="becoming-formatting-context">Becoming a formatting context</h2>
+
+In some some types of containement,
+a box may need to <dfn export lt='become a formatting context|becomes a formatting context|becoming a formatting context'>become a <a>formatting context</a></dfn>.
+If the box already establishes a <a>formatting context</a> of any kind other than an <a>inline formatting context</a>,
+this condition is satisfied.
+Otherwise, it is made to establish a <a>BFC</a> by changing its <a>inner display type</a> to ''flow-root''.
+This change happens at <a>used value</a> time,
+and does not affect the <a>computed value</a> of the 'display' property.
+
+Issue: What should we do about boxes that establish <a>ruby formatting contexts</a>?
+See some discussion here: https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-319996309
+
+
 Privacy and Security Considerations {#privsec}
 ==============================================
 
@@ -390,6 +404,14 @@ Answers are provided below.
 
 This appendix is <em>informative</em>.
 
+<h3 id="2017-08-08-changes">Changes from the
+<a href="https://www.w3.org/TR/2017/CR-css-contain-1-20170808/"
+   >Candidate Recommendation of 8 August 2017</a></h3>
+
+<ul>
+	<li>Move the definition of "Becoming a formatting context" back to this specification
+</ul>
+
 <h3 id="2017-04-19-changes">Changes from the
 <a href="https://www.w3.org/TR/2017/WD-css-contain-1-20170419/"
    >Working Draft of 19 April 2017</a></h3>

css-display/Overview.bs

@@ -803,17 +803,6 @@ Run-In Layout</h2>
 
 	Note: This run-in model is slightly different from the one proposed in earlier revisions of [[!CSS2]].
 
-<h2 id="becoming-formatting-context">Becoming a formatting context</h2>
-
-In some circumstances (See [[CSS-CONTAIN-1]] or [[CSS3-MULTICOL]] for examples),
-a box may need to <dfn export lt='become a formatting context|becomes a formatting context|becoming a formatting context'>become a <a>formatting context</a></dfn>.
-If the box already establishes a <a>formatting context</a> of any kind,
-this condition is satisfied.
-Otherwise, it is made to establish a <a>BFC</a> by changing its <a>inner display type</a> to ''flow-root''.
-This change happens at <a>used value</a> time,
-and does not affect the <a>computed value</a> of the 'display' property.
-
-
 <h2 id='glossary' class=no-num>
 Appendix A: Glossary</h2>
 
@@ -1133,6 +1122,10 @@ Acknowledgments</h2>
 <h2 class=no-num id="changes">
 Changes</h2>
 
+	Changes since the <a href="https://www.w3.org/TR/2017/WD-css-display-3-20170720/">20 July 2017 Working Draft</a> include:
+
+	* Moved back the section about becomming a formatting context to css-contain
+
 	Changes since the <a href="https://www.w3.org/TR/2017/WD-css-display-3-20170126/">26 January 2017 Working Draft</a> include:
 
 	* Remove <css>inline-list-item</css> value that is equivalent to ''inline list-item''.