# Markup Validation Service

Check the markup (HTML, XHTML, …) of Web documents

## Errors found while checking this document as XHTML 1.0 Strict!

Result: | 426 Errors, 42 warning(s)
Address: |
Encoding: | utf-8 |
Doctype: | XHTML 1.0 Strict |
Root Element: | html
Root Namespace: | http://www.w3.org/1999/xhtml

Options

Show Source | Show Outline | List Messages Sequentially Group Error Messages by Type
Validate error pages | Verbose Output | Clean up Markup with HTML Tidy

Help on the options is available.

↑ Top

### Validation Output: 426 Errors

1. Line 24, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified

       …="y_key" content="1d8b62e6da1997a…

   ✉

   You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

2. Line 24: start tag was here

       ><meta name="y_key" content="1d8b62e6da1997ab">

3. Line 169, Column 299: character "&amp;" is the first character of a delimiter but occurred as data

       …type="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServ

   ✉

   This message may appear in several cases:

   - You tried to include the "<" character in your page: you should escape it as "&lt;"
   - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   - Another possibility is that you forgot to close quotes in a previous tag.
4. Line 169, Column 300: character "&amp;" is the first character of a delimiter but occurred as data

       …ype="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServi

   ✉

   This message may appear in several cases:

   - You tried to include the "<" character in your page: you should escape it as "&lt;"
   - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   - Another possibility is that you forgot to close quotes in a previous tag.
5. Line 244, Column 31: an attribute value must be a literal unless it contains only name characters

       document.writeln('<style type=\"text/css\">');

   ✉

   You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

6. Line 244, Column 43: document type does not allow element "style" here

       document.writeln('<style type=\"text/css\">');

   ✉

   The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

   One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

7. Line 328, Column 71: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

       …" class="txt" type="text" value="" /> <a onclick="if ($('#txt_searchBox')[0].

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

8. Line 328, Column 187: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

       …('#fm_Search').submit();};" href="#"><img alt="Search" src="/gfx/00/07/40/bt-

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

9. Line 986, Column 82: character "&amp;" is the first character of a delimiter but occurred as data

       …chedule---results/" title="Schedule & Results">Schedule & Results</a></li>

   ✉

   This message may appear in several cases:

   - You tried to include the "<" character in your page: you should escape it as "&lt;"
   - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   - Another possibility is that you forgot to close quotes in a previous tag.
10. Line 986, Column 102: character "&amp;" is the first character of a delimiter but occurred as data

        …title="Schedule & Results">Schedule & Results</a></li>

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
11. Line 1090, Column 20: Attribute "language" exists, but can not be used for this element.

        		<script language="JavaScript" type="text/javascript">

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

12. Line 1097, Column 28: an attribute value must be a literal unless it contains only name characters

        document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

13. Line 1097, Column 57: "height:" is not a member of a group specified for any attribute

        … style=\"position:relative; height: 293px;\"><div style=\"position:absolute;

    ✉

14. Line 1097, Column 57: "293px" is not a member of a group specified for any attribute

        … style=\"position:relative; height: 293px;\"><div style=\"position:absolute;

    ✉

15. Line 1097, Column 65: document type does not allow element "div" here

        …"position:relative; height: 293px;\"><div style=\"position:absolute; left: -1

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

16. Line 1097, Column 77: an attribute value must be a literal unless it contains only name characters

        …:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

17. Line 1097, Column 104: "left:" is not a member of a group specified for any attribute

        …iv style=\"position:absolute; left: -19px;\">");

    ✉

18. Line 1097, Column 104: "-19px" is not a member of a group specified for any attribute

        …iv style=\"position:absolute; left: -19px;\">");

    ✉

19. Line 1356, Column 141: required attribute "alt" not specified

        …/27/46/96639829_50imgGalTh-UO.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

20. Line 1365, Column 147: required attribute "alt" not specified

        …/44/96639019-10_44imgGalTh-Vw.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

21. Line 1374, Column 147: required attribute "alt" not specified

        …/44/96638966-10_30imgGalTh-xl.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

22. Line 1383, Column 147: required attribute "alt" not specified

        …/44/96638932-10_32imgGalTh-YU.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

23. Line 1392, Column 147: required attribute "alt" not specified

        …/44/96638984-10_34imgGalTh-ul.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

24. Line 1401, Column 147: required attribute "alt" not specified

        …/44/96638985-10_36imgGalTh-Vs.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

25. Line 1420, Column 147: required attribute "alt" not specified

        …/44/96639006-10_40imgGalTh-dY.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

26. Line 1429, Column 147: required attribute "alt" not specified

        …/44/96639016-10_42imgGalTh-Qv.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

27. Line 1438, Column 147: required attribute "alt" not specified

        …/44/96638914-10_24imgGalTh-Gd.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

