[css-multicol] Update introduction

Updated the introduction to remove mention of the benefits of multicol over using tables for layout and instead refer to the unique characteristics of multicol. #3654

Author: rachelandrew

css-multicol-1/Overview.bs

@@ -51,13 +51,9 @@ Introduction</h2>
 	that the content of an element is to be laid out in multiple
 	columns.
 
-	On the Web, tables have also been used to describe multi-column
-	layouts. The main benefit of using CSS-based columns is flexibility;
-	content can flow from one column to another, and the number of columns
-	can vary depending on the size of the viewport. Removing presentation
-	table markup from documents allows them to more easily be presented on
-	various output devices including speech synthesizers and small mobile
-	devices.
+	Other layout methods in CSS, when applied to a parent element, change the display properties of the direct children. For example if a three column grid layout is created, the direct children of the grid container become grid items and are placed into the column tracks, one element per cell with additional rows created as needed.
+
+	The child elements of a multi-column container however continue in normal flow, that flow is arranged into a number of columns. These columns have a flexible inline size, and therefore respond to available space by changing the size or number of columns displayed. 
 
 	Multi-column layouts are easy to describe in CSS. Here is a simple example:
 
@@ -1418,6 +1414,7 @@ This appendix is <em>informative</em>.
 
 <h3 id="changes-from-20171005">Changes from the <a href="https://www.w3.org/TR/2018/WD-css-multicol-1-20180528/">Working Draft (WD) of 28 May 2018</a></h3>
 <ul>
+	<li>Updated the introduction to remove mention of the benefits of multicol over using tables for layout and instead refer to the unique characteristics of multicol. Editorial change referenced in <a href="https://github.com/w3c/csswg-drafts/issues/3654">issue 3654</a>.</li>
 	<li>Changed the sentence added in the pseudo-algorithm section after the 7 Jan 2016 resolution, to refer to <em>columns</em> and not <em>tracks</em> as tracks are not defined in this specification. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/3649#issuecomment-472505520">13 March 2019</a>.</li>
 	<li>Changes and clarifications to the SVG images used in the specification.</li>
 </ul>