[css2] Punctuation and similar small changes.

bert-github · bert-github · commit 6b20462a3cf7 · 2009-05-15T17:31:52.000Z
--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402946
diff --git a/css2/cascade.src b/css2/cascade.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: cascade.src,v 2.65 2008-11-26 15:05:03 bbos Exp $ -->
+<!-- $Id: cascade.src,v 2.66 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Assigning property values, Cascading, and Inheritance</TITLE>
 </HEAD>
@@ -54,7 +54,7 @@ property. See the section on <a href="#inheritance">inheritance</a>
 for the definition of computed values when the specified value is
 'inherit'.
 
-<p>The computed value exists even when the property doesn't apply, as
+<p>The computed value exists even when the property does not apply, as
 defined by the <a href="about.html#applies-to">'Applies To'</a> line.
 However, some
 properties may define the computed value of a property for an element
diff --git a/css2/changes.src b/css2/changes.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: changes.src,v 2.108 2009-04-23 14:40:39 bbos Exp $ -->
+<!-- $Id: changes.src,v 2.109 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Changes</TITLE>
 </HEAD>
@@ -568,7 +568,7 @@ Text direction</a></h3>
 <p>Conforming UAs are now allowed to not support bidirectional text; in
 this case they must ignore the 'direction' and 'unicode-bidi' properties.
 However since applying bidi can have an effect even when a document
-doesn't contain right-to-left characters, UAs that do support bidi are
+does not contain right-to-left characters, UAs that do support bidi are
 no longer permitted to not apply the algorithm just because the document
 lacks right-to-left characters.</p>
 
@@ -1599,7 +1599,7 @@ Text direction</a></h3>
 
 <p>Corrected note about 'direction' on table column elements to say
 that "columns are not the ancestors of the cells in the document tree"
-rather than saying "columns don't exist in the document tree".</p>
+rather than saying "columns do not exist in the document tree".</p>
 
 <p>Added table cells, table captions, and inline blocks alongside
 block-level elements in description of 'bidi-override' value. Also
@@ -1661,7 +1661,7 @@ and inline-block elements".</p>
 another DIV was not rendered correctly. The first style rule applied
 to both DIVs, so the second DIV box should have been rendered with a
 red border as well. The second DIV has now been changed to a CITE,
-which doesn't have a red border.
+which does not have a red border.
 
 <h3 id="x11.1.2"><a href="visufx.html#clipping">Section 11.1.2 Clipping:
 the 'clip' property</a></h3>
@@ -1677,7 +1677,7 @@ Visibility</a></h3>
 <h3 id="x12.4.2"><a href="generate.html#counter-styles">Section 12.4.2 Counter
 styles</a></h3>
 
-<p>The example used the style 'hebrew', which doesn't exist in CSS
+<p>The example used the style 'hebrew', which does not exist in CSS
 level�2. Changed to 'lower-greek'.
 
 <h3 id="x12.6.2"><a href="generate.html#list-style">Section 12.6.2 Lists</a></h3>
@@ -1960,7 +1960,7 @@ Integers and real numbers</a></h3>
 <h3 id="r4.3.2"><a href="syndata.html#length-units">Section 4.3.2
 Lengths</a></h3>
 
-<p>Clarified that negative length values on properties that don't allow them
+<p>Clarified that negative length values on properties that do not allow them
 cause the declaration to be ignored.</p>
 
 <h3 id="r4.3.4"><a href="syndata.html#uri">Section 4.3.4
@@ -2182,7 +2182,7 @@ as that situation is now defined in <a href="box.html#bidi-box-model">section
 <h3 id="r9.4.3"><a href="visuren.html#relative-positioning">Section 9.4.3
 Relative positioning</a></h3>
 
-<p>Clarified that although relative positioning normally doesn't
+<p>Clarified that although relative positioning normally does not
 directly affect layout, it may affect layout indirectly through
 the creation of scrollbars.</p>
 
@@ -2345,7 +2345,7 @@ different languages are mixed.</p>
 Automatic counters and numbering</a></h3>
 
 <p>In the "self-nesting" behavior of counters, clarified that merely
-using a counter in a child element doesn't create a new instance of it:
+using a counter in a child element does not create a new instance of it:
 only resetting it does.</p>
 
 <p>Clarified that the scope of a counter does not include any elements
@@ -2378,7 +2378,7 @@ stacking context and referred to z-index property for details.</p>
 
 <blockquote><p>Note that there is only <em>one</em> viewport per
 document. I.e., even if an element has a scrolling mechanism (see
-'overflow'), a 'fixed' background doesn't move with it.</blockquote>
+'overflow'), a 'fixed' background does not move with it.</blockquote>
 
 <p>Definition of 'background-position' has been rewritten as normative rules
 rather than just examples.</p>
