Fix typo

Author: MarkJB

README.md

@@ -8,7 +8,7 @@ It was not intended to provide 100% test coverage, but was an exercise in starti
 
 I hit a few Gotchas that I remember hitting in the past like using async inside `.forEach` tests\*, or `map()` with other logic (Note: both `map()` and `[]forEach()` work fine if you are calling `test()` within it in a synchronous way (i.e. not calling it with async - see note below)).
 
-I originally stated "I should get used to using `for (const x of y) {}` for parametrized tests", but the Playwright documentation shows [].forEach(), and as long as I stick with what I said in the note below, `[]forEach()` should be fine.
+I originally stated "I should get used to using `for (const x of y) {}` for parametrized tests", but the Playwright documentation shows [].forEach(), and as long as I stick with what I said in the note below, `[].forEach()` should be fine.
 
 I looked into fixtures which I've not really done before - they are not like Pytest fixtures. They are more opaque and don't play nice with parametrized tests and `.use()` (Passing parametrized data to a fixture in a loop will override that data for all tests, and if they are running in parallel, its not going to end well).