There are "rules" to remember when it comes to writing.
Style guides are often useful resources as they can help writers avoid making decisions about the same issue repeatedly, provide assistance on how to best structure everything, and perhaps most importantly, keep everything consistent.
While it's important to have a style guide for your enterprise, a good foundation/starting point has just been released by Google in their
Developer Documentation style guide
The guide is used to "codify and record decisions" that Google's Developer Relations group makes about style. While it does not apply to all Google documentation and is not meant to provide any industry standard, but it does provide some insights into the language and style that the company prefers (which may extend to other areas)
The style guide provides information on general principles, language and grammar, punctuation, formatting and organization, the use of HTML and CSS, naming conventions and more.