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

https://wiki.civicrm.org/confluence/display/CRMDOC/Extending+Smarty

https://wiki.civicrm.org/confluence/display/CRMDOC/Customize+Built-in+Profile+Contribution+and+Event+Registration+Screens

https://wiki.civicrm.org/confluence/display/CRMDOC/Backbone+Reference

https://wiki.civicrm.org/confluence/display/CRMDOC/Transaction+Reference

https://github.com/civicrm/civicrm-core/blob/master/.github/CONTRIBUTING.md

https://wiki.civicrm.org/confluence/display/CRMDOC/Manual+testing

Why? Because right now there's where lots of other content exists which
is pretty similar to this page. And there's no "reference" chapter. I
think that once we're finished with the wiki migration we might like to
clean up that "framework" chapter a bit by moving some pages around. But
until then, I think it's easiest if we keep content together which is
similar.

Issue 92 Rename API Paramaters to API Options and also port in Custom Data Documentation to help with Issue 92