QA/Markdown CS: use consistent list styles

* Use the same list markers throughout each document.
* Use consistent sublist indentation: each level should be indented by four spaces.

Author: jrfnl

.github/CONTRIBUTING.md

@@ -6,19 +6,19 @@ Thank you for your interest in contributing to PHP_CodeSniffer!
 ## Table of Contents
 
 * [Reporting Bugs](#reporting-bugs)
-   - [Reporting Security Issues](#reporting-security-issues)
-   - [Support/Questions About Using PHP_CodeSniffer](#supportquestions-about-using-php_codesniffer)
+    * [Reporting Security Issues](#reporting-security-issues)
+    * [Support/Questions About Using PHP_CodeSniffer](#supportquestions-about-using-php_codesniffer)
 * [Contributing Without Writing Code](#contributing-without-writing-code)
-   - [Bug Triage](#bug-triage)
-   - [Testing Open Pull Requests](#testing-open-pull-requests)
-   - [Writing sniff documentation](#writing-sniff-documentation)
-   - [Other tasks](#other-tasks)
+    * [Bug Triage](#bug-triage)
+    * [Testing Open Pull Requests](#testing-open-pull-requests)
+    * [Writing sniff documentation](#writing-sniff-documentation)
+    * [Other tasks](#other-tasks)
 * [Contributing With Code](#contributing-with-code)
-   - [Requesting/Submitting New Features](#requestingsubmitting-new-features)
-   - [Getting started](#getting-started)
-   - [While working on a patch](#while-working-on-a-patch)
-   - [Writing tests](#writing-tests)
-   - [Submitting your pull request](#submitting-your-pull-request)
+    * [Requesting/Submitting New Features](#requestingsubmitting-new-features)
+    * [Getting started](#getting-started)
+    * [While working on a patch](#while-working-on-a-patch)
+    * [Writing tests](#writing-tests)
+    * [Submitting your pull request](#submitting-your-pull-request)
 * [Licensing](#licensing)
 
 
@@ -255,9 +255,9 @@ For example, for the sniff named `Generic.NamingConventions.ConstructorName`:
 * The sniff lives in the `src/Standards/Generic/Sniffs/NamingConventions/` directory.
 * The tests live in the `src/Standards/Generic/Tests/NamingConventions/` directory.
 * The tests consist of two files:
-    - `src/Standards/Generic/Tests/NamingConventions/ConstructorNameUnitTest.inc` which is the test _case_ file containing
+    * `src/Standards/Generic/Tests/NamingConventions/ConstructorNameUnitTest.inc` which is the test _case_ file containing
        code for the sniff to analyse.
-    - `src/Standards/Generic/Tests/NamingConventions/ConstructorNameUnitTest.php` which is the test file, containing two methods,
+    * `src/Standards/Generic/Tests/NamingConventions/ConstructorNameUnitTest.php` which is the test file, containing two methods,
         `getErrorList()` and `getWarningList()`, which should each return an array with as the keys the line number
         in the test _case_ file and as the values the number of errors or warnings which are expected on each line.
         Only lines on which errors/warnings are expected need to be included in the lists. All other lines will automatically

CHANGELOG.md

@@ -2457,9 +2457,9 @@ Additionally, thanks to [Alexander Turek][@derrabus] for consulting on the repo
 - This release includes a change to support newer versions of PHPUnit (versions 4, 5, and 6 are now supported)
     - The custom PHP_CodeSniffer test runner now requires a bootstrap file
     - Developers with custom standards using the PHP_CodeSniffer test runner will need to do one of the following:
-      - run your unit tests from the PHP_CodeSniffer root dir so the bootstrap file is included
-      - specify the PHP_CodeSniffer bootstrap file on the command line: phpunit --bootstrap=/path/to/phpcs/tests/bootstrap.php
-      - require the PHP_CodeSniffer bootstrap file from your own bootstrap file
+        - run your unit tests from the PHP_CodeSniffer root dir so the bootstrap file is included
+        - specify the PHP_CodeSniffer bootstrap file on the command line: phpunit --bootstrap=/path/to/phpcs/tests/bootstrap.php
+        - require the PHP_CodeSniffer bootstrap file from your own bootstrap file
     - If you don't run PHP_CodeSniffer unit tests, this change will not affect you
     - Thanks to [Juliette Reinders Folmer][@jrfnl] for the patch
 - A phpcs.xml or phpcs.xml.dist file now takes precedence over the default_standard config setting
@@ -3179,7 +3179,7 @@ Additionally, thanks to [Alexander Turek][@derrabus] for consulting on the repo
 - Improved the formatting of the end brace when auto fixing InlineControlStructure errors (request [#1121][sq-1121])
 - Generic.Functions.OpeningFunctionBraceKernighanRitchie.BraceOnNewLine fix no longer leaves blank line after brace (request [#1085][sq-1085])
 - Generic UpperCaseConstantNameSniff now allows lowercase namespaces in constant definitions
-  - Thanks to [Daniel Schniepp][@dschniepp] for the patch
+    - Thanks to [Daniel Schniepp][@dschniepp] for the patch
 - Squiz DoubleQuoteUsageSniff is now more tolerant of syntax errors caused by mismatched string tokens
 - A few sniffs that produce errors based on the current PHP version can now be told to run using a specific PHP version
     - Set the php_version config var using --config-set, --runtime-set, or in a ruleset to specify a specific PHP version