style: pre-commit fixes

Author: pre-commit-ci[bot]

docs/pages/principles/testing.md

@@ -351,11 +351,11 @@ It is common practice to import and alias all of a library, such as
 `import numpy as np`. However, as we develop our unit tests, this can cause
 difficulty with mocking, and complicate refactoring.
 
-To patch out `numpy.sum` in your test, you either need to patch the _global_ numpy
-module, which can have unintended side-effects, or specifically patch numpy.sum
-within the module namespace, which can result in absurdly long namespace paths,
-and logical breaks in the path when we transition from the local module
-namespace into an imported dependency's namespace, like so:
+To patch out `numpy.sum` in your test, you either need to patch the _global_
+numpy module, which can have unintended side-effects, or specifically patch
+numpy.sum within the module namespace, which can result in absurdly long
+namespace paths, and logical breaks in the path when we transition from the
+local module namespace into an imported dependency's namespace, like so:
 
 ```python
 def test_func(mocker):
@@ -395,15 +395,14 @@ total = numeric_sum(some_numeric_values)
 
 We recommend using Pytest for running tests in your development environments. To
 run unit tests in your source folder, from your package root, use
-`pytest {path/to/source}`.
-To run tests from an installed package (outside of
+`pytest {path/to/source}`. To run tests from an installed package (outside of
 your source repository), use `pytest --pyargs {package name}`.
 
-You can set the default test path in `pyproject.toml`, see:
-[Configuring pytest]({% link pages/tutorials/test.md %}#configuring-pytest)
-
-We recommend configuring pytest to run ONLY your fastest, least demanding test suite by default.
+You can set the default test path in `pyproject.toml`, see: [Configuring
+pytest]({% link pages/tutorials/test.md %}#configuring-pytest)
 
+We recommend configuring pytest to run ONLY your fastest, least demanding test
+suite by default.
 
 #### Mocking and Patching to Isolate the code under test