Update _posts/2025-04-22-test-classloading-rewrite.adoc

Co-authored-by: Max Rydahl Andersen <max.andersen@gmail.com>

Author: holly-cummins

_posts/2025-04-22-test-classloading-rewrite.adoc

@@ -45,7 +45,7 @@ In practice, there have been a few hiccups and we've discovered some edge cases
 
 === Things to watch out for
 
-- *Test order change*. As part of the rewrite, the execution order of some tests has swapped around. Of course, we all know tests should not depend on execution order if they don't set an order explicitly. However, it's easy to not notice that a test requires a certain order... until the order changes. We discovered some tests in our own suite that were sensitive to the execution order, and other people may make similar discoveries.
+- *Test order change*. A side effect of the rewrite is that the execution order of test can be different. Of course, we all know tests should not depend on execution order if they don't set an order explicitly. However, it's easy to not notice that a test requires a certain order... until the order changes. We discovered some tests in our own suite that were sensitive to the execution order, and other people may make similar discoveries.
 - *Test timing change*. We also discovered that the rewrite exposed some timing issues in tests. Because classloading is frontloaded at the beginning of the test run, rather than between test executions, there's less time for asynchronous operations to finish between tests. For example, there may no longer be time for external state to 'reset' before the next test starts. This might expose some heisenbugs in test suites.
 
 === Dropped support