It's rather fine text, and when you save it as an image, it's alignment to the "pixel grid" may differ (from the same type/size text in similar images) by a fraction of a pixel.
Fonts have a built-in parameter called "hinting" which helps ensure that varying proximity to the pixel grid doesn't distort the glyphs of live type while they're displayed on-screen. It's a scientifically grizzly little property that dictates which portions of a glyph are always black, versus the portions that are subject to "anti-aliasing." When you rasterize the text as you have, it loses its hinting and becomes subject to "accident" in terms of pixel grid alignment, anti-aliasing, and subsequent perceptual rendering on-screen.
Considering the above, rasterizing text is somewhat of a crap-shoot and should be avoided. Your layouts could be composed with live text; and should be. Methods might differ depending on whether the end-product is an "email blast" or something that's always and only ever rendered in a browser.
Thank you for the reply.
What do you mean by "live text"...text within tables in html? And yes these webpages are composed first for email templates and second to remain on the website for later referral.
What do you mean by "live text"...text within tables in html?
Well, it doesn't have to be in tables, but yes...live, unconverted, edit-able, font-borne text (as opposed to rasterized or outlined pictures of text).
And yes these webpages are composed first for email templates...
Well, then you may be limited to table-based layouts, which does make it a bit more complex to incorporate live text. Can you say "nested tables"?