>I recommend using the tags twice, just to make sure the
>lists are all "closed".
>
>Repeat with a <B> tag, and any other tag you feel my be left
>open.
>
>I also search for <P> so I can get chunks from the entire
>article. Don't worry if you miss a <P> or two...
>
>I then paste them into my text file with all my other lines.
>
>Then I open the line file in a browser (make sure to save
>your one liner file as html so you can preview them) and
>look for any errors.
>
>I'll spend about a minute trying to fix an line, and if I
>can't I'll delete the line.
>
>If you have trouble with html, don't mess with full article
>pages for now and just stick to using the pheeds.com search
>results.

Here is another tip...

If you use Firefox (even just for development), I would suggest downloading the following Firefox "extension"...

HTML Validator (based on Tidy)
https://addons.mozilla.org/extensions/moreinfo.php?id=249

Simple select "View" -> "Page Source"

The built-in validator will flag any "iffy" HTML, and even suggest a fix