How many times have you paused and reflected, \u2018man, I know I am right, but the style guide does not agree\u2026\u2019? <\/p>\n
For example, some style guides proscribe the use of the possessive pronoun<\/strike> noun (earlier I had written ‘pronoun’. Thanks Guy for pointing it out.) and demand that you elaborate: IP address of the Server <\/b> as against Server\u2019s IP address <\/b>. In certain contexts I prefer the latter; for it is shorter and I am sure it won\u2019t confuse the users. But the style guide does not agree. <\/p>\n
I think that a style guide is by no means sacrosanct. It is around to help us, and not to put us in dilemmas. So, if you strongly believe that certain rules of the guide are rigid do share your opinion. A style guide evolves. It needs inputs from all concerned for it to become comprehensive, robust, and current. Do we need styled guides at all? Yes sir, product documentation needs to be consistent in terms of tone, style, and grammar. So, we need style guides. Also, when there is a team of writers working on the various modules of the product, a style guide helps in making the documentation coherent and consistent. Columbia guide to online writing<\/a><\/p>\n Lynch Guide<\/a><\/p>\n Write to me: Suman[at]techwritersindia[dot]com<\/p>\n
\n
You thoughts?
\n
Some style guides…<\/strong>
\n
The American Psychological Association (APA) Style<\/a><\/p>\n