@@ -2796,7 +2796,7 @@ Rule sets, declaration blocks, and selectors</a></h3>
 <p><span class=date>[2008-11-26]</span> More precise statement of what
 is ignored:
 
-<blockquote><p>When a user agent can't parse the selector (i.e., it is
+<blockquote><p>When a user agent cannot parse the selector (i.e., it is
 not valid CSS&nbsp;2.1), it must ignore the <ins>selector and the
 following</ins> declaration block <ins>(if any)</ins> as
 well.</blockquote>
@@ -3251,7 +3251,7 @@ Section 10.3.2 Inline, replaced elements</a></h3>
 follows:
 
 <blockquote><p>If it does, <del>then a percentage intrinsic width on
-that element can't be resolved and the element is assumed to have no
+that element cannot be resolved and the element is assumed to have no
 intrinsic width</del> <ins>then the resulting layout is undefined in
 CSS2.1</ins>.</blockquote>
 
@@ -3588,7 +3588,7 @@ sheet</a></h3>
 
 <p><span class=date>[2009-02-02]</span> <p>Remove sections 13.2.1.1
 and 13.2.1.2. (The described situations cannot occur in CSS&nbsp;2.1,
-because CSS&nbsp;2.1 doesn't have a 'size' property.)
+because CSS&nbsp;2.1 does not have a 'size' property.)
 
 <!--========================== issue 76 ===========================-->
 
diff --git a/css2/colors.src b/css2/colors.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: colors.src,v 2.53 2009-04-15 13:26:27 bbos Exp $ -->
+<!-- $Id: colors.src,v 2.54 2009-05-15 17:31:38 bbos Exp $ -->
 <head>
 <title>Colors and backgrounds</title>
 <meta name="editor" lang="tr" content="Tantek &Ccedil;elik">
@@ -231,8 +231,8 @@ href="visuren.html#viewport">viewport</a> ('fixed') or scrolls along
 with the containing block ('scroll').</p>
 
 <p>Note that there is only one viewport per view. If an element has
-a scrolling mechanism (see 'overflow'), a 'fixed' background doesn't
-move with the element, and a 'scroll' background doesn't move with
+a scrolling mechanism (see 'overflow'), a 'fixed' background does not
+move with the element, and a 'scroll' background does not move with
 the scrolling mechanism.</p>
 
 <p>Even if the image is fixed, it is still only visible when it is in
diff --git a/css2/fonts.src b/css2/fonts.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: fonts.src,v 2.94 2009-02-23 21:08:16 bbos Exp $ -->
+<!-- $Id: fonts.src,v 2.95 2009-05-15 17:31:38 bbos Exp $ -->
 <head>
 <title>Fonts</title>
 <meta name="editor" lang="tr" content="Tantek &Ccedil;elik">
@@ -62,7 +62,7 @@ processed by step 2, and if there is a next alternative 'font-family'
 in the font set, then repeat step 2 with the next alternative
 'font-family'.
 </li>
-<li>If there is a matching font face, but it doesn't contain a glyph
+<li>If there is a matching font face, but it does not contain a glyph
 for the current character, and if there is a next alternative
 'font-family' in the font sets, then repeat step 2 with the next
 alternative 'font-family'.
diff --git a/css2/generate.src b/css2/generate.src
@@ -218,7 +218,7 @@ class="value-inst-no-close-quote"><strong>no-close-quote</strong></span></span>
 <dd>This function returns as a string the value of attribute X 
 for the subject of the selector. The
 string is not parsed by the CSS processor.  If the subject of the selector
-doesn't have an attribute X, an empty string is returned. The
+does not have an attribute X, an empty string is returned. The
 case-sensitivity of attribute names depends on the document language. 
 </dl>
 
diff --git a/css2/grammar.src b/css2/grammar.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: grammar.src,v 2.58 2009-04-09 17:10:27 bbos Exp $ -->
+<!-- $Id: grammar.src,v 2.59 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Grammar of CSS&nbsp;2.1</TITLE>
 </HEAD>
@@ -22,7 +22,7 @@ the "class" attribute.
 
 <P> The grammar below is <span class="index-inst"
 title="LALR(1)">LALR(1)</span> (but note that most UA's should not use it
-directly, since it doesn't express the <a
+directly, since it does not express the <a
 href="syndata.html#parsing-errors">parsing conventions</a>, only the
 CSS&nbsp;2.1 syntax). The format of the productions is optimized for human
 consumption and some shorthand notation beyond Yacc (see [[YACC]]) is