28. Line 1447, Column 147: required attribute "alt" not specified

        …/44/96638919-10_26imgGalTh-pY.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

29. Line 1456, Column 147: required attribute "alt" not specified

        …/44/96638921-10_28imgGalTh-NT.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

30. Line 1465, Column 147: required attribute "alt" not specified

        …/44/96637898-10_14imgGalTh-Fa.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

31. Line 1484, Column 147: required attribute "alt" not specified

        …/44/96638333-10_16imgGalTh-xd.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

32. Line 1493, Column 147: required attribute "alt" not specified

        …/44/96638831-10_18imgGalTh-Vi.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

33. Line 1502, Column 147: required attribute "alt" not specified

        …/44/96638850-10_20imgGalTh-Rs.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

34. Line 1511, Column 147: required attribute "alt" not specified

        …/44/96638913-10_22imgGalTh-fW.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

35. Line 1520, Column 330: required attribute "alt" not specified

        …igital-download_42imgGalTh-ql.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

36. Line 1529, Column 330: required attribute "alt" not specified

        …igital-download_40imgGalTh-xO.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

37. Line 1548, Column 330: required attribute "alt" not specified

        …igital-download_38imgGalTh-co.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

38. Line 1557, Column 330: required attribute "alt" not specified

        …igital-download_36imgGalTh-El.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

39. Line 1566, Column 330: required attribute "alt" not specified

        …igital-download_52imgGalTh-vj.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

40. Line 1575, Column 330: required attribute "alt" not specified

        …igital-download_54imgGalTh-wA.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

41. Line 1584, Column 330: required attribute "alt" not specified

        …igital-download_56imgGalTh-di.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

42. Line 1593, Column 330: required attribute "alt" not specified

        …igital-download_50imgGalTh-zu.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

43. Line 1612, Column 330: required attribute "alt" not specified

        …igital-download_44imgGalTh-cB.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

44. Line 1621, Column 330: required attribute "alt" not specified

        …igital-download_46imgGalTh-lx.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

45. Line 1630, Column 330: required attribute "alt" not specified

        …igital-download_48imgGalTh-mO.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

46. Line 1639, Column 147: required attribute "alt" not specified

        …/44/96636619-10_04imgGalTh-ED.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

47. Line 1648, Column 147: required attribute "alt" not specified

        …/44/96636737-10_06imgGalTh-cW.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

48. Line 1657, Column 147: required attribute "alt" not specified

        …/44/96636841-10_08imgGalTh-ro.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

49. Line 1715, Column 140: cannot generate system identifier for general entity "utm_medium"

        …1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&ut

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

50. Line 1715, Column 140: general entity "utm_medium" not defined and no default entity

        …1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&ut

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

51. Line 1715, Column 150: reference not terminated by REFC delimiter

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

52. Line 1715, Column 150: reference to external entity in attribute value

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

53. Line 1715, Column 150: reference to entity "utm_medium" for which no system identifier could be generated

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

54. Line 1715, Column 138: entity was defined here

        …-p1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&

55. Line 1715, Column 159: cannot generate system identifier for general entity "utm_source"

        …=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=openingrn

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

56. Line 1715, Column 159: general entity "utm_source" not defined and no default entity

        …=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=openingrn

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

57. Line 1715, Column 169: reference not terminated by REFC delimiter

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

58. Line 1715, Column 169: reference to external entity in attribute value

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

59. Line 1715, Column 169: reference to entity "utm_source" for which no system identifier could be generated

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

60. Line 1715, Column 157: entity was defined here

        …gn=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=opening

61. Line 1715, Column 179: cannot generate system identifier for general entity "utm_content"

        …_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the Gam

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

62. Line 1715, Column 179: general entity "utm_content" not defined and no default entity

        …_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the Gam

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

63. Line 1715, Column 190: reference not terminated by REFC delimiter

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

64. Line 1715, Column 190: reference to external entity in attribute value

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

65. Line 1715, Column 190: reference to entity "utm_content" for which no system identifier could be generated

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

66. Line 1715, Column 177: entity was defined here

        …tm_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the G

67. Line 1715, Column 299: required attribute "alt" not specified

        …mepage-souvenirprogram_64d-hz.jpg" /></a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

68. Line 1740, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
69. Line 1740, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
70. Line 1812, Column 166: required attribute "alt" not specified

        …ideo--7---day-2_28imgGalTh-Jx.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

71. Line 1858, Column 147: required attribute "alt" not specified

        …--how-to-code-3_06imgGalTh-Ce.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

72. Line 1904, Column 167: required attribute "alt" not specified

        …-pt-1---podcast_08imgGalTh-bR.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

73. Line 1995, Column 107: required attribute "alt" not specified

        …0/09/57/culture_42imgGalTh-ch.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

