style: pre-commit fixes

Author: pre-commit-ci[bot]

docs/pages/principles/testing.md

@@ -11,11 +11,11 @@ parent: Principles
 # Testing recommendations
 
 ## Outside-In Tests
-* live outside of source code, in the tests/ directory
-* Describe the various types of outsid-in tests (integration, fuzz, e2e, API)
-* Reference topical guides
-* Provide suggestions for testing categories
 
+- live outside of source code, in the tests/ directory
+- Describe the various types of outsid-in tests (integration, fuzz, e2e, API)
+- Reference topical guides
+- Provide suggestions for testing categories
 
 ## Unit Tests
 
@@ -228,8 +228,8 @@ troubleshoot problems.
 ### Guidelines for Diagnostic Tests
 
 - Consider using the stdlib `unittest.TestCase` and other stdlib tools instead
-  of pytest. To allow running unit tests for diagnostics in production environments,
-  without installing additional packages.
+  of pytest. To allow running unit tests for diagnostics in production
+  environments, without installing additional packages.
 
 - Test files should be named `test_{{file under test}}.py`, so that stdlib
   unittest can find them easily.
@@ -263,4 +263,3 @@ stdlib's unittest can be used in environments where pytest is not available:
 - To use unittest to run tests in your source folder, from your package root,
   use
   `python -m unittest discover --start-folder {{source folder}} --top-level-directory .`
-