- General formatting improvements.
- Change  "Ubuntu 12.04 or 14.04" to "Ubuntu 12.04 or later" because the
  buildkit install script is clearly designed to work for later versions
  of Ubuntu.
- Relocate troubleshoot steps to after configuration steps (so the
  reader doesn't stop reading when they see "troubleshooting".
- Higlight post-installation steps.
- New instructions for manually ading webserver settings after running
  `amp config`.
- More troubleshooting help.

This was in the general "buildkit" page, and I think it fits better in
the specific "civibuild" page.

This is a direct copy-paste from one section of the guide to another,
without any edits. When someone is installing buildkit, these steps are
easy to miss if they're located in the civibuild file.

Add in Coding Standards Docs for PHP and SQL

- Use the GitLab repo instead of the GitHub one
- Provide more instructions for the step where you create a fork

Add info about AngularJS versions

Migration was done by Seamus. This commit simply adds the redirect

Fix example

debugging.md - Remove misleading link

The doc mentions the page "Administer => System Settings => Cleanup Caches and Update Paths" as a way to clear caches. This is half-true: it does clear `templates_c` and the `civicrm_cache` table, but there are other things that it doesn't touch. (Compare `CRM_Admin_form_Setting_UpdateConfigBackend::postProcess` with the `CRM_Core_Invoke::rebuildMenuAndCaches`.)

IMHO, `UpdateConfigBackend::postProcess` should be patched to just do a general system flush (`civicrm_api3('System', 'flush', array())`) -- but (for now) the page is misleading and we shouldn't direct people there.

Developer Community - Add registration links & instructions

Corrected hook definition.

Improve instructions for MySQL query logging

civibuild.md - Split settings section. Add civibuild.conf.

Add link page on PR reviewing

- Add details about how to do query logging to a table instead of a
  file.
- Put instructions into steps in chronological order.

We don't really need the two bulleted lists:
 * In context, the previous section should give hints about what this means.
 * If the context isn't clear enough, then the links provide more concrete description.

1.  The title for section `civicrm.settings.php; settings.php;
wp-config.php` is very long. Split the section -- a longer one
which discusses `civicrm.settings.php` in more depth, and a shorter
which discusses similar files briefly.

2.  Add a section for `civibuild.conf`.

Strict markdown standards for internal hyperlink URLs

Fixed misnamed hook

Run the following command to do so:
./bin/hook-summary.py