Corrected spelling, formatting

Author: HalloweenCreature

index.html

@@ -898,7 +898,7 @@ <h3>
   padding: 0;
 }</code></pre>
           <p>
-            There a couple of points worth noting in the <abbr>CSS</abbr>. The table has been centered by giving the left and right margins a value of <code>auto</code>. For block-level elements a <code>width</code> declaration would also be required when applying this technique, however tables have an inherent width so one does not need to be specified explicitly.
+            There a couple of points worth noting in the <abbr>CSS</abbr>. The table has been centred by giving the left and right margins a value of <code>auto</code>. For block-level elements a <code>width</code> declaration would also be required when applying this technique, however tables have an inherent width so one does not need to be specified explicitly.
           </p>
           <p>
             The bullet points separating chapter titles and page numbers have been generated by the <abbr>CSS</abbr>. Specifically a bullet point (Unicode character 2022) has been inserted before the <code>td</code> element. Generated content is not supported by Internet Explorer 6 or 7, so a more cross-browser alternative would be to write a bullet point entity <code>&amp;#8226;</code> into the markup itself.
@@ -1270,7 +1270,7 @@ <h2>
           <blockquote>
             <span class="quote">“</span>
             <p>
-              Verse is usually set flush left and ragged right, and verse quotations within prose should not be deprived of their chosen form. But to distinguish verse quotations from surrounding prose, they should be indented or centered on the longest line.”
+              Verse is usually set flush left and ragged right, and verse quotations within prose should not be deprived of their chosen form. But to distinguish verse quotations from surrounding prose, they should be indented or centred on the longest line.”
             </p>
           </blockquote>
           <p>
@@ -1289,7 +1289,7 @@ <h2>
   font-family: inherit;
 }</code></pre>
           <p>
-            A logical way to center the verse on the longest line would be to simply specify <code>width:auto</code> and <code>margin:0 auto</code>. Unfortunately, due to browsers’ rendering of preformatted elements, the element will still be considered to comprise full-width lines, so no centering will occur. However we can work around this by specifying the <code>pre</code> element to display as a <code>table</code> as follows:
+            A logical way to center the verse on the longest line would be to simply specify <code>width:auto</code> and <code>margin:0 auto</code>. Unfortunately, due to browsers’ rendering of preformatted elements, the element will still be considered to comprise full-width lines, so no centring will occur. However we can work around this by specifying the <code>pre</code> element to display as a <code>table</code> as follows:
           </p>
           <pre data-lang="CSS"><code>.verse pre {
   font-family: inherit;
@@ -1307,7 +1307,7 @@ <h2>
 Thinks in a marrow bone.&lt;/span&gt;&lt;/pre&gt;
 &lt;/blockquote&gt;</code></pre>
           <p>
-            This <code>span</code> can then be centered in Internet Explorer applying <code>text-align:center</code> to the <code>pre</code> and resetting the text alignment on the <code>span</code> element.
+            This <code>span</code> can then be centred in Internet Explorer applying <code>text-align:center</code> to the <code>pre</code> and resetting the text alignment on the <code>span</code> element.
           </p>
           <pre data-lang="CSS"><code>.verse pre {
   text-align: center;
@@ -1335,7 +1335,7 @@ <h2>
   &lt;link rel="stylesheet" type="text/css" href="ie-lte-7.css" /&gt;
 &lt;![endif]-&gt;</code></pre>
           <p>
-            Here’s the final rendered example of prose, set flush left & ragged right, and centered on the longest line:
+            Here’s the final rendered example of prose, set flush left & ragged right, and centred on the longest line:
           </p>
           <figure id="example-12">
             <p>
@@ -1379,7 +1379,7 @@ <h3>
             The Future
           </h3>
           <p>
-            Until recently, the <a class="ext-link" href="https://www.w3.org/TR/css3-text/#hyphenate" target="_blank"><abrr>CSS</abbr> 3 Text module</a> contained the <code>hyphenate</code> property which could be set to <code>auto</code> or <code>none</code>. This property introduced the concept of automatic hyphenation to browsers, and would require that the web browser has a hyphenation dictionary for the language of the text being hyphenated. For example:
+            Until recently, the <a class="ext-link" href="https://www.w3.org/TR/css3-text/#hyphenate" target="_blank"><abbr>CSS</abbr> 3 Text module</a> contained the <code>hyphenate</code> property which could be set to <code>auto</code> or <code>none</code>. This property introduced the concept of automatic hyphenation to browsers, and would require that the web browser has a hyphenation dictionary for the language of the text being hyphenated. For example:
           </p>
           <pre data-lang="CSS"><code>p {
   hyphenate: auto;
@@ -1400,7 +1400,7 @@ <h2>
             </h2>
           </header>
           <p>
-            This guideline can be achieved easily when hyphenating manually. See <a href="#At_hyphenated_line-ends,_leave_at_least_two_characters_behind_and_take_at_least_three_forward" target="_blank">§2.4.1</a> for more information on manual hypenation.
+            This guideline can be achieved easily when hyphenating manually. See <a href="#At_hyphenated_line-ends,_leave_at_least_two_characters_behind_and_take_at_least_three_forward" target="_blank">§2.4.1</a> for more information on manual hyphenation.
           </p>
           <h3>
             The Future
@@ -1474,7 +1474,7 @@ <h2>
           </p>
           <pre data-lang="HTML"><code>1&amp;nbsp;inch is equivalent to 2.54&amp;nbsp;cm.</code></pre>
           <p>
-            It should not really be expected of authors to type <code>&amp;nbsp;</code> everytime a non-breaking space is required. This is a job that, to some degree, can be performed automatically by a content management system. To demonstrate this by way of simple <abbr>PHP</abbr> example, a regular expression function could automatically insert non-breaking spaces as follows:
+            It should not really be expected of authors to type <code>&amp;nbsp;</code> every time a non-breaking space is required. This is a job that, to some degree, can be performed automatically by a content management system. To demonstrate this by way of simple <abbr>PHP</abbr> example, a regular expression function could automatically insert non-breaking spaces as follows:
           </p>
           <pre data-lang="PHP"><code>$search = '/([0-9]) ([a-zA-Z])/';
 $replace = '$1&amp;nbsp;$2';
@@ -1500,7 +1500,7 @@ <h2>
             Comprehensive control for page breaks was introduced in <abbr>CSS</abbr> 2, however browser support is currently limited to Opera 9. The only paging properties supported by Internet Explorer 7, Safari 3 and Firefox 2 are <code>page-break-before</code> and <code>page-break-after</code> (this is also true of <abbr>IE8</abbr> beta and Firefox 3 beta at time of writing).
           </p>
           <p>
-            The <code>page-break-before</code> and <code>page-break-after</code> properties enable you to say that a page break should occur before or after the specified element. The following example starts a new page everytime an <code>h1</code> heading is encountered and after every <code>.section</code> block.
+            The <code>page-break-before</code> and <code>page-break-after</code> properties enable you to say that a page break should occur before or after the specified element. The following example starts a new page every time an <code>h1</code> heading is encountered and after every <code>.section</code> block.
           </p>
           <pre data-lang="CSS"><code>h1 {
   page-break-before: always;