What's not so nice is seeing errors in posts, especially grammatical errors. My parents paid a pretty penny for my private school education and it seems I should be using it for some good purpose even now, even as a housewife. :)
When I go back to read, I admit I change the errors I find. Sometimes I even gasp when I find a mistake. You may be surprised to read my admission, I proofread each entry at least twice before posting. To find errors even after that amount of scrutiny is shameful (in my world).
When I find formatting errors, now that's just irritating. Formatting each blog post can be a bit of a pain. In order to have the posts appear as I'd like, I have to make several adjustments to the text and spacing.
When I've previewed a post to my satisfaction and later find odd spacing (as I did tonight on the Better Days entry) I get a little frustrated. When the post continues to retain blank lines in odd places within the content of my post no matter what I do, that frustration intensifies.
On the page where new posts are composed, I noticed a button I've never used before. It's an HTML button. I decided to click it to see what may be going on with my messed up entry. That's when I saw some underlying code that was placing blank lines in my post even when there were no blank lines in the composition.
What I was doing in tug-of-war fashion on the composition side for 15 minutes or more with no headway was resolved in 15 seconds or so on the HTML side. Thank the Lord for a Bellevue buddy who taught me some basics about HTML code a few years ago! Problem solved.
In hindsight, rereading previous posts for nostalgia's sake may not be the quirkiest thing you've read about me today ;) Hmm...
That photo rocks!
ReplyDelete