[e] (1) Clarify exactly what is meant by some of the line join requir…

…ements

git-svn-id: http://svn.whatwg.org/webapps@1203 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -16895,8 +16895,8 @@ idea from Mihai:
 
   <p>The <dfn id=linejoin
    title=dom-context-2d-lineJoin><code>lineJoin</code></dfn> attribute
-   defines the type of corners that that UAs will place where two lines meet.
-   The three valid values are <code>bevel</code>, <code>round</code>, and
+   defines the type of corners that UAs will place where two lines meet. The
+   three valid values are <code>bevel</code>, <code>round</code>, and
    <code>miter</code>.
 
   <p>On setting, any other value than the literal strings <code>bevel</code>,
@@ -16907,13 +16907,15 @@ idea from Mihai:
    href="#linejoin">lineJoin</a></code> attribute must initially have the
    value <code>miter</code>.
 
-  <p>A join exists at any point in a subpath shared by two consecutive pairs
-   of lines. When a subpath is closed, then a join also exists at its first
-   point (equivalent to its last point) connecting the first and last lines
-   in the subpath. In addition to the point where the join occurs, two
-   additional points are relevant to each join: the corners found half the
-   line width away from the join point, perpendicular to the two lines
-   joining at the join point.
+  <p>A join exists at any point in a subpath shared by two consecutive lines.
+   When a subpath is closed, then a join also exists at its first point
+   (equivalent to its last point) connecting the first and last lines in the
+   subpath.
+
+  <p>In addition to the point where the join occurs, two additional points
+   are relevant to each join, one for each line: the two corners found half
+   the line width away from the join point, one perpendicular to each line,
+   each on the side furthest from the other line.
 
   <p>A filled triangle connecting these two opposite corners with a straight
    line, with the third point of the triangle being the point of the join

source

@@ -14452,8 +14452,8 @@ idea from Mihai:
 
   <p>The <dfn
   title="dom-context-2d-lineJoin"><code>lineJoin</code></dfn>
-  attribute defines the type of corners that that UAs will place where
-  two lines meet. The three valid values are <code>bevel</code>,
+  attribute defines the type of corners that UAs will place where two
+  lines meet. The three valid values are <code>bevel</code>,
   <code>round</code>, and <code>miter</code>.</p>
 
   <p>On setting, any other value than the literal strings
@@ -14465,12 +14465,15 @@ idea from Mihai:
   initially have the value <code>miter</code>.</p>
 
   <p>A join exists at any point in a subpath shared by two consecutive
-  pairs of lines. When a subpath is closed, then a join also exists at
-  its first point (equivalent to its last point) connecting the first
-  and last lines in the subpath. In addition to the point where the
-  join occurs, two additional points are relevant to each join: the
-  corners found half the line width away from the join point,
-  perpendicular to the two lines joining at the join point.</p>
+  lines. When a subpath is closed, then a join also exists at its
+  first point (equivalent to its last point) connecting the first and
+  last lines in the subpath.</p>
+
+  <p>In addition to the point where the join occurs, two additional
+  points are relevant to each join, one for each line: the two corners
+  found half the line width away from the join point, one
+  perpendicular to each line, each on the side furthest from the other
+  line.</p>
 
   <p>A filled triangle connecting these two opposite corners with a
   straight line, with the third point of the triangle being the point