74. Line 2031, Column 158: required attribute "alt" not specified

        …g/00/09/57/code_46imgGalTh-bA.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

75. Line 2076, Column 183: required attribute "alt" not specified

        …0/27/32/live-55_60imgGalTh-Zp.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

76. Line 2134, Column 353: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Vancouver 2010 </a><br /><a href="http:

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

77. Line 2134, Column 542: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Cultural Olympiad</a></div>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

78. Line 2135, Column 300: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Vancouver 2010</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

79. Line 2136, Column 148: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Torch Relay</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

80. Line 2137, Column 142: required attribute "alt" not specified

        …vertical-align:middle !important;" /> CODE 2010</a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

81. Line 2162, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
82. Line 2162, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
83. Line 2239, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
84. Line 2239, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    - You tried to include the "<" character in your page: you should escape it as "&lt;"
    - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    - Another possibility is that you forgot to close quotes in a previous tag.
85. Line 2264, Column 9: required attribute "type" not specified

        		<style>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

86. Line 2264, Column 9: document type does not allow element "style" here

        		<style>

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

87. Line 2272, Column 12: Attribute "name" exists, but can not be used for this element.

        <form name="#">

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

88. Line 2272, Column 15: required attribute "action" not specified

        <form name="#">

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

89. Line 2273, Column 172: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

        …lue) location.href = selectedValue;">

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

90. Line 2276, Column 71: cannot generate system identifier for general entity "cat1"

        …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

91. Line 2276, Column 71: general entity "cat1" not defined and no default entity

        …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

92. Line 2276, Column 75: reference not terminated by REFC delimiter

        …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

93. Line 2276, Column 75: reference to external entity in attribute value

        …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

94. Line 2276, Column 75: reference to entity "cat1" for which no system identifier could be generated

        …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

95. Line 2276, Column 69: entity was defined here

        …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

96. Line 2276, Column 83: cannot generate system identifier for general entity "q"

        …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

97. Line 2276, Column 83: general entity "q" not defined and no default entity

        …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

98. Line 2276, Column 84: reference not terminated by REFC delimiter

        …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

99. Line 2276, Column 84: reference to external entity in attribute value

        …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

100. Line 2276, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

101. Line 2276, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

102. Line 2276, Column 86: cannot generate system identifier for general entity "start"

         …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

103. Line 2276, Column 86: general entity "start" not defined and no default entity

         …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

104. Line 2276, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

105. Line 2276, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

106. Line 2276, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

107. Line 2276, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

108. Line 2277, Column 75: reference not terminated by REFC delimiter

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

109. Line 2277, Column 75: reference to external entity in attribute value

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

110. Line 2277, Column 75: reference to entity "cat1" for which no system identifier could be generated

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

111. Line 2276, Column 69: entity was defined here

         …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

112. Line 2277, Column 84: reference not terminated by REFC delimiter

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

113. Line 2277, Column 84: reference to external entity in attribute value

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

114. Line 2277, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

115. Line 2276, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

116. Line 2277, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

117. Line 2277, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

118. Line 2277, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

119. Line 2276, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

120. Line 2278, Column 75: reference not terminated by REFC delimiter

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

121. Line 2278, Column 75: reference to external entity in attribute value

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

122. Line 2278, Column 75: reference to entity "cat1" for which no system identifier could be generated

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

123. Line 2276, Column 69: entity was defined here

         …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

124. Line 2278, Column 84: reference not terminated by REFC delimiter

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

125. Line 2278, Column 84: reference to external entity in attribute value

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

126. Line 2278, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

127. Line 2276, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

128. Line 2278, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

129. Line 2278, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

130. Line 2278, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

131. Line 2276, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

132. Line 2338, Column 421: Attribute "target" exists, but can not be used for this element.

         …verse-weather_274552uH.html" target="_self">news release</a> for more informa

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

133. Line 2493, Column 15: required attribute "action" not specified

         <form name="#">

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for `type` are `type="text/css"` for `<style>` and `type="text/javascript"` for `<script>`.

134. Line 2494, Column 13: ID "drp_filter" already defined

         <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

135. Line 2273, Column 12: ID "drp_filter" first defined here

         <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

136. Line 2494, Column 231: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

         …h: 280px !important; color:#0076CC;">

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

137. Line 2496, Column 3: "DOCTYPE" declaration not allowed in instance

         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

138. Line 2497, Column 43: document type does not allow element "html" here

         <html xmlns="http://www.w3.org/1999/xhtml">

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

139. Line 2503, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Albania  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

140. Line 2504, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Albania  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

141. Line 2505, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Algeria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

142. Line 2506, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Algeria  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

143. Line 2507, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Andorra  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

144. Line 2508, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Andorra  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

