fixing typo

Author: howcom

css3-gcpm/Overview.src.html

@@ -2149,7 +2149,7 @@ <h2>Bookmarks</h2>
       <td><dfn>bookmark-label</dfn>
     <tr>
       <td><em>Value:</em>
-      <td>[ contents | content-before | content-element | content-after | &lt;string> ]+ | none
+      <td>[ &lt;content-list> ]+ | none
     <tr>
       <td><em>Initial:</em>
       <td>none
@@ -2171,7 +2171,8 @@ <h2>Bookmarks</h2>
 </table>
 
 <p>This property specifies the label of the bookmark, i.e., the text
-that will represent the bookmark in the bookmark structure. The keyword values are defined on the 'string-set' property. 
+that will represent the bookmark in the bookmark structure.
+&lt;content-list> is defined on the 'string-set' property.
 
 <div class="example">
 <pre>
@@ -2571,11 +2572,41 @@ <h2>Page and column floats</h2>
 <dt>bottom-corner
 <dd>similar to 'top-corner', exept the box is floated to the bottom
 
-<dt>snap
-<dd>same as 'top' if the box is naturally near the top; same as 'bottom' if the box is naturally near the bottom. The 'widows'/'orphans' properties may be consulted to determine if the box is near the top/bottom. If
-the box naturally leads to a (page/column) break, the box is floated to the top of the next page/column. 
+<dt>snap(&lt;length>)
+
+<dd>same as 'top' if the box is naturally near the top; same as
+'bottom' if the box is naturally near the bottom. If the box naturally
+leads to a (page/column) break, the box is floated to the top of the
+next page/column. The length value specifies how far from the
+top/bottom the element can be influenced.
+
+<div class=example>
+<p>In this example, tables will snap to the top/bottom if the top/bottom of the border box is closer than '3em' from the top/bottom of the page/column.
+
+<pre>
+table { float: snap(3em) }
+</pre>
+</div>
+
+<p>If the functional notation is not used, an implementation-dependent value is used. 
+
+<div class=example>
+<pre>
+table { float: snap }
+</pre>
+</div>
+
+<p class=issue>Should we define a reasonable default (say, 3em) instead of relying on implementation-specific values? 
+<p class=issue>Do numberic values make sense, like for orphans/widows
+<p class=issue>Does the "snap" solution address all use cases for "unless-room"/"unless-fit"?
+
+
 </dl>
 
+<!--
+The 'widows'/'orphans' properties may be consulted to determine if the box is near the top/bottom. 
+-->
+
 <p>These new keywords only apply in paged media; in continous media declarations with these keywords are ignored. 
 
 <div class=example>