Update DD-0-Defining_Datocracy.adoc

[ernest-bruce]

in my opinion as a writer of technical documentation and other types of content, i believe in not capitalizing words willy nilly · capitalize proper names is the only easy·to·understand capitalization rule · in my opinion, whether a word starts a sentence or is part of a title is no reason to capitalize it; yes, this goes against the rules of gramar; the reason for most of those rules do not exist today and must not be followed

my rules:

• should capitalize book and article titles (authors and publishers set the actual name)
• capitalize the proper names of entities and products according to the owners desires (it is iPhone, not Iphone)
• do not capitalize terms that can be pluralized (decision not Decision)
• i hate that “legal” documents capitalize everything; seriously, why is User capitalized? we must not imitate wrong choices of people who lived in a very different world
• use underline, italics, or bold to emphasize terms, not capitalization

[ernest-bruce]

just like programmers or those in charge of their work come up with policies that specify how to indent code (or, is it Int number, or Int number, or Int * number?), we must specify “formatting rules” for Englich, a comically ambiguous, inexact, and difficult·to·understand language for native speakers, readers, and writers · let us not make life even more difficult for nonnative English readers and speakers, readers, and writers