145. Line 2509, Column 65: document type does not allow element "option" here

         …="http://www.ar.terra.com/deportes/vancouver2010/" >Argentina - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

146. Line 2510, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Armenia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

147. Line 2511, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Armenia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

148. Line 2512, Column 42: document type does not allow element "option" here

         <option value="http://www.nos.nl/os2010" >Aruba - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

149. Line 2513, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Aruba  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

150. Line 2514, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Aruba - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

151. Line 2515, Column 56: document type does not allow element "option" here

         <option value="http://www.foxtel.com.au/vancouver2010" >Australia - Foxtel</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

152. Line 2516, Column 49: document type does not allow element "option" here

         <option value="http://ninemsn.com.au/vancouver" >Australia - Nine</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

153. Line 2517, Column 48: document type does not allow element "option" here

         <option value="http://de.eurosport.yahoo.com " >Austria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

154. Line 2518, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Austria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

155. Line 2519, Column 37: document type does not allow element "option" here

         <option value="http://sport.orf.at" >Austria - ORF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

156. Line 2520, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Azerbaijan  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

157. Line 2521, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Azerbaijan  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

158. Line 2522, Column 44: document type does not allow element "option" here

         <option value="http://olimpicgames.tvr.by" >Belarus -TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

159. Line 2523, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Belarus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

160. Line 2524, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Belarus - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

161. Line 2525, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Belgium  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

162. Line 2526, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Belgium - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

163. Line 2527, Column 42: document type does not allow element "option" here

         <option value="http://www.rtbf.be/sport" >Belgium - RTBF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

164. Line 2528, Column 52: document type does not allow element "option" here

         <option value="http://www.sporza.be/vancouver2010" >Belgium - VRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

165. Line 2529, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Bosnia and Herzegovina</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

166. Line 2530, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Bosnia and Herzegovina - Eurovision</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

167. Line 2531, Column 60: document type does not allow element "option" here

         <option value="http://esportes.terra.com.br/vancouver2010" >Brazil - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

168. Line 2532, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >British Indian Ocean Territory</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

169. Line 2533, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >British Indian Ocean Territory  - Eurovi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

170. Line 2534, Column 38: document type does not allow element "option" here

         <option value="http://winter.bnt.bg" >Bulgaria - BNT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

171. Line 2535, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Bulgaria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

172. Line 2536, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Bulgaria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

173. Line 2537, Column 43: document type does not allow element "option" here

         <option value="http://www.ctvolympics.ca" >Canada - CTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

174. Line 2538, Column 45: document type does not allow element "option" here

         <option value="http://www.rdsolympiques.ca" >Canada - RDS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

175. Line 2539, Column 51: document type does not allow element "option" here

         <option value="http://www.rtve.es/vancouver-2010" >Canary Islands - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

176. Line 2540, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Canary Islands  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

177. Line 2541, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Canary Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

178. Line 2542, Column 65: document type does not allow element "option" here

         …="http://www.cl.terra.com/deportes/vancouver2010/" >Chile - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

179. Line 2543, Column 39: document type does not allow element "option" here

         <option value="http://sports.cntv.cn" >China, People's Republic of - CCTV</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

180. Line 2544, Column 57: document type does not allow element "option" here

         <option value="http://www.elta.tv/event/Vancouver2010/" >Chinese Taipei - ELTA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

181. Line 2545, Column 65: document type does not allow element "option" here

         …="http://www.co.terra.com/deportes/vancouver2010/" >Colombia - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

182. Line 2546, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Costa Rica - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

183. Line 2547, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Croatia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

184. Line 2548, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Croatia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

185. Line 2549, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Cyprus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

186. Line 2550, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Cyprus  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

187. Line 2551, Column 45: document type does not allow element "option" here

         <option value="http://www.ceskatelevize.cz" >Czech Republic - ceskatelevize</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

188. Line 2552, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Czech Republic  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

189. Line 2553, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Czech Republic - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

190. Line 2554, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Denmark  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

191. Line 2555, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Denmark - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

192. Line 2556, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Denmark - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

193. Line 2557, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Denmark - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

194. Line 2558, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Dominican Republic</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

195. Line 2559, Column 65: document type does not allow element "option" here

         …="http://www.ec.terra.com/deportes/vancouver2010/" >Ecuador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

196. Line 2560, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Egypt  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

197. Line 2561, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Egypt  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

198. Line 2562, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >El Salvador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

199. Line 2563, Column 39: document type does not allow element "option" here

         <option value="http://www.err.ee/om/" >Estonia - ERR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

200. Line 2564, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Estonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

201. Line 2565, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Estonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

202. Line 2566, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Falkland Islands (Malvinas)  - Eurosport

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

203. Line 2567, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Falkland Islands (Malvinas) - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

204. Line 2568, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Faroe Islands - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

