fixing typos, adding text on inline footnotes

Author: howcom

css3-gcpm/Overview.src.html

@@ -287,22 +287,28 @@ <h4>Setting named strings: the 'string-set' property</h4>
 <dt>''env()''
 
 <dd>This function returns data from the environment of the user at
-the time of formatting. 
+the time of formatting. The function accepts one of these keywords:
 
-<div class=example>
+<ul>
+<li>env(url): returns the URL of the document
+<li>env(date): returns the date on the user's system at the time of formatting
+<li>env(time): returns the time on the user's system at the time of formatting
+<li>env(date-time): returns the date and time on the user's system at the time of formatting
+</ul>
 
-<p>Possible uses of this function are:
+<p class=note>Information about date and time is formatted according to the locale of the user. Implementors can get access to preformatted strings by way of the <a href="http://www.opengroup.org/onlinepubs/009695399/functions/strftime.html">strftime</a> function. The date, time and date-time strings can be found by using the "%x", "%X" and "%c" conversion strings, respectively.
+
+<div class=example>
 
 <pre>
+string-set: url env(url);
 string-set: date env(date);
 string-set: date env(time);
 string-set: date env(date-time);
-string-set: url env(url);
 </pre>
 
 </div>
 
-<p class=note>Information about date and time is formatted according to the locale of the user. Implementors can get access to preformatted strings by way of the <a href="http://www.opengroup.org/onlinepubs/009695399/functions/strftime.html">strftime</a> function. The date, time and date-time strings can be found by using the "%x", "%X" and "%c" conversion strings, respectively
 
 </dl>
 </dl>
@@ -836,7 +842,7 @@ <h2>Footnotes</h2>
 
 <pre>
 &lt;style>
-.footnote { float: footnote; display: block; }
+.footnote { float: footnote }
 &lt;/style>
 
 &lt;p>A sentence consists of words. &lt;span class="footnote">Most often.&lt;/span>.
@@ -866,7 +872,6 @@ <h2>Footnotes</h2>
 @media print {
   .footnote { 
     float: footnote;
-    display: block;
     content: target-pull(attr(href, url)) }
   .call { display: none }
 }
@@ -900,7 +905,6 @@ <h2>Footnotes</h2>
 span[title]::after { 
   content: attr(title);
   float: footnote;
-  display: block;
 }
 </pre>
 </div>
@@ -916,45 +920,45 @@ <h3>Turning elements into footnotes</h3>
 <pre>
 span.footnote { 
   float: footnote;
-  display: block;
 }
 </pre>
 </div>
 
-<p>The 'display' property determines how elements in the footnote area are displayed. 
+<p>Footnote elements are presented inside the <em>footnote area</em>,
+but they inherit through their normal place in the structure of the
+document.
+
+<p>The 'display' property on footnote elements is ignored. Instead,
+the value of the 'display' property in the @footnote context
+determines if footnotes are block or inline elements.
 
 <div class="example">
 <p>In this example, the footnotes are displayed inline:
 
 <pre>
+@footnote { 
+  display: inline;
+}
 span.footnote { 
   float: footnote;
-  display: inline; /* probably not necessary for &lt;span&gt; elements */
 }
 span.footnote::before { 
   content: counter(footnote);
 }
 </pre>
+
 <p>Here is one possible presentation of inline footnotes:
 
 <pre>
 &#xB9; The first footnote. &#xBA; The second footnote. 
 </pre>
 </div>
 
-<p class=issue>Instead of relying on the 'display' property for each footnote element, there could be a setting in @footnote for this.
+<p class=issue>Another way to achieve this would be to introduce different keywords for inline and block footnotes (e.g., float: footnote-inline, float: footnote-block). 
 
 <p>For each new footnote element, the ''footnote'' counter is automatically
 incremented. 
 
-<p>Footnote elements are presented inside the <em>footnote area</em>,
-but they inherit through their normal place in the structure of the
-document.
-
-<!--
-<p class="issue">There has been a number of proposals on how to achieve this, including ''position: footnote'', ''flow: footnote'', and ''display: footnote''. The current thinking is that 'float' is suitable as the content still takes up space.
--->
-
 
 <h3>The footnote area</h3>