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

Co-authored-by: Rosie Yohannan <rosie@circleci.com>

Author: mseong6251

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

@@ -11,20 +11,19 @@ NOTE: This page is currently in development and will be updated as the feature i
 
 Use adaptive testing to run only tests that are impacted by code changes and evenly distribute tests across parallel execution nodes. Adaptive testing reduces test execution time while maintaining test confidence.
 
-== Where Adaptive Testing works well:
+== Use cases for adaptive testing
 
-=== Ideal use cases
-* Unit and integration tests that exercise code within the same repository
-* Projects with comprehensive test coverage - The more thorough your tests, the more precisely adaptive testing can identify which tests are impacted by changes
-* Test frameworks with built-in coverage support (Jest, pytest, Go test, Vitest) where generating coverage reports is straightforward
+* Unit and integration tests that exercise code within the same repository.
+* Projects with comprehensive test coverage. The more thorough your tests, the more precisely adaptive testing can identify which tests are impacted by changes.
+* Test frameworks with built-in coverage support (Jest, pytest, Go test, Vitest) where generating coverage reports is straightforward.
++
+TIP: In codebases with sparse test coverage, adaptive testing cannot accurately determine which tests cover changed code. This causes the system to run more tests, reducing the benefits of intelligent test selection.
 
-*Why coverage matters*: In codebases with sparse test coverage, adaptive testing cannot accurately determine which tests cover changed code. This causes the system to run more tests, reducing the benefits of intelligent test selection.
+== Limitations
 
-=== Current Constraints
 * 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 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.
 * Adaptive testing works best when testing a single deployable unit. A monorepo which performs integration tests across many packages at once may not be a good fit.
-
 == Key benefits:
 
 * Faster CI/CD pipelines through intelligent test selection.