205. Line 2569, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Faroe Islands - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

206. Line 2570, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Faroe Islands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

207. Line 2571, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Faroe Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

208. Line 2572, Column 31: document type does not allow element "option" here

         <option value="http://yle.fi" >Finland - YLE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

209. Line 2573, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Finland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

210. Line 2574, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Finland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

211. Line 2575, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >France - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

212. Line 2576, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.fr " >France - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

213. Line 2577, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >France - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

214. Line 2578, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Guyana - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

215. Line 2579, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >French Guyana - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

216. Line 2580, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >French Guyana - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

217. Line 2581, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Polynesia - France Télévisions</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

218. Line 2582, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >French Polynesia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

219. Line 2583, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >French Polynesia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

220. Line 2584, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Southern Territories  - France Té

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

221. Line 2585, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >French Southern Territories - Eurosport<

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

222. Line 2586, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >French Southern Territories - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

223. Line 2587, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Georgia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

224. Line 2588, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Georgia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

225. Line 2589, Column 48: document type does not allow element "option" here

         <option value="http://de.eurosport.yahoo.com " >Germany - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

226. Line 2590, Column 39: document type does not allow element "option" here

         <option value="http://olympia.ard.de" >Germany - ARD</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

227. Line 2591, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Germany - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

228. Line 2592, Column 39: document type does not allow element "option" here

         <option value="http://olympia.zdf.de" >Germany - ZDF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

229. Line 2593, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >Gibraltar - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

230. Line 2594, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Gibraltar - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

231. Line 2595, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Gibraltar - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

232. Line 2596, Column 56: document type does not allow element "option" here

         <option value="http://news.ert.gr/sports/olympics2010" >Greece - ERT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

233. Line 2597, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Greece - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

234. Line 2598, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Greece - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

235. Line 2599, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Greenland - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

236. Line 2600, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Greenland - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

237. Line 2601, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Greenland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

238. Line 2602, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Greenland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

239. Line 2603, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Guadeloupe - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

240. Line 2604, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Guadeloupe - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

241. Line 2605, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Guadeloupe - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

242. Line 2606, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Guatemala - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

243. Line 2607, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Honduras - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

244. Line 2608, Column 40: document type does not allow element "option" here

         <option value="http://www.i-cable.com" >Hong Kong - i-Cable</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

245. Line 2609, Column 43: document type does not allow element "option" here

         <option value="http://www.teliolimpia.hu" >Hungary - Magyar</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

246. Line 2610, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Hungary - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

247. Line 2611, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Hungary - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

248. Line 2612, Column 42: document type does not allow element "option" here

         <option value="http://www.ruv.is/ol2010" >Iceland - RUV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

249. Line 2613, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Iceland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

250. Line 2614, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Iceland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

251. Line 2615, Column 47: document type does not allow element "option" here

         <option value="http://uk.eurosport.yahoo.com" >Ireland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

252. Line 2616, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Ireland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

253. Line 2617, Column 45: document type does not allow element "option" here

         <option value="http://www.iba.org.il/sport" >Israel - IBA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

254. Line 2618, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Israel - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

255. Line 2619, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Israel - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

256. Line 2620, Column 49: document type does not allow element "option" here

         <option value="http://www.vancouver2010.rai.it" >Italy - Rai</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

257. Line 2621, Column 45: document type does not allow element "option" here

         <option value="http://www.sky.it/olimpiadi" >Italy - Sky Italia</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

258. Line 2622, Column 37: document type does not allow element "option" here

         <option value="http://www.gorin.jp" >Japan - Gorin</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

259. Line 2623, Column 47: document type does not allow element "option" here

         <option value="http://www.nhk.or.jp/olympic " >Japan - NHK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

260. Line 2624, Column 44: document type does not allow element "option" here

         <option value="http://www.nhk-ondemand.jp" >Japan - NHK On Demand</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

261. Line 2625, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Jordan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

262. Line 2626, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Jordan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

263. Line 2627, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Kazakhstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

264. Line 2628, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Kazakhstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

265. Line 2629, Column 42: document type does not allow element "option" here

         <option value="http://olympic.sbs.co.kr" >Korea - SBS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

266. Line 2630, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Kyrgyzstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

267. Line 2631, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Kyrgyzstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

268. Line 2632, Column 36: document type does not allow element "option" here

         <option value="http://www.ltv7.lv" >Latvia - LTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

269. Line 2633, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Latvia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

270. Line 2634, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Latvia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

271. Line 2635, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Lebanon - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

272. Line 2636, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Lebanon - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

273. Line 2637, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Libya - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

274. Line 2638, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Libya - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

275. Line 2639, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Liechtenstein - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

276. Line 2640, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Liechtenstein - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

277. Line 2641, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Lithuania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

278. Line 2642, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Lithuania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

