style: pre-commit fixes

Author: pre-commit-ci[bot]

docs/pages/principles/testing.md

@@ -99,10 +99,9 @@ guide]({% link pages/guides/pytest.md %}).
 
 ## Project Level Integration Testing
 
-The term "Integration Test" is
-unfortunately overloaded, and used to describe testing that various components
-integrate with each other, at many levels of the system. These tests will loosely
-follow the "Detroit School" of test design.
+The term "Integration Test" is unfortunately overloaded, and used to describe
+testing that various components integrate with each other, at many levels of the
+system. These tests will loosely follow the "Detroit School" of test design.
 
 - Write tests which view the code from an outside-in perspective, like
   [Public Interface]() tests
@@ -120,8 +119,8 @@ should be helpful for users of the package.
 
 ## Unit Tests
 
-Unit tests loosely follow the "London School" of testing, where the smallest unit
-of code is tested in isolation.
+Unit tests loosely follow the "London School" of testing, where the smallest
+unit of code is tested in isolation.
 
 These tests are written from an internal perspective, so they are a good place
 to test aspects of the codebase which are "private" not directly exposed to