I recently took a class on writing technical documentation. While I enjoy writing as a hobby, I had never given a lot of thought to some of the technical aspects of writing until I completed some of the assignments in this class. In the following months, I began to study technical writing more, and tried to see how it might apply to other forms of writing, such as blog posts. I was really interested in how the tone of a story or article might affect readers. During my research, I came across this from the Google Technical Documentation Guide:
> Aim, in your documents, for a voice and tone that’s conversational, friendly, and respectful without being overly colloquial or frivolous; a voice that’s casual and natural and approachable, not pedantic or pushy. Try to sound like a knowledgeable friend who understands what the developer wants to do.
> Don’t try to write exactly the way you speak; you probably speak more colloquially and verbosely than you should write, at least for developer documentation. But aim for a conversational tone rather than a formal one.
> Don’t try to be super-entertaining, but also don’t aim for super-dry. Be human, let your personality show, be memorable; you can even be a little funny now and then. But remember that the primary purpose of the document is to provide information to someone who’s looking for it.
> Remember that many readers are not native speakers of English, and that many of them come from cultures different from yours, and that your document may be translated into other languages.
I completely agree with this, and have tried to achieve similar tones in both my technical documentation, as well as my blog posts. My question is, as a writer, is tone something you focus on while writing? And if so, what are your thoughts on it?
As a reader, is tone something you notice in a story? And if so, how does it affect how you read or feel about a story?