@@ -248,7 +248,7 @@ CSS1</a></h2>
 
 <p>There are some differences in the syntax specified in the CSS1
 recommendation ([[-CSS1]]), and the one above. Most of these are due
-to new tokens in CSS2 that didn't exist in CSS1. Others are because
+to new tokens in CSS2 that did not exist in CSS1. Others are because
 the grammar has been rewritten to be more readable. However, there are
 some incompatible changes, that were felt to be errors in the CSS1
 syntax. They are explained below.
diff --git a/css2/images/longdesc/pixel1-desc.html b/css2/images/longdesc/pixel1-desc.html
@@ -15,7 +15,7 @@ <h1>Long description for the illustration of a pixel's definition</h1>
 <P>The image depicts the user looking at two planes, one 28 inches (71
 cm) from the user, the second 140 inches (3.5 m) from the user. An
 expanding cone is projected from the user's eye onto each plane. Where
-the cone strikes the first plane, the projected pixel is .28 mm
+the cone strikes the first plane, the projected pixel is 0.26 mm
 high. Where the cone strikes the second plane, the projected pixel is
 1.4mm high.
 
diff --git a/css2/images/pixel1.idraw b/css2/images/pixel1.idraw
@@ -728,7 +728,7 @@ Helvetica 14 SetF
 [ 1 0 0 1 293 580 ] concat
 %I
 [
-(28 inch)
+(28 inches)
 (71 cm)
 ] Text
 End
@@ -757,7 +757,7 @@ Helvetica 14 SetF
 [ 1 0 0 1 361 522 ] concat
 %I
 [
-(140 inch)
+(140 inches)
 (3.5 m)
 ] Text
 End
diff --git a/css2/intro.src b/css2/intro.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: intro.src,v 2.50 2009-05-12 11:47:41 bbos Exp $ -->
+<!-- $Id: intro.src,v 2.51 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Introduction to CSS&nbsp;2.1</TITLE>
 </HEAD>
@@ -158,7 +158,7 @@ semicolons, though the last declaration may also be followed by a
 semicolon.
 
 <P>The first declaration on the BODY element sets the font family to
-"Gill Sans". If that font isn't available, the user agent (often
+"Gill Sans". If that font is not available, the user agent (often
 referred to as a "browser") will use the 'sans-serif' font family
 which is one of five generic font families which all users agents
 know. Child elements of BODY will inherit the value of the <span
@@ -181,7 +181,7 @@ element are three times wider than the font size.
 <P>CSS can be used with any structured document format, for example
 with applications of the eXtensible Markup Language [[-XML10]]. In
 fact, XML depends more on style sheets than HTML, since authors can
-make up their own elements that user agents don't know how to
+make up their own elements that user agents do not know how to
 display.
 
 <P>Here is a simple XML fragment:
@@ -240,7 +240,7 @@ a processing instruction:
 <P>Notice that the word "flute" remains within the paragraph since it
 is the content of the inline element INSTRUMENT.
 
-<P>Still, the text isn't formatted the way you would expect. For
+<P>Still, the text is not formatted the way you would expect. For
 example, the headline font size should be larger than then the rest of
 the text, and you may want to display the author's name in italic:</P>
 
@@ -375,7 +375,7 @@ interface</a>).
 <LI>
 <P><STRONG>Forward and backward compatibility</STRONG>. CSS&nbsp;2.1 user
 agents will be able to understand CSS1 style sheets. CSS1 user agents
-will be able to read CSS&nbsp;2.1 style sheets and discard parts they don't
+will be able to read CSS&nbsp;2.1 style sheets and discard parts they do not
 understand. Also, user agents with no CSS support will be able to
 display style-enhanced documents. Of course, the stylistic
 enhancements made possible by CSS will not be rendered, but all
diff --git a/css2/media.src b/css2/media.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: media.src,v 2.44 2008-12-02 18:50:38 bbos Exp $ -->
+<!-- $Id: media.src,v 2.45 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Media types</TITLE>
 </HEAD>
@@ -253,7 +253,7 @@ devices that allow user interaction), or
 <span
 class="index-def" title="'static' media group"><a
 name="static-media-group"><strong>static</strong></a></span> (for
-those that don't).
+those that do not).
 
 <li><span class="index-def" title="'all'
 media group"> <a name="all-media-group"><strong>all</strong></a></span>
diff --git a/css2/page.src b/css2/page.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: page.src,v 2.60 2009-04-15 13:26:27 bbos Exp $ -->
+<!-- $Id: page.src,v 2.61 2009-05-15 17:31:38 bbos Exp $ -->
 <HEAD>
 <TITLE>Paged media</TITLE>
 </HEAD> 
@@ -204,7 +204,7 @@ the page box:</p>
 pages to "bleed".
 
 <li>User agents should avoid generating a large number of empty page
