begin experimenting with shared Authentication section
standardize document title: 1 line, Quickstart for <official-product-name>
begin standardizing Concepts section
standardize Concepts section: immediately after general intro; one-word title Concepts followed by one-line section intro: terms in alphabetical order; terms & definitions formatted per Rackspace Technical Documentation style; every Quickstart includes this section now
try use of term() markup for Concepts section
try term again, just using indented definition 1 line below
format all Concepts sections using term + indented definition
add final More Information section to all, offering links to more detailed doc & support resources
correct link to /developers/ forum
still trying to fix the link to the Community: /developers/default w no final /
standardize Authentication section: title, placement immediately after Concepts section, language introducing code sample
try better placement of bullets in Authentication section
try better placement of bullets in Authentication section
correct placement of bullets in Authentication section
add Use the API section above detailed examples; structure becomes title+intro, Concepts, Authentication, Use, More Info
standardize subsection titles: sentence-style capitalization; consistent heading level; singular noun (List server, not List servers); imperative verb (Delete server, not Deleting server). Standardize text introducing code samples: minimize prefatory (To, not If you want to); minimize pointer to sample (:, not follow the example below:)
improve formatting of POST in Authentication section
try deeper levels of subsection: =, -, ~
standardize 3 levels of subsection: =, -, ~.
Merge pull request #253 from rose-coste/master

standardize structure of 11 Quickstarts