It might be because you define the line-height repeatedly. My understanding of CSS, admittedly limited, is that if you define something in the container DIV then it will automatically be used in any nested DIVs which don't specify that parameter. So you don't need to specify it again in the paragraph parameter. I may be wrong though!

The people at CSS forums were helpful to me this afternoon, so you could ask there...

Well, it would help if you took the "margin-bottom:10px" out of your ".content p" section in your style tag, but the problem isn't with your style sheet; it's that in the entries with the long spaces, you have both a p (unclosed) and a br tag between paragraphs. Methinks it's probably something having to do with whatever post-editor thing that Movable Type uses (I'm trying to work up the courage to go to movable type with my blog. I'm a leetle scared still though). Does it have a setting to format hard returns as either double or single line breaks? You might check that, and change it to suit yourself. Note that this entry doesn't have the extra blank lines; your source code shows this entry with only a p tag, and no br (and no line break), to separate the paragraphs. Not sure why without having a greater undertanding of how movable type works.

oh, cripes, underSTANDing. Can I claim the "it's late" excuse before eleven o'clock?

Rachel -- something you said made me realize the problem. I use ecto (a desktop client) to post movable type entries, and somehow or another the format setting had got changed to 'convert line breaks' which was adding in that extra break code.

You would have no problem with movable type, I'm absolutely sure you could handle it. And it's a wonderful way to procrastinate, fiddling with stylesheets and formatting and plugins and all that good stuff.

Mags-- I had a look at your site and followed some of the css links. Good stuff, thanks.

like feuding sisters at a family dinner.

I'm so jealous of this kind of simile. Can't do one to save my life. Love to read them.