fix: Update tuist cloud document (#6239)

docs/docs/cloud/selective-testing.md

@@ -28,11 +28,11 @@ For example, assuming the following dependency graph:
 | ---- | --- | ---- |
 | `tuist test` invocation | Runs the tests in `CoreTests`, `FeatureATests`, and `FeatureBTests` | The hashes of `FeatureATests`, `FeatureBTests` and `CoreTests` are persisted |
 | `FeatureA` is updated | The developer modifies the code of a target | Same as before |
-| `tuist test` invocation | Runs the tests in `FeatureBTests` because it hash has changed | The new hash of `FeatureBTests` is persisted |
+| `tuist test` invocation | Runs the tests in `FeatureATests` because it hash has changed | The new hash of `FeatureATests` is persisted |
 | `Core` is updated | The developer modifies the code of a target | Same as before |
 | `tuist test` invocation | Runs the tests in `CoreTests`, `FeatureATests`, and `FeatureBTests` | The new hash of `FeatureATests` `FeatureBTests`, and `CoreTests` are persisted |
 
 The combination of selective testing with binary caching can dramatically reduce the time it takes to run tests on your CI.
 
 > [!WARNING] MODULE VS FILE-LEVEL GRANULARITY
-> Due to the impossibility of detecting the in-code dependencies between tests and sources, the maximum granularity of selective testing is at the target level. Therefore, we recommend keeping your targets small and focused to maximize the benefits of selective testing.
+> Due to the impossibility of detecting the in-code dependencies between tests and sources, the maximum granularity of selective testing is at the target level. Therefore, we recommend keeping your targets small and focused to maximize the benefits of selective testing.