Currently we have 'All Hooks' followed by each of the categories of hooks
so it looks like 'Setup' is a hook category.  Its content is closer to 'Using Hooks'

These documents are misleading -- they talk about CiviMail because, *historically*,
much of this grew out of CiviMail. However, *today*, tokens are used more generally.
Also, in `civicrm-core`, `TokenProcessor` is *not* used by CiviMail. (You have to
install FlexMailer to use it.)

style guide ref:
https://docs.civicrm.org/dev/en/latest/documentation/style-guide/#hackable-urls

I'd like to be able to merge the general, incremental improvements for the
"Testing" section, but these two new pages aren't yet written.  Comment them
out.

1. Add new entries for Protractor, Codeception, and QUnit

2.  This menu includes (a) some pages about the overall testing process and
(b) some pages about specific tools.  Consistently put the general before
the specific.

There are multiple tools for testing in JS. We'll want separate pages for each.

related:
https://github.com/civicrm/civicrm-user-guide/pull/232

Resolve #316

Per discussion of https://github.com/civicrm/civicrm-dev-docs/pull/434

When scanning the navbar, there are several words which (IMHO) aren't adding
much value.  This simplifies and should make it easier to navigate.

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

Broaden the "Coding Standards" chapter to "Development Standards" to
better encompass "Review Standards" as a page.

Replace 'Wordpress' with 'WordPress' to use correct camel casing according to the WordPress Wordmark and Trademark

Typo

ref:
https://docs.civicrm.org/dev/en/latest/documentation/style-guide/#describing-the-civicrm-user-interface

https://wiki.civicrm.org/confluence/display/CRMDOC/Verify+a+bug+fix