Docs: tweak markdown for compliance with markdownlint

Author: jrfnl

CHANGELOG.md

@@ -1,4 +1,4 @@
-# Change Log for the PHPCSDevTools standard for PHP Codesniffer
+# Change Log for the PHPCSDevTools standard for PHP_CodeSniffer
 
 All notable changes to this project will be documented in this file.
 

README.md

@@ -1,5 +1,4 @@
-PHPCSDevTools for developers of PHP_CodeSniffer sniffs
-=====================================================
+# PHPCSDevTools for developers of PHP_CodeSniffer sniffs
 
 <div aria-hidden="true">
 
@@ -34,8 +33,7 @@ This is a set of tools to assist developers of sniffs for [PHP CodeSniffer](http
 * [License](#license)
 
 
-Installation
--------------------------------------------
+## Installation
 
 ### Composer Project-based Installation
 
@@ -72,8 +70,7 @@ Composer will automatically install dependencies and register the PHPCSDebug sta
    ```
 
 
-Features
-------------------------------
+## Features
 
 ### Checking whether all sniffs in a PHPCS standard are feature complete
 
@@ -94,7 +91,7 @@ php -f "path/to/PHPCSDevTools/bin/phpcs-check-feature-completeness"
 If all is good, you will see a `All # sniffs are accompanied by unit tests and documentation.` message.
 
 If there are files missing, you will see errors/warnings for each missing file, like so:
-```
+```text
 WARNING: Documentation missing for path/to/project/StandardName/Sniffs/Category/SniffNameSniff.php.
 ERROR: Unit tests missing for path/to/project/StandardName/Sniffs/Category/SniffNameSniff.php.
 ```
@@ -105,7 +102,7 @@ phpcs-check-feature-completeness ./StandardName
 ```
 
 #### Options
-```
+```text
 directories   One or more specific directories to examine.
               Defaults to the directory from which the script is run.
 -q, --quiet   Turn off warnings for missing documentation.
@@ -143,7 +140,7 @@ phpcs ./SniffNameUnitTest.inc --standard=YourStandard,PHPCSDebug --sniffs=YourSt
 ```
 
 The output will look something along the lines of:
-```
+```text
 Ptr | Ln | Col  | Cond | ( #) | Token Type                 | [len]: Content
 -------------------------------------------------------------------------
   0 | L1 | C  1 | CC 0 | ( 0) | T_OPEN_TAG                 | [  5]: <?php
@@ -174,7 +171,7 @@ Ptr | Ln | Col  | Cond | ( #) | Token Type                 | [len]: Content
  21 | L5 | C  6 | CC 0 | ( 0) | T_WHITESPACE               | [  0]:
 ```
 
-PHPCS itself can also display similar information using the `-vv` or `-vvv` verbosity flags, however, when using those, you will receive a *lot* more information than just the token list and, while useful for debugging PHPCS itself, the additional information is mostly just noise when developing a sniff.
+PHPCS itself can also display similar information using the `-vv` or `-vvv` verbosity flags, however, when using those, you will receive a _lot_ more information than just the token list and, while useful for debugging PHPCS itself, the additional information is mostly just noise when developing a sniff.
 
 ### Documentation XSD Validation
 
@@ -229,12 +226,12 @@ jobs:
 
 :point_right: You'll need to replace the `YourRuleset` within the command with the name of your ruleset (of course).
 
-Contributing
--------
+## Contributing
+
 Contributions to this project are welcome. Clone this repository, branch off from `develop`, make your changes, commit them and send in a pull request.
 
 If unsure whether the changes you are proposing would be welcome, open an issue first to discuss your proposal.
 
-License
--------
+## License
+
 This code is released under the [GNU Lesser General Public License (LGPLv3)](http://www.gnu.org/copyleft/lesser.html).