Doc tweaks

Author: MGatner

docs/COVERAGE.md

@@ -1,7 +1,7 @@
 # Code Coverage
 
->> Code coverage is a term used in software testing to describe how much program source
->> code is covered by a testing plan. -[TechnoPedia](https://www.techopedia.com/definition/22535/code-coverage)
+> Code coverage is a term used in software testing to describe how much program source
+> code is covered by a testing plan. -[TechnoPedia](https://www.techopedia.com/definition/22535/code-coverage)
 
 ## Overview
 
@@ -24,13 +24,13 @@ Common practice is to create a local copy of this file as **phpunit.xml** and ad
 sensitive or environment info (like database connections). Prevent **phpunit.xml** from
 being tracked in your repo by adding it to **.gitignore**.
 
->> PHPUnit will always use **phpunit.xml** before **phpunit.xml.dist**, if it is found.
+> PHPUnit will always use **phpunit.xml** before **phpunit.xml.dist**, if it is found.
 
 ### Exclusions
 
 In addition to the code source mentioned above, PHPUnit can be configured to exclude files
 that are not relevant to testing or would otherwise cause the coverage calculations to fail.
-**ci4-module-tests** provides a few files common to CodeIgniter 4 but you may need to add
+**ci4-module-tests** starts with a few files common to CodeIgniter 4 but you may need to add
 your own:
 ```
 	<exclude>
@@ -41,7 +41,9 @@ your own:
 
 ### Logging
 
-Another common change is adjusting the output location and format of the coverage reports:
+Output is available in a variety of formats (see the [Logging Section](https://phpunit.readthedocs.io/en/8.3/logging.html)
+of the PHPUnit Guide). You can adjust the default location and format of the reports by
+modifying the `<logging>` tag:
 ```
 	<logging>
 		<log type="coverage-html" target="build/logs/html"/>
@@ -54,8 +56,6 @@ Another common change is adjusting the output location and format of the coverag
 	</logging>
 ```
 
-To read more on logging and options see the
-[Loggin Section](https://phpunit.readthedocs.io/en/8.3/logging.html) of the PHPUnit Guide.
-
 For more information on using the PHPUnit XML file generally see the
-[Configuration Section](https://phpunit.readthedocs.io/en/8.3/configuration.html) of the guide.
+[Configuration Section](https://phpunit.readthedocs.io/en/8.3/configuration.html)
+of the guide.

docs/CREATING.md

@@ -8,7 +8,7 @@
 ## Test Cases
 
 Every test needs a *test case*, or class that your tests extend. CodeIgniter 4
-provides a few you may use directly:
+provides a few that you may use directly:
 * `CodeIgniter\Test\CIUnitTestCase` - for basic tests with no other service needs
 * `CodeIgniter\Test\CIDatabaseTestCase` - for tests that need database access
 
@@ -22,22 +22,25 @@ common to your test suites.
 ## Tests
 
 All tests go in the **tests/** directory. **ci-module-tests** provides two generic
-subfolders for you **unit** and **database** but feel free to make your own. Each test file
-is a class that extends a **Test Case** (see above) and contains methods for each individual
-test. These method names must start with the word "test" and should have descriptive names
+subfolders for you, **unit** and **database** - but feel free to make your own. Each test file
+is a class that extends a **Test Case** (see above) and contains methods for the individual
+tests. These method names must start with the word "test" and should have descriptive names
 for precisely what they are testing: `testUserCanModifyFile()` `testOutputColorMatchesInput()`
 `testIsLoggedInFailsWithInvalidUser()`
 
+Writing tests is an art, and there are many resources available to help learn how. Review
+the links above and always pay attention to your [Code Coverage](docs/COVERAGE.md).
+
 ### Database Tests
 
-**ci-module-tests** provides a examples for migrating, seeding, and testing against a mock
+**ci-module-tests** provides examples for migrating, seeding, and testing against a mock
 or live<sup>1</sup> database. The example files can be modified or replaced with your own:
 * **tests/_support/Database/Migrations/create_test_tables.php**
 * **tests/_support/Database/Seeds/ExampleSeeder.php**
 * **tests/_support/Models/ExampleModel.php**
 
 Be sure to modify the test case (or create your own) to point to your seed and migrations
-and include any additional steps in `setUp()`:
+and include any additional steps to be run before tests in the `setUp()` method:
 * **tests/_support/DatabaseTestCase.php**
 
 <sup>1</sup> Note: If you are using database tests that require a live database connection you will need
@@ -47,6 +50,7 @@ repo by adding it to **.gitignore**.
 
 ### Session Tests
 
-Similar to the database test case, **ci-module-tests** provides a test case pre-configured
-with the mock session class to make testing sessions easy:
+Similar to database testing, **ci-module-tests** provides a test case pre-configured
+with the [mock session class](https://codeigniter4.github.io/userguide/testing/overview.html#mocking-services)
+to make testing sessions easier:
 * **tests/_support/SessionTestCase.php**