If a reader has customized their interactive shell, their system could have
small discrepancies in shell notation.  It shouldn't matter 95% of the time,
and it's not critical to support those folks perfectly.  But it is nice.  So
let's just share the link to heighten awareness.

(Example: I usually do `export VAR=value`...  but in future docs, I'll try
to use `VAR=value; export VAR`.)

This is following-up on some comments from @ginkgomzd who found the
`bash-hackers.org` site and shared it on https://github.com/civicrm/civicrm-buildkit/pull/365

 * Simplify titles under "Common standards". (Use a noun-phrase instead of an imperative statement.)
 * Combine `r-ext`, `r-core` into r-technical. Add more details. Reference `#gotchas`.
 * Rename `r-read` to `r-code`
 * Rename `rg-schema` to `rg-upgrade`. Add more details.

To see actual examples of the coding style, you need to skim multiple blurbs
and click multiple links, and the eventual page shows very isolated
examples.

This revision adds a brief example so that a new contributor can get a
general sense of the layout immediately.

(Note: It's not possible for a brief example to show every edge-case, and we
shouldn't try -- that's why the commit also emphasizes the link into the
relevant examples from d.o docs.)

Specifically:

 * Alphabetize
 * Add general description

ref:
https://github.com/civicrm/civicrm-wordpress/pull/112

I'm not sure if this has only come about because of my ineptitude (i.e. whether an Entity would always have the same name as the extension), but I found that I couldn't find the files referred to because my Entity and my Extension had different names.

Would that be bad practice on my part? (it would be good to know as I'm very new to coding)

Either way, I think this may be more accurate... rest is up to you.

Cheers,
M.

GitLab doesn't allow spaces in the username.

This makes it easier to reference these things from other pages.

I've changed the link for contribution guidelines to an internal link within the guide (rather than an external link to GitHub that links back to the guide).

Not sure of the Petition Signature Pages URL - its not Event registration....