-boxes to honor the positioning of elements (e.g., you don't want to
+boxes to honor the positioning of elements (e.g., you do not want to
 print 100 blank pages).
 
 <li>Authors should not position elements in inconvenient locations
@@ -359,7 +359,7 @@ class="propinst-page-break-inside">'page-break-inside'</span> property
 of the element and all its ancestors is 'auto'.
 </ul>
 
-<p>If the above doesn't provide enough break points to keep content
+<p>If the above does not provide enough break points to keep content
 from overflowing the page boxes, then rules A, B and D are dropped in
 order to find additional breakpoints.
 
@@ -386,7 +386,7 @@ that they are sometimes contradictory):</p>
 
 <ul>
 <li>Break as few times as possible.
-<li>Make all pages that don't end with a forced break appear to have about
+<li>Make all pages that do not end with a forced break appear to have about
 the same height.
 <li>Avoid breaking inside a replaced element.
 </ul>
diff --git a/css2/selector.src b/css2/selector.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01//EN'>
 <html lang="en">
-<!-- $Id: selector.src,v 2.113 2009-04-15 07:25:26 bbos Exp $ -->
+<!-- $Id: selector.src,v 2.114 2009-05-15 17:31:38 bbos Exp $ -->
 <head>
 <title>Selectors</title>
 </head>
@@ -881,12 +881,12 @@ focus (accepts keyboard events or other forms of text input).
 
 <p>An element may match several pseudo-classes at the same time.
 
-<p>CSS doesn't define which elements may be in the above states, or
+<p>CSS does not define which elements may be in the above states, or
 how the states are entered and left. Scripting may change whether
 elements react to user events or not, and different devices and UAs
 may have different ways of pointing to, or activating elements.
 
-<p>CSS&nbsp;2.1 doesn't define if the parent of an element that is
+<p>CSS&nbsp;2.1 does not define if the parent of an element that is
 ':active' or ':hover' is also in that state.
 
 <p>User agents are not required to reflow a currently displayed
@@ -971,7 +971,7 @@ being either equal to, or a hyphen-separated substring of, the
 element's language value, in the same way as if performed by the <a
 href="#attribute-selectors">'|='</a> operator. The matching of C
 against the element's language value is performed case-insensitively.
-The identifier C doesn't have to be a valid language name.</p>
+The identifier C does not have to be a valid language name.</p>
 
 <p>C must not be empty.
 
@@ -1120,7 +1120,7 @@ etcetera&lt;/DIV&gt;</code> the first formatted line of the DIV is not
 the line "Hello".
 
 <p class="note">Note that the first line of the P in this fragment:
-<code>&lt;p&gt&lt;br&gt;First...</code> doesn't contain any letters
+<code>&lt;p&gt&lt;br&gt;First...</code> does not contain any letters
 (assuming the default style for BR in HTML 4). The word "First" is
 not on the first formatted line.
 
@@ -1199,7 +1199,7 @@ have specific properties that apply to first-letter.
 <p>This example shows a possible rendering of an initial cap. Note
 that the 'line-height' that is inherited by the first-letter
 pseudo-element is 1.1, but the UA in this example has computed the
-height of the first letter differently, so that it doesn't cause any
+height of the first letter differently, so that it does not cause any
 unnecessary space between the first two lines. Also note that the
 fictional start tag of the first letter is inside the SPAN, and thus
 the font weight of the first letter is normal, not bold as the SPAN:
@@ -1313,12 +1313,12 @@ fragment:
 first letter of an ancestor element. Thus, in <code>&lt;DIV&gt;&lt;P
 STYLE="display: inline-block">Hello&lt;BR&gt;Goodbye&lt;/P&gt;
 etcetera&lt;/DIV&gt;</code> the first letter of the DIV is not the
-letter "H". In fact, the DIV doesn't have a first letter.
+letter "H". In fact, the DIV does not have a first letter.
 
 <p>The first letter must occur on the <a
 href="#first-formatted-line">first formatted line.</a> For example, in
 this fragment: <code>&lt;p&gt&lt;br&gt;First...</code> the first line
-doesn't contain any letters and ':first-letter' doesn't match anything
+does not contain any letters and ':first-letter' does not match anything
 (assuming the default style for BR in HTML 4). In particular, it
 does not match the "F" of "First."
 
diff --git a/css2/syndata.src b/css2/syndata.src
diff --git a/css2/tables.src b/css2/tables.src
diff --git a/css2/text.src b/css2/text.src
diff --git a/css2/ui.src b/css2/ui.src
diff --git a/css2/visudet.src b/css2/visudet.src
diff --git a/css2/visuren.src b/css2/visuren.src
