Minor futzing to test-plan.md

sideshowbarker · sideshowbarker · commit bae7d5b09cdb · 2017-07-14T12:40:38.000+09:00
diff --git a/test-plan.md b/test-plan.md
@@ -13,16 +13,16 @@ commit message an explanation why tests aren’t needed for the change.
 Typically, both the PR for a spec update and the PR for the associated tests will be merged
 around the same time. If the spec PR is approved but the tests PR needs more work, add the
 [`needs tests`](https://w3c.github.io/spec-labels.html) label to the spec PR. Or if the
-tests PR is approved but the spec PR hasn’t yet been approved, add the
+tests PR is approved but the spec PR hasn’t yet been OK’ed, add the
 [`status:needs-spec-decision`](https://github.com/w3c/web-platform-tests/issues?utf8=%E2%9C%93&q=label%3Astatus%3Aneeds-spec-decision%20)
 label to the tests PR.
 
 Note that a test change which doesn’t conform to the current spec source on the `master`
 branch should not be merged before the corresponding spec change is merged to `master`.
 
-If testing a particular change isn’t practical due to web-platforms-tests limitations,
+If testing a particular spec change isn’t practical due to web-platforms-tests limitations,
 explain why in the spec-PR commit message, file a
-[web-platform-tests issue](https://github.com/w3c/web-platform-tests/issues)
+[wpt issue](https://github.com/w3c/web-platform-tests/issues)
 describing the limitation, and add the
 [`type:untestable`](https://github.com/w3c/web-platform-tests/issues?utf8=%E2%9C%93&q=label%3Atype%3Auntestable%20)
 label to the issue.
