- \n
- Spelling? Not too shabby. I think all the spelling errors had been caught by the time this proof was done.<\/li>\n
- Grammar? It was pretty clean on that front as well, with the exception of a few things that could go either way. For instance: they changed one brief passage from simple past tense to past perfect tense, to avoid some confusion.<\/li>\n
- Punctuation? Abysmal.<\/li>\n<\/ul>\n
And what’s worse, every punctuation error in the proof came straight out of the manuscript I submitted<\/em>. They didn’t change them, I guess because they thought I wanted them that way, but very soon I wanted to grit my teeth at my own inattention to detail.<\/p>\n
My main problem was hyphenating words that didn’t need hyphens, such as writing “pre-fabricated” where “prefabricated” is a perfectly good word, or “set-up” instead of “setup.” Not a tragedy, by any stretch, but what annoyed me most was that I had been inconsistent within the document itself<\/em> and used both versions here and there\u00a0— “de-briefing” in one spot, say, and “debriefing” in another — with no rhyme and certainly no reason.<\/p>\n
So, herewith I apologize to the editorial and production team at WordFire Press<\/a><\/strong> for not being more diligent in catching all those errors sooner.<\/p>\n
![\"Employee](\"https:\/\/c1.staticflickr.com\/1\/88\/235530615_0e35b4f282.jpg\")
<\/a>
\nPunctuation can be pretty important. (Image: “Employee Must ‘Wash Hands’,” by Sean Graham, on Flickr under Creative Commons.)<\/em><\/span><\/p>\nI suppose I could have kept silent about my punctuation problems. Once the errors were corrected, folks who hadn’t seen an advance reader copy wouldn’t know how inconsistent my punctuation was in the early going. But I thought it was better to come clean about it, by way of expressing my thankfulness for the opportunity to catch the problem in production. To me, it validates my choice to go with a small press instead of self-publishing<\/a>.<\/p>\n
Will the final product be perfect, in the sense of having no flaws? Of course not. But it will have fewer flaws than the version I just saw, and that’s what matters.<\/p>\n
And the good news is that this stage of the proofing is done, so now we press on. Wish us luck!<\/p>\n
___
\n*That line sparked a strange idea: To write a\u00a0song to that effect, along the lines of the old Schoolhouse Rock<\/em> number, “How a Bill Becomes a Law.”<\/p>\n![\"Facebook\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/facebook.png\" "\\"Share")
<\/a>![\"twitter\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" "\\"Share")
<\/a>![\"pinterest\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/pinterest.png\" "\\"Pin")
<\/a>![\"linkedin\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" "\\"Share")
<\/a>![\"mail\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" "\\"Share")
<\/a>by <\/span>![\"feather\"](\"https:\/\/www.grayrinehart.com\/blog\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/icon.png\")
<\/a>","protected":false},"excerpt":{"rendered":"… consistently, that is. File this under, “how a manuscript becomes a published novel.”* I spent the last week or so poring over the proof copy of Walking On the Sea of Clouds, and realized that I’m not as good at the mechanics of writing as I thought I was. \u2026 Continue reading