docs: update command style

Author: kenjis

admin/module/tests/README.md

@@ -16,11 +16,15 @@ writing we are running version 8.5.13. Support for this has been built into the
 **composer.json** file that ships with CodeIgniter and can easily be installed
 via [Composer](https://getcomposer.org/) if you don't already have it installed globally.
 
-	> composer install
+```console
+> composer install
+```
 
 If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer.
 
-	> ln -s ./vendor/bin/phpunit ./phpunit
+```console
+> ln -s ./vendor/bin/phpunit ./phpunit
+```
 
 You also need to install [XDebug](https://xdebug.org/index.php) in order
 for code coverage to be calculated successfully.
@@ -37,19 +41,26 @@ on your machine. More details on a test database setup are in the
 
 The entire test suite can be run by simply typing one command-line command from the main directory.
 
-	> ./phpunit
+```console
+> ./phpunit
+```
 
 You can limit tests to those within a single test directory by specifying the
 directory name after phpunit.
 
-	> ./phpunit app/Models
+```console
+> ./phpunit app/Models
+```
 
 ## Generating Code Coverage
 
 To generate coverage information, including HTML reports you can view in your browser,
 you can use the following command:
 
 	> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```console
+> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```
 
 This runs all of the tests again collecting information about how many lines,
 functions, and files are tested. It also reports the percentage of the code that is covered by tests.

admin/starter/tests/README.md

@@ -17,11 +17,15 @@ writing we are running version 9.x. Support for this has been built into the
 **composer.json** file that ships with CodeIgniter and can easily be installed
 via [Composer](https://getcomposer.org/) if you don't already have it installed globally.
 
-	> composer install
+```console
+> composer install
+```
 
 If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer.
 
-	> ln -s ./vendor/bin/phpunit ./phpunit
+```console
+> ln -s ./vendor/bin/phpunit ./phpunit
+```
 
 You also need to install [XDebug](https://xdebug.org/index.php) in order
 for code coverage to be calculated successfully.
@@ -43,23 +47,31 @@ the tests run quite a bit faster.
 
 The entire test suite can be run by simply typing one command-line command from the main directory.
 
-	> ./phpunit
+```console
+> ./phpunit
+```
 
 If you are using Windows, use the following command.
 
-	> vendor\bin\phpunit
+```console
+> vendor\bin\phpunit
+```
 
 You can limit tests to those within a single test directory by specifying the
 directory name after phpunit.
 
-	> ./phpunit app/Models
+```console
+> ./phpunit app/Models
+```
 
 ## Generating Code Coverage
 
 To generate coverage information, including HTML reports you can view in your browser,
 you can use the following command:
 
-	> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```console
+> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```
 
 This runs all of the tests again collecting information about how many lines,
 functions, and files are tested. It also reports the percentage of the code that is covered by tests.

tests/README.md

@@ -12,11 +12,15 @@ writing we are running version 9.x. Support for this has been built into the
 **composer.json** file that ships with CodeIgniter and can easily be installed
 via [Composer](https://getcomposer.org/) if you don't already have it installed globally.
 
-	> composer install
+```console
+> composer install
+```
 
 If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer.
 
-	> ln -s ./vendor/bin/phpunit ./phpunit
+```console
+> ln -s ./vendor/bin/phpunit ./phpunit
+```
 
 You also need to install [XDebug](https://xdebug.org/docs/install) in order
 for code coverage to be calculated successfully. After installing `XDebug`, you must add `xdebug.mode=coverage` in the **php.ini** file to enable code coverage.
@@ -38,31 +42,43 @@ the tests run quite a bit faster.
 
 The entire test suite can be run by simply typing one command-line command from the main directory.
 
-	> ./phpunit
+```console
+> ./phpunit
+```
 
 If you are using Windows, use the following command.
 
-	> vendor\bin\phpunit
+```console
+> vendor\bin\phpunit
+```
 
 You can limit tests to those within a single test directory by specifying the
 directory name after phpunit. All core tests are stored under **tests/system**.
 
-	> ./phpunit tests/system/HTTP/
+```console
+> ./phpunit tests/system/HTTP/
+```
 
 Individual tests can be run by including the relative path to the test file.
 
-	> ./phpunit tests/system/HTTP/RequestTest.php
+```console
+> ./phpunit tests/system/HTTP/RequestTest.php
+```
 
 You can run the tests without running the live database and the live cache tests.
 
-	> ./phpunit --exclude-group DatabaseLive,CacheLive
+```console
+> ./phpunit --exclude-group DatabaseLive,CacheLive
+```
 
 ## Generating Code Coverage
 
 To generate coverage information, including HTML reports you can view in your browser,
 you can use the following command:
 
-	> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```console
+> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m
+```
 
 This runs all of the tests again collecting information about how many lines,
 functions, and files are tested. It also reports the percentage of the code that is covered by tests.