Update docs/rules/no-wait-for-snapshot.test.md

Co-authored-by: Gonzalo D'Elia <[email protected]>

Author: Gpx

docs/rules/no-wait-for-snapshot.test.md

@@ -7,7 +7,7 @@ Ensure that no calls to `toMatchSnapshot` are made from within a `waitFor` metho
 The `waitFor()` method runs in a timer loop. So it'll retry every n amount of time.
 If a snapshot is generated inside the wait condition, jest will generate one snapshot per loop.
 
-The problem then is the amount of loop ran until the condition is met will vary between different computers (or CI machines.) This leads to tests that will regenerate a lot of snapshots until the condition is match when devs run those tests locally updating the snapshots; e.g devs cannot run `jest -u` locally or it'll generate a lot of invalid snapshots who'll fail during CI.
+The problem then is the amount of loop ran until the condition is met will vary between different computers (or CI machines). This leads to tests that will regenerate a lot of snapshots until the condition is matched when devs run those tests locally updating the snapshots; e.g devs cannot run `jest -u` locally or it'll generate a lot of invalid snapshots who'll fail during CI.
 
 Note that this lint rule prevents from generating a snapshot from within any of the [async utility methods](https://testing-library.com/docs/dom-testing-library/api-async).