fix planned assertion docs - fixes #140

readme.md

@@ -148,7 +148,7 @@ test(function name(t) {
 
 ### Planned assertions
 
-Planned assertions are useful for being able to assert that all async actions happened and catch bugs where too many assertions happen. It also comes with the benefit of not having to manually end the test.
+Planned assertions are useful for being able to assert that all async actions happened. It also comes with the benefit of not having to manually end the test.
 
 This will result in a passed test:
 
@@ -162,20 +162,6 @@ test(t => {
 });
 ```
 
-And this will result in an error because the code called more assertions than planned:
-
-```js
-test(t => {
-	t.plan(1);
-
-	t.pass();
-
-	setTimeout(() => {
-		t.pass();
-	}, 100);
-});
-```
-
 ### Serial test execution
 
 While concurrency is awesome, there are some things that can't be done concurrently. In these rare cases, you can call `test.serial`, which will force those tests to run serially before the concurrent ones.