Apply suggestion from @rosieyohannan

Author: rosieyohannan

docs/guides/modules/test/pages/adaptive-testing.adoc

@@ -29,7 +29,7 @@ TIP: In codebases with sparse test coverage, adaptive testing cannot accurately
 == Limitations
 
 * Generating code coverage data is essential for determining how tests are related to code. If tests are run in a way that makes generating and accessing code coverage data tricky then adaptive testing may not be a good fit.
-* Adaptive testing works best when testing a single deployable artifact. For example, a monorepo with integration tests that span multiple packages/services—especially when services run in separate container—makes coverage generation and consolidation difficult.
+* Adaptive testing works best when testing a single deployable artifact. For example, a monorepo with integration tests that span multiple packages/services, especially when services run in separate container, makes coverage generation and consolidation difficult.
 * Adaptive testing needs to be configured with commands to discover all available tests and run a subset of those tests. If you cannot run commands to discover tests and run a subset of tests on the CLI then adaptive testing may not be a good fit.
 
 == Key benefits