CS/markdownlint: code blocks should always specify language

When the code block contains plain text, use `text`.

Author: jrfnl

wiki/About-Standards-for-PHP_CodeSniffer.md

@@ -76,7 +76,7 @@ Once you have a good name:
 ```
 
 If your chosen standard name is `MyCompanyStandard`, the directory structure would now look like this:
-```
+```text
 - MyCompanyStandard (directory)
   - ruleset.xml (file)
 ```
@@ -124,7 +124,7 @@ Sniffs need to follow strict directory layout and naming conventions to allow fo
 A sniff MUST belong to a standard and MUST be in a category.
 
 The directory structure MUST be as follows:
-```
+```text
 [StandardName]/Sniffs/[CategoryName]/
 ```
 

wiki/Fixing-Errors-Automatically.md

@@ -54,7 +54,7 @@ patching file /path/to/code/file.php
 
 ## Using the PHP Code Beautifier and Fixer
 To automatically fix as many sniff violations as possible, use the `phpcbf` command in place of the `phpcs` command. While most of the PHPCS command line arguments can be used by PHPCBF, some are specific to reporting and will be ignored. Running PHPCBF with the `-h` or `--help` command line arguments will print a list of commands that PHPCBF will respond to. The output of `phpcbf -h` is shown below.
-```
+```text
 Usage:
   phpcbf [options] <file|directory>
 

wiki/Usage.md

@@ -13,7 +13,7 @@
 
 Running PHP_CodeSniffer with the `-h` or `--help` command line arguments will print a list of commands that PHP_CodeSniffer will respond to. The output of `phpcs -h` is shown below.
 
-```
+```text
 Usage:
   phpcs [options] <file|directory>
 
@@ -138,7 +138,7 @@ $ phpcs /path/to/code/myfile.inc /path/to/code/my_dir
 
 After PHP_CodeSniffer has finished processing your files, you will get an error report. The report lists both errors and warnings for all files that violated the coding standard. The output looks like this:
 
-```
+```bash
 $ phpcs /path/to/code/myfile.php
 
 FILE: /path/to/code/myfile.php
@@ -157,7 +157,7 @@ FOUND 5 ERROR(S) AND 1 WARNING(S) AFFECTING 5 LINE(S)
 
 If you don't want warnings included in the output, specify the `-n` command line argument.
 
-```
+```bash
 $ phpcs -n /path/to/code/myfile.php
 
 FILE: /path/to/code/myfile.php
@@ -179,7 +179,7 @@ FOUND 5 ERROR(S) AFFECTING 5 LINE(S)
 
 By default, PHP_CodeSniffer will print a complete list of all errors and warnings it finds. This list can become quite long, especially when checking a large number of files at once. To print a summary report that only shows the number of errors and warnings for each file, use the `--report=summary` command line argument. The output will look like this:
 
-```
+```bash
 $ phpcs --report=summary /path/to/code
 
 PHP CODE SNIFFER REPORT SUMMARY
@@ -196,7 +196,7 @@ A TOTAL OF 6 ERROR(S) AND 3 WARNING(S) WERE FOUND IN 3 FILE(S)
 
 As with the full report, you can suppress the printing of warnings with the `-n` command line argument.
 
-```
+```bash
 $ phpcs -n --report=summary /path/to/code
 
 PHP CODE SNIFFER REPORT SUMMARY
@@ -220,7 +220,7 @@ By default, PHP_CodeSniffer will run quietly, only printing the report of errors
 To enable progress reporting, use the `-p` command line argument.
 With progress output enabled, PHP_CodeSniffer will print a single-character status for each file being checked, like so:
 
-```
+```bash
 $ phpcs /path/to/code/CodeSniffer -p
 
 ...S........W.........S.....................................  60 / 110 (54%)
@@ -245,7 +245,7 @@ Legend for the progress indicators:
 
 With verbose output enabled, PHP_CodeSniffer will print the file that it is checking, show you how many tokens and lines the file contains, and let you know how long it took to process. The output will look like this:
 
-```
+```bash
 $ phpcs /path/to/code/CodeSniffer -v
 
 Registering sniffs in PEAR standard... DONE (28 sniffs registered)
@@ -292,7 +292,7 @@ $ phpcs --standard=PEAR,Squiz,/path/to/MyStandard /path/to/code/myfile.inc
 
 PHP_CodeSniffer can print you a list of the coding standards that are installed so that you can correctly specify a coding standard to use for testing. You can print this list by specifying the `-i` command line argument.
 
-```
+```bash
 $ phpcs -i
 The installed coding standards are MySource, PEAR, PSR1, PSR2, PSR12, Squiz and Zend
 ```
@@ -304,7 +304,7 @@ The installed coding standards are MySource, PEAR, PSR1, PSR2, PSR12, Squiz and
 
 PHP_CodeSniffer can print you a list of the sniffs that a coding standard includes by specifying the `-e` command line argument along with the `--standard` argument. This allows you to see what checks will be applied when you use a given standard.
 
-```
+```bash
 $ phpcs --standard=PSR1 -e
 
 The PSR1 standard contains 8 sniffs

wiki/Version-1.3.0-Upgrade-Guide.md

@@ -4,7 +4,7 @@ PHP_CodeSniffer version 1.3.0 contains an important backwards compatibility brea
 > If you have not created your own coding standard, you do not need to follow this guide. Users of PHP_CodeSniffer that use one of the built-in standards can continue to check their code as normal.
 
 This guide assumes your coding standard has the following directory structure:
-```
+```text
 MyStandard
 |_ MyStandardCodingStandard.php
 |_ Sniffs
@@ -18,7 +18,7 @@ The only thing we need to do to upgrade a custom coding standard is convert the
 ### The Basics
 
 The first thing you need to do is create a `ruleset.xml` file directly under your top-level directory. The name of the file must be `ruleset.xml`:
-```
+```bash
 touch MyStandard/ruleset.xml
 ```
 
@@ -63,7 +63,7 @@ These rules would be replicated in a `ruleset.xml` file like this:
 ```
 
 The two changes here are the use of the `rule` tag to include sniffs and standards, and also the way we reference an individual sniff. Instead of specifying the path to the sniff we instead specify the internal code that PHP_CodeSniffer gives it, which is based on the path. It's actually a pretty easy conversion. Just just drop the `Sniffs` directory, convert the slashes to periods and remove `Sniff.php` from the end. Here are some more examples to make sure it is clear.
-```
+```text
 BEFORE: Generic/Sniffs/VersionControl/SubversionPropertiesSniff.php
 AFTER:  Generic.VersionControl.SubversionProperties