Depending on how he has set up your skin it will most likely be in portal.ascx
have a look for this line of code
<link href="
skin.css" rel="stylesheet" type="text/css" />
It should be in the first couple of lines of the file - it is an invalid link reference since dnn actually handles the injection of the skin.css stylesheet into the finished site.
It is not breaking your site in any way - but it does cause a small an additional overhead as the browser attempts to file the file.
Basically it should not really be there in the skin - the whole line can be deleted - for your production site - keep a copy of the file with it left in though as it makes it easier to edit the skin in tools that know how to show the information display layout from the stylesheet
Next - look for:
<td nowrap="nowrap"><a class="more" href="
/Contact.aspx"><span> CONTACT </span></a></p></td>
it has a </p> near the end of the line that should not be there ...
<td nowrap="nowrap"><a class="more" href="
/Contact.aspx"><span> CONTACT </span></a></td>
Next - look for:
<td nowrap="nowrap"><a class="more" href="
/Directions.aspx"><span>DIRECTIONS</span></a></p></td>
same thing here remove </p>:
<td nowrap="nowrap"><a class="more" href="
/Directions.aspx"><span>DIRECTIONS</span></a></td>
I would have to say however, that while the skin does work apart from this - it is not in a totally suitable format for future development - it uses the old <table layout methodology for its layout, instead of using the more recommended css <div based layout system.
Its not breaking anything as such - but have a read of this article some time - it talks about how things should really be done.
http://www.hotdesign.com/seybold/
Westa