279. Line 2643, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Luxembourg - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

280. Line 2644, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Luxembourg - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

281. Line 2645, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Macedonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

282. Line 2646, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Macedonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

283. Line 2647, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Madeira - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

284. Line 2648, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Madeira - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

285. Line 2649, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Malta - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

286. Line 2650, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Malta - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

287. Line 2651, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Martinique - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

288. Line 2652, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Martinique - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

289. Line 2653, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Martinique - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

290. Line 2654, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >Mayotte - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

291. Line 2655, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Mayotte - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

292. Line 2656, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Mayotte - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

293. Line 2657, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Mexico - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

294. Line 2658, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Moldova, Republic Of - Eurosport</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

295. Line 2659, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Moldova, Republic Of - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

296. Line 2660, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Monaco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

297. Line 2661, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Monaco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

298. Line 2662, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Montenegro - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

299. Line 2663, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Montenegro - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

300. Line 2664, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Morocco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

301. Line 2665, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Morroco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

302. Line 2666, Column 38: document type does not allow element "option" here

         <option value="http://nos.nl/os2010" >Netherlands - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

303. Line 2667, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Netherlands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

304. Line 2668, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Netherlands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

305. Line 2669, Column 42: document type does not allow element "option" here

         <option value="http://www.nos.nl/os2010" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

306. Line 2670, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

307. Line 2671, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Netherlands Antilles - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

308. Line 2672, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >New Caledonia - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

309. Line 2673, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >New Caledonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

310. Line 2674, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >New Caledonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

311. Line 2675, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Nicaragua - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

312. Line 2676, Column 38: document type does not allow element "option" here

         <option value="http://www.nrk.no/ol" >Norway - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

313. Line 2677, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Norway - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

314. Line 2678, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Norway - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

315. Line 2679, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Panama - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

316. Line 2680, Column 65: document type does not allow element "option" here

         …="http://www.pe.terra.com/deportes/vancouver2010/" >Peru - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

317. Line 2681, Column 45: document type does not allow element "option" here

         <option value="http://vancouver2010.tvp.pl" >Poland - TVP</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

318. Line 2682, Column 37: document type does not allow element "option" here

         <option value="http://eurosport.pl" >Poland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

319. Line 2683, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Poland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

320. Line 2684, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Portugal - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

321. Line 2685, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Portugal - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

322. Line 2686, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >Réunion - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

323. Line 2687, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Réunion - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

324. Line 2688, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Réunion - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

325. Line 2689, Column 43: document type does not allow element "option" here

         <option value="http://www.tvr.ro/Joiarna" >Romania - TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

326. Line 2690, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Romania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

327. Line 2691, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Romania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

328. Line 2692, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.ru " >Russia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

329. Line 2693, Column 41: document type does not allow element "option" here

         <option value="http://www.1tv.ru/olimp" >Russia - C1R</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

330. Line 2694, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Russia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

331. Line 2695, Column 57: document type does not allow element "option" here

         <option value="http://video.sportbox.ru/olimpiada 2010" >Russia - RTR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

332. Line 2696, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Saint Pierre And Miquelon - France Télév

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

333. Line 2697, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Saint Pierre And Miquelon - Eurosport</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

334. Line 2698, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Saint Pierre And Miquelon - Eurovision</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

335. Line 2699, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >San Marino - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

336. Line 2700, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >San Marino - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

337. Line 2701, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Serbia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

338. Line 2702, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Serbia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

339. Line 2703, Column 45: document type does not allow element "option" here

         <option value="http://www.stv.sk/vancouver" >Slovakia - STV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

340. Line 2704, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Slovakia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

341. Line 2705, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Slovakia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

342. Line 2706, Column 45: document type does not allow element "option" here

         <option value="http://www.rtvslo.si/oi2010" >Slovenia - RTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

343. Line 2707, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Slovenia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

344. Line 2708, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Slovenia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

345. Line 2709, Column 51: document type does not allow element "option" here

         <option value="http://www.rtve.es/vancouver-2010" >Spain - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

346. Line 2710, Column 48: document type does not allow element "option" here

         <option value="http://es.eurosport.yahoo.com " >Spain - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

347. Line 2711, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Spain - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

348. Line 2712, Column 41: document type does not allow element "option" here

         <option value="http://www.nrksport.net" >Spitsbergen - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

349. Line 2713, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Spitsbergen - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

350. Line 2714, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Spitsbergen - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

351. Line 2715, Column 38: document type does not allow element "option" here

         <option value="http://www.svt.se/os" >Sweden - SVT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

352. Line 2716, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.se " >Sweden - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

353. Line 2717, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Sweden - Eurovision </option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

354. Line 2718, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Switzerland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

355. Line 2719, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Switzerland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

