[Invalid] Markup Validation of http://spreadhiv.com/~mphillips/

Errors found while checking this document as XHTML 1.0 Transitional!

Result:	100 Errors, 97 warning(s)
Address:
Modified:	(undefined)
Server:	Microsoft-IIS/6.0
Size:	12220
Content-Type:	text/html
Encoding:	utf-8
Doctype:	XHTML 1.0 Transitional
Root Element:	html
Root Namespace:	http://www.w3.org/1999/xhtml

Result:

100 Errors, 97 warning(s)

Address:

Modified:

(undefined)

Server:

Microsoft-IIS/6.0

Size:

12220

Content-Type:

text/html

Encoding:

utf-8

Doctype:

XHTML 1.0 Transitional

Root Element:

html

Root Namespace:

http://www.w3.org/1999/xhtml

Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

Character Encoding mismatch!

The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation.

↑ Top

Validation Output: 100 Errors

Line 10, Column 18: Attribute "LANGUAGE" is not a valid attribute. Did you mean "language"?
```
<SCRIPT LANGUAGE='Javascript' SRC='/spreadhiv.com.js'></SCRIPT>
```
✉

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.
Line 10, Column 35: Attribute "SRC" is not a valid attribute. Did you mean "src"?
```
<SCRIPT LANGUAGE='Javascript' SRC='/spreadhiv.com.js'></SCRIPT>
```
✉

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.
Line 10, Column 54: element "SCRIPT" undefined. Did you mean "script"?
```
<SCRIPT LANGUAGE='Javascript' SRC='/spreadhiv.com.js'></SCRIPT>
```
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 11, Column 1806: cannot generate system identifier for general entity "cssid"
```
…0e5fd8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='defaul
```
✉

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 "&" (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 æ 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.
Line 11, Column 1806: general entity "cssid" not defined and no default entity
```
…0e5fd8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='defaul
```
✉

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.
Line 11, Column 1811: reference not terminated by REFC delimiter
```
…8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='default' ty
```
✉

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.
Line 11, Column 1811: reference to external entity in attribute value
```
…8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='default' ty
```
✉

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 '&'.
Line 11, Column 1811: reference to entity "cssid" for which no system identifier could be generated
```
…8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='default' ty
```
✉

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.

Line 11, Column 1804: entity was defined here

…230e5fd8%7cSrchBox%3aTextboxWidth%3d0&cssid=116' rel='stylesheet' title='defa

Line 94, Column 408: cannot generate system identifier for general entity "slt"
```
…T0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner"
```
✉

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 "&" (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 æ 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.
Line 94, Column 408: general entity "slt" not defined and no default entity
```
…T0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner"
```
✉

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.
Line 94, Column 411: reference not terminated by REFC delimiter
```
…O0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Sp
```
✉

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.
Line 94, Column 411: reference to external entity in attribute value
```
…O0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Sp
```
✉

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 '&'.
Line 94, Column 411: reference to entity "slt" for which no system identifier could be generated
```
…O0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Sp
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 414: cannot generate system identifier for general entity "slr"
```
…9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Sprea
```
✉

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 "&" (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 æ 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.
Line 94, Column 414: general entity "slr" not defined and no default entity
```
…9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Sprea
```
✉

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.
Line 94, Column 417: reference not terminated by REFC delimiter
```
…ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread H
```
✉

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.
Line 94, Column 417: reference to external entity in attribute value
```
…ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread H
```
✉

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 '&'.
Line 94, Column 417: reference to entity "slr" for which no system identifier could be generated
```
…ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread H
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 420: cannot generate system identifier for general entity "lpt"
```
…WFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread HIV<
```
✉

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 "&" (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 æ 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.
Line 94, Column 420: general entity "lpt" not defined and no default entity
```
…WFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread HIV<
```
✉

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.
Line 94, Column 423: reference not terminated by REFC delimiter
```
…IEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread HIV</sp
```
✉

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.
Line 94, Column 423: reference to external entity in attribute value
```
…IEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread HIV</sp
```
✉

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 '&'.
Line 94, Column 423: reference to entity "lpt" for which no system identifier could be generated
```
…IEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');">Spread HIV</sp
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 792: reference not terminated by REFC delimiter
```
…t%2cYT0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Sp
```
✉

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.
Line 94, Column 792: reference to external entity in attribute value
```
…t%2cYT0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Sp
```
✉

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 '&'.
Line 94, Column 792: reference to entity "slt" for which no system identifier could be generated
```
…t%2cYT0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Sp
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 798: reference not terminated by REFC delimiter
```
…0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread</
```
✉

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.
Line 94, Column 798: reference to external entity in attribute value
```
…0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread</
```
✉

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 '&'.
Line 94, Column 798: reference to entity "slr" for which no system identifier could be generated
```
…0xO0w9U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread</
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 804: reference not terminated by REFC delimiter
```
…U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread<
```
✉

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.
Line 94, Column 804: reference to external entity in attribute value
```
…U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread<
```
✉

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 '&'.
Line 94, Column 804: reference to entity "lpt" for which no system identifier could be generated
```
…U3ByZWFkO1I9MjtTPU0j&slt=1&slr=2&lpt=1');">Spread<
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 1193: reference not terminated by REFC delimiter
```
…ZXMgZm9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Ho
```
✉

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.
Line 94, Column 1193: reference to external entity in attribute value
```
…ZXMgZm9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Ho
```
✉

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 '&'.
Line 94, Column 1193: reference to entity "slt" for which no system identifier could be generated
```
…ZXMgZm9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Ho
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 1199: reference not terminated by REFC delimiter
```
…9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes Fo
```
✉

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.
Line 94, Column 1199: reference to external entity in attribute value
```
…9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes Fo
```
✉

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 '&'.
Line 94, Column 1199: reference to entity "slr" for which no system identifier could be generated
```
…9yIFNhbGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes Fo
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 1205: reference not terminated by REFC delimiter
```
…bGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes For Sale
```
✉

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.
Line 94, Column 1205: reference to external entity in attribute value
```
…bGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes For Sale
```
✉

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 '&'.
Line 94, Column 1205: reference to entity "lpt" for which no system identifier could be generated
```
…bGU7Uj0zO1M9byMtIzNn&slt=1&slr=3&lpt=1');">Homes For Sale
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 1594: reference not terminated by REFC delimiter
```
…QXBhcnRtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Ap
```
✉

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.
Line 94, Column 1594: reference to external entity in attribute value
```
…QXBhcnRtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Ap
```
✉

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 '&'.
Line 94, Column 1594: reference to entity "slt" for which no system identifier could be generated
```
…QXBhcnRtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Ap
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 1600: reference not terminated by REFC delimiter
```
…RtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartmen
```
✉

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.
Line 94, Column 1600: reference to external entity in attribute value
```
…RtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartmen
```
✉

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 '&'.
Line 94, Column 1600: reference to entity "slr" for which no system identifier could be generated
```
…RtZW50cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartmen
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 1606: reference not terminated by REFC delimiter
```
…cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartments</sp
```
✉

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.
Line 94, Column 1606: reference to external entity in attribute value
```
…cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartments</sp
```
✉

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 '&'.
Line 94, Column 1606: reference to entity "lpt" for which no system identifier could be generated
```
…cztSPTQ7Uz1vIy0jM2c.&slt=1&slr=4&lpt=1');">Apartments</sp
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 2004: reference not terminated by REFC delimiter
```
…IFNlcnZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Da
```
✉

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.
Line 94, Column 2004: reference to external entity in attribute value
```
…IFNlcnZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Da
```
✉

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 '&'.
Line 94, Column 2004: reference to entity "slt" for which no system identifier could be generated
```
…IFNlcnZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Da
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 2010: reference not terminated by REFC delimiter
```
…ZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating S
```
✉

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.
Line 94, Column 2010: reference to external entity in attribute value
```
…ZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating S
```
✉

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 '&'.
Line 94, Column 2010: reference to entity "slr" for which no system identifier could be generated
```
…ZpY2VzO1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating S
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 2016: reference not terminated by REFC delimiter
```
…O1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating Service
```
✉

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.
Line 94, Column 2016: reference to external entity in attribute value
```
…O1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating Service
```
✉

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 '&'.
Line 94, Column 2016: reference to entity "lpt" for which no system identifier could be generated
```
…O1I9NTtTPW8jLSMzZw..&slt=1&slr=5&lpt=1');">Dating Service
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 2406: reference not terminated by REFC delimiter
```
…Q2hhdCBSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Ch
```
✉

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.
Line 94, Column 2406: reference to external entity in attribute value
```
…Q2hhdCBSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Ch
```
✉

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 '&'.
Line 94, Column 2406: reference to entity "slt" for which no system identifier could be generated
```
…Q2hhdCBSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Ch
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 2412: reference not terminated by REFC delimiter
```
…BSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Roo
```
✉

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.
Line 94, Column 2412: reference to external entity in attribute value
```
…BSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Roo
```
✉

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 '&'.
Line 94, Column 2412: reference to entity "slr" for which no system identifier could be generated
```
…BSb29tcztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Roo
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 2418: reference not terminated by REFC delimiter
```
…cztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Rooms</sp
```
✉

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.
Line 94, Column 2418: reference to external entity in attribute value
```
…cztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Rooms</sp
```
✉

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 '&'.
Line 94, Column 2418: reference to entity "lpt" for which no system identifier could be generated
```
…cztSPTY7Uz1vIy0jM2c.&slt=1&slr=6&lpt=1');">Chat Rooms</sp
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 2816: reference not terminated by REFC delimiter
```
…ZSBUaWNrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Ai
```
✉

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.
Line 94, Column 2816: reference to external entity in attribute value
```
…ZSBUaWNrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Ai
```
✉

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 '&'.
Line 94, Column 2816: reference to entity "slt" for which no system identifier could be generated
```
…ZSBUaWNrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Ai
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 2822: reference not terminated by REFC delimiter
```
…NrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline 
```
✉

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.
Line 94, Column 2822: reference to external entity in attribute value
```
…NrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline 
```
✉

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 '&'.
Line 94, Column 2822: reference to entity "slr" for which no system identifier could be generated
```
…NrZXRzO1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline 
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 2828: reference not terminated by REFC delimiter
```
…O1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline Ticket
```
✉

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.
Line 94, Column 2828: reference to external entity in attribute value
```
…O1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline Ticket
```
✉

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 '&'.
Line 94, Column 2828: reference to entity "lpt" for which no system identifier could be generated
```
…O1I9NztTPW8jLSMzZw..&slt=1&slr=7&lpt=1');">Airline Ticket
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 3225: reference not terminated by REFC delimiter
```
…dmVsIEd1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Tr
```
✉

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.
Line 94, Column 3225: reference to external entity in attribute value
```
…dmVsIEd1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Tr
```
✉

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 '&'.
Line 94, Column 3225: reference to entity "slt" for which no system identifier could be generated
```
…dmVsIEd1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Tr
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 3231: reference not terminated by REFC delimiter
```
…d1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel G
```
✉

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.
Line 94, Column 3231: reference to external entity in attribute value
```
…d1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel G
```
✉

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 '&'.
Line 94, Column 3231: reference to entity "slr" for which no system identifier could be generated
```
…d1aWRlcztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel G
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 3237: reference not terminated by REFC delimiter
```
…cztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel Guides<
```
✉

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.
Line 94, Column 3237: reference to external entity in attribute value
```
…cztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel Guides<
```
✉

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 '&'.
Line 94, Column 3237: reference to entity "lpt" for which no system identifier could be generated
```
…cztSPTg7Uz1vIy0jM2c.&slt=1&slr=8&lpt=1');">Travel Guides<
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 3624: reference not terminated by REFC delimiter
```
…TGFzIFZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">La
```
✉

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.
Line 94, Column 3624: reference to external entity in attribute value
```
…TGFzIFZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">La
```
✉

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 '&'.
Line 94, Column 3624: reference to entity "slt" for which no system identifier could be generated
```
…TGFzIFZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">La
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 3630: reference not terminated by REFC delimiter
```
…ZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vega
```
✉

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.
Line 94, Column 3630: reference to external entity in attribute value
```
…ZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vega
```
✉

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 '&'.
Line 94, Column 3630: reference to entity "slr" for which no system identifier could be generated
```
…ZlZ2FzO1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vega
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 3636: reference not terminated by REFC delimiter
```
…O1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vegas</spa
```
✉

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.
Line 94, Column 3636: reference to external entity in attribute value
```
…O1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vegas</spa
```
✉

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 '&'.
Line 94, Column 3636: reference to entity "lpt" for which no system identifier could be generated
```
…O1I9OTtTPW8jLSMzZw..&slt=1&slr=9&lpt=1');">Las Vegas</spa
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 4012: reference not terminated by REFC delimiter
```
…O0w9SGF3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">H
```
✉

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.
Line 94, Column 4012: reference to external entity in attribute value
```
…O0w9SGF3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">H
```
✉

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 '&'.
Line 94, Column 4012: reference to entity "slt" for which no system identifier could be generated
```
…O0w9SGF3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">H
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 4018: reference not terminated by REFC delimiter
```
…F3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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.
Line 94, Column 4018: reference to external entity in attribute value
```
…F3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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 '&'.
Line 94, Column 4018: reference to entity "slr" for which no system identifier could be generated
```
…F3YWlpO1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 4025: reference not terminated by REFC delimiter
```
…1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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.
Line 94, Column 4025: reference to external entity in attribute value
```
…1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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 '&'.
Line 94, Column 4025: reference to entity "lpt" for which no system identifier could be generated
```
…1I9MTA7Uz1vIy0jM2c.&slt=1&slr=10&lpt=1');">Hawaii<
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 94, Column 4418: reference not terminated by REFC delimiter
```
…VXNlZCBDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">U
```
✉

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.
Line 94, Column 4418: reference to external entity in attribute value
```
…VXNlZCBDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">U
```
✉

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 '&'.
Line 94, Column 4418: reference to entity "slt" for which no system identifier could be generated
```
…VXNlZCBDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">U
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 94, Column 4424: reference not terminated by REFC delimiter
```
…BDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Ca
```
✉

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.
Line 94, Column 4424: reference to external entity in attribute value
```
…BDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Ca
```
✉

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 '&'.
Line 94, Column 4424: reference to entity "slr" for which no system identifier could be generated
```
…BDYXJzO1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Ca
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 94, Column 4431: reference not terminated by REFC delimiter
```
…1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Cars</spa
```
✉

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.
Line 94, Column 4431: reference to external entity in attribute value
```
…1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Cars</spa
```
✉

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 '&'.
Line 94, Column 4431: reference to entity "lpt" for which no system identifier could be generated
```
…1I9MTE7Uz1vIy0jM2c.&slt=1&slr=11&lpt=1');">Used Cars</spa
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 101, Column 123: required attribute "alt" not specified
```
…781_female_student.jpg" border="0" /></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>.
Line 141, Column 434: reference not terminated by REFC delimiter
```
…Y2Vzc29yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">C
```
✉

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.
Line 141, Column 434: reference to external entity in attribute value
```
…Y2Vzc29yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">C
```
✉

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 '&'.
Line 141, Column 434: reference to entity "slt" for which no system identifier could be generated
```
…Y2Vzc29yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">C
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 141, Column 440: reference not terminated by REFC delimiter
```
…9yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Acc
```
✉

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.
Line 141, Column 440: reference to external entity in attribute value
```
…9yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Acc
```
✉

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 '&'.
Line 141, Column 440: reference to entity "slr" for which no system identifier could be generated
```
…9yaWVzO1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Acc
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 141, Column 447: reference not terminated by REFC delimiter
```
…1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Accessorie
```
✉

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.
Line 141, Column 447: reference to external entity in attribute value
```
…1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Accessorie
```
✉

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 '&'.
Line 141, Column 447: reference to entity "lpt" for which no system identifier could be generated
```
…1I9MTI7Uz1vIy0jM2c.&slt=1&slr=12&lpt=1');">Car Accessorie
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 141, Column 863: reference not terminated by REFC delimiter
```
…ZXNzb3JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">C
```
✉

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.
Line 141, Column 863: reference to external entity in attribute value
```
…ZXNzb3JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">C
```
✉

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 '&'.
Line 141, Column 863: reference to entity "slt" for which no system identifier could be generated
```
…ZXNzb3JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">C
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 141, Column 869: reference not terminated by REFC delimiter
```
…JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellula
```
✉

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.
Line 141, Column 869: reference to external entity in attribute value
```
…JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellula
```
✉

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 '&'.
Line 141, Column 869: reference to entity "slr" for which no system identifier could be generated
```
…JpZXM7Uj0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellula
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 141, Column 876: reference not terminated by REFC delimiter
```
…j0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellular Acces
```
✉

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.
Line 141, Column 876: reference to external entity in attribute value
```
…j0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellular Acces
```
✉

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 '&'.
Line 141, Column 876: reference to entity "lpt" for which no system identifier could be generated
```
…j0xMztTPW8jLSMzZw..&slt=1&slr=13&lpt=1');">Cellular Acces
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 141, Column 1285: reference not terminated by REFC delimiter
```
…aG9uZSBEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">C
```
✉

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.
Line 141, Column 1285: reference to external entity in attribute value
```
…aG9uZSBEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">C
```
✉

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 '&'.
Line 141, Column 1285: reference to entity "slt" for which no system identifier could be generated
```
…aG9uZSBEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">C
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 141, Column 1291: reference not terminated by REFC delimiter
```
…BEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Ph
```
✉

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.
Line 141, Column 1291: reference to external entity in attribute value
```
…BEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Ph
```
✉

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 '&'.
Line 141, Column 1291: reference to entity "slr" for which no system identifier could be generated
```
…BEZWFscztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Ph
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 141, Column 1298: reference not terminated by REFC delimiter
```
…ztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Phone Dea
```
✉

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.
Line 141, Column 1298: reference to external entity in attribute value
```
…ztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Phone Dea
```
✉

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 '&'.
Line 141, Column 1298: reference to entity "lpt" for which no system identifier could be generated
```
…ztSPTE0O1M9byMtIzNn&slt=1&slr=14&lpt=1');">Cell Phone Dea
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 141, Column 1722: reference not terminated by REFC delimiter
```
…UmluZ3RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">D
```
✉

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.
Line 141, Column 1722: reference to external entity in attribute value
```
…UmluZ3RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">D
```
✉

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 '&'.
Line 141, Column 1722: reference to entity "slt" for which no system identifier could be generated
```
…UmluZ3RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">D
```
✉

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.

Line 94, Column 406: entity was defined here

…cYT0xO0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inne

Line 141, Column 1728: reference not terminated by REFC delimiter
```
…RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Downloa
```
✉

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.
Line 141, Column 1728: reference to external entity in attribute value
```
…RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Downloa
```
✉

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 '&'.
Line 141, Column 1728: reference to entity "slr" for which no system identifier could be generated
```
…RvbmVzO1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Downloa
```
✉

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.

Line 94, Column 412: entity was defined here

…0w9U3ByZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spr

Line 141, Column 1735: reference not terminated by REFC delimiter
```
…1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Download Ringt
```
✉

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.
Line 141, Column 1735: reference to external entity in attribute value
```
…1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Download Ringt
```
✉

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 '&'.
Line 141, Column 1735: reference to entity "lpt" for which no system identifier could be generated
```
…1I9MTU7Uz1vIy0jM2c.&slt=1&slr=15&lpt=1');">Download Ringt
```
✉

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.

Line 94, Column 418: entity was defined here

…yZWFkIEhJVjtSPTE7Uz1NIw..&slt=1&slr=1&lpt=1');"><span class="inner">Spread HI

Line 11, Column > 80: XML Parsing Error: EntityRef: expecting ';'

…ostingURL%3dhttp%3a%2f%2fi.nuseek.com%7cBdyStyl%3aPageBackgroundColor%3d%23ff…

✉