Create E2E tests for nomination pools

README.md

@@ -79,7 +79,7 @@ Initial coverage can be limited to critical path scenarios composed of common ex
 from each of a runtime's pallets, and from there test more complex interactions.
 
 Note that since block execution throughput in `chopsticks` on a local development machine is limited
-to roughly `1` and `10` blocks/second, not all scenarios are testable in practice e.g. referenda
+to roughly `1-10` blocks/second, not all scenarios are testable in practice e.g. referenda
 confirmation, or the unbonding of staked funds.
 Consider placing such tests elsewhere, or using different tools (e.g. XCM emulator).
 
@@ -109,7 +109,7 @@ Consider placing such tests elsewhere, or using different tools (e.g. XCM emulat
 3. Run the newly created tests so their snapshots can be created in `packages/<network>/src/__snapshots__`
   - Inspect the snapshots, and make corrections to tests as necessary - or upstream, if the test
     has revealed an issue with e.g. `polkadot-sdk`
-4. Craete a PR with the new tests.
+4. Create a PR with the new tests.
 
 ### Writing Tests