356. Line 2720, Column 45: document type does not allow element "option" here

         <option value="http://www.rsi.ch/vancouver" >Switzerland - RSI</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

357. Line 2721, Column 44: document type does not allow element "option" here

         <option value="http://vancouver2010.sf.tv" >Switzerland - SF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

358. Line 2722, Column 54: document type does not allow element "option" here

         <option value="http://www.tsrsport.ch/vancouver2010" >Switzerland - TSR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

359. Line 2723, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Tajikistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

360. Line 2724, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Tajikistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

361. Line 2725, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >The Azores - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

362. Line 2726, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >The Azores - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

363. Line 2727, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Tunisia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

364. Line 2728, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Tunisia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

365. Line 2729, Column 39: document type does not allow element "option" here

         <option value="http://www.trt.net.tr" >Turkey - TRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

366. Line 2730, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Turkey - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

367. Line 2731, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Turkey - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

368. Line 2732, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Turkmenistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

369. Line 2733, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Turkmenistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

370. Line 2734, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Ukraine - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

371. Line 2735, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Ukraine - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

372. Line 2736, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >United Kingdom - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

373. Line 2737, Column 47: document type does not allow element "option" here

         <option value="http://uk.eurosport.yahoo.com" >United Kingdom - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

374. Line 2738, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >United Kingdom - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

375. Line 2739, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Uruguay - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

376. Line 2740, Column 44: document type does not allow element "option" here

         <option value="http://www.nbcolympics.com" >USA - NBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

377. Line 2741, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Uzbekistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

378. Line 2742, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Uzbekistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

379. Line 2743, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Vatican City State (Holy See) - Eurospor

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

380. Line 2744, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Vatican City State (Holy See) - Eurovisi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

381. Line 2745, Column 65: document type does not allow element "option" here

         …="http://www.ve.terra.com/deportes/vancouver2010/" >Venezuela - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

382. Line 2746, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >Virgin Islands, British</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

383. Line 2747, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Virgin Islands, British - Eurosport</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

384. Line 2748, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Virgin Islands, British - Eurovision</op

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

385. Line 2749, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Wallis And Futuna - France Télévisions</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

386. Line 2750, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Wallis And Futuna - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

387. Line 2751, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Wallis And Futuna - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

388. Line 2752, Column 9: end tag for "body" omitted, but OMITTAG NO was specified

         </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

389. Line 2502: start tag was here

         ><body>

390. Line 2752, Column 9: end tag for "html" omitted, but OMITTAG NO was specified

         </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

391. Line 2497: start tag was here

         ><html xmlns="http://www.w3.org/1999/xhtml">

392. Line 2826, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …nternational Olympic Committee" rel=nofollow><img src="/gfx/00/17/22/ioc_18d-

     ✉

393. Line 2827, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …apore Youth Olympic Games 2010" rel=nofollow><img src="/gfx/00/13/35/singapor

     ✉

394. Line 2828, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …et="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-2

     ✉

395. Line 2829, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …get="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-20

     ✉

396. Line 2830, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …arget="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18/99/rio2016_

     ✉

397. Line 2900, Column 5: document type does not allow element "ul" here; assuming missing "li" start-tag

          <ul><br />

     ✉

398. Line 2900, Column 11: document type does not allow element "br" here; assuming missing "li" start-tag

          <ul><br />

     ✉

399. Line 2902, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

          <li><a href="/more-2010-information/olympic-torch-relay/olympic-torch-relay-int

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

400. Line 2907, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

          <li><a href="/more-2010-information/olympic-torch-relay/about-the-olympic-torch

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

401. Line 2908, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

          </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

402. Line 2900, Column 5: start tag was here

          <ul><br />

403. Line 2908, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

          </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

404. Line 2900, Column 1: start tag was here

          <ul><br />

405. Line 2908, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

          </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

406. Line 2900, Column 1: start tag was here

          <ul><br />

407. Line 2908, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

          </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

408. Line 2896, Column 1: start tag was here

          <ul>

409. Line 2939, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

410. Line 2978, Column 36: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     - You tried to include the "<" character in your page: you should escape it as "&lt;"
     - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     - Another possibility is that you forgot to close quotes in a previous tag.
411. Line 2978, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     - You tried to include the "<" character in your page: you should escape it as "&lt;"
     - You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     - Another possibility is that you forgot to close quotes in a previous tag.
412. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

413. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

414. Line 244, Column 30: XML Parsing Error: AttValue: " or ' expected

         document.writeln('<style type=\"text/css\">');

     ✉

415. Line 244, Column 30: XML Parsing Error: attributes construct error

         document.writeln('<style type=\"text/css\">');

     ✉

416. Line 244, Column 30: XML Parsing Error: Couldn't find end of Start Tag style line 244

         document.writeln('<style type=\"text/css\">');

     ✉

417. Line 247, Column 26: XML Parsing Error: Opening and ending tag mismatch: script line 199 and style

         document.writeln('</style>');

     ✉

418. Line 248, Column 9: XML Parsing Error: Opening and ending tag mismatch: meta line 24 and script

         </script>

     ✉

419. Line 986, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

420. Line 986, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

421. Line 1097, Column 27: XML Parsing Error: AttValue: " or ' expected

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

422. Line 1097, Column 27: XML Parsing Error: attributes construct error

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

423. Line 1097, Column 27: XML Parsing Error: Couldn't find end of Start Tag div line 1097

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

424. Line 1097, Column 76: XML Parsing Error: AttValue: " or ' expected

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

425. Line 1097, Column 76: XML Parsing Error: attributes construct error

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

426. Line 1097, Column 76: XML Parsing Error: Couldn't find end of Start Tag div line 1097

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

427. Line 1113, Column 22: XML Parsing Error: Opening and ending tag mismatch: script line 1090 and div

         document.write("</div></div>");

     ✉

428. Line 1119, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 1033 and script

         </script>

     ✉

429. Line 1715, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

430. Line 1715, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

431. Line 1715, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

432. Line 1740, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

433. Line 1740, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

434. Line 2162, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

435. Line 2162, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

436. Line 2239, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

437. Line 2239, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

438. Line 2276, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Aler

     ✉

439. Line 2276, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

440. Line 2276, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

441. Line 2277, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Aler

     ✉

442. Line 2277, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

443. Line 2277, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

444. Line 2278, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</o

     ✉

445. Line 2278, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

446. Line 2278, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

447. Line 2496, Column 1: XML Parsing Error: StartTag: invalid element name

         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

448. Line 2752, Column 9: XML Parsing Error: Opening and ending tag mismatch: body line 2502 and select

         </select>

     ✉

449. Line 2753, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2497 and form

         </form>

     ✉

450. Line 2754, Column 6: XML Parsing Error: Opening and ending tag mismatch: select line 2494 and div

         </div>

     ✉

451. Line 2755, Column > 80: XML Parsing Error: Opening and ending tag mismatch: form line 2493 and div

         …line" src="/gfx/00/23/57/broadcaster2_00d-ku.jpg" /></div>…

     ✉

452. Line 2826, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

453. Line 2826, Column > 80: XML Parsing Error: attributes construct error

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

454. Line 2826, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 2826

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

455. Line 2826, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 2826 and a

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

456. Line 2826, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 2825 and li

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

457. Line 2827, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

458. Line 2827, Column > 80: XML Parsing Error: attributes construct error

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

459. Line 2827, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 2827

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

460. Line 2827, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 2827 and a

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

461. Line 2827, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 2823 and li

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

462. Line 2828, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

463. Line 2828, Column > 80: XML Parsing Error: attributes construct error

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

464. Line 2828, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 2828

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

465. Line 2828, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 2828 and a

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

466. Line 2828, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 2822 and li

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

467. Line 2829, Column 76: XML Parsing Error: AttValue: " or ' expected

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

468. Line 2829, Column 76: XML Parsing Error: attributes construct error

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

469. Line 2829, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 2829

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

470. Line 2829, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 2829 and a

         …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

471. Line 2829, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 2805 and li

         …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

472. Line 2830, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

473. Line 2830, Column > 80: XML Parsing Error: attributes construct error

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

474. Line 2830, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 2830

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

475. Line 2830, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 2830 and a

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

476. Line 2830, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 275 and li

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

477. Line 2831, Column 6: XML Parsing Error: Opening and ending tag mismatch: div line 274 and ul

          </ul>

     ✉

478. Line 2908, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 2900 and div

          </div>

     ✉

479. Line 2927, Column 8: XML Parsing Error: Opening and ending tag mismatch: ul line 2896 and div

         		</div><!-- end of refLine -->

     ✉

480. Line 2939, Column 58: XML Parsing Error: AttValue: " or ' expected

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

481. Line 2939, Column 58: XML Parsing Error: attributes construct error

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

482. Line 2939, Column 58: XML Parsing Error: Couldn't find end of Start Tag a line 2939

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

483. Line 2939, Column 74: XML Parsing Error: Opening and ending tag mismatch: li line 2939 and a

         …ss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

484. Line 2939, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 2931 and li

         … title="RSS" rel=nofollow>RSS</a></li>…

     ✉

485. Line 2940, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 2930 and ul

         </ul>

     ✉

486. Line 2947, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 263 and div

          </div>

     ✉

487. Line 2966, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and div

         	</div><!--end of wrapFooter-->

     ✉

488. Line 2977, Column 2: XML Parsing Error: Extra content at the end of the document

         		<script type="text/javascript">

     ✉

↑ Top