Remove documentation about "pub run test:test".

README.md

 `test` provides a standard way of writing and running tests in Dart.
 
 * [Writing Tests](#writing-tests)
 * [Running Tests](#running-tests)
   * [Restricting Tests to Certain Platforms](#restricting-tests-to-certain-platforms)
   * [Platform Selectors](#platform-selectors)
   * [Running Tests on Dartium](#running-tests-on-dartium)
 * [Asynchronous Tests](#asynchronous-tests)
 * [Running Tests With Custom HTML](#running-tests-with-custom-html)
 * [Configuring Tests](#configuring-tests)
@@ skipping 106 matching lines @@
 
   // ...
 }
 ```
 
 [setUp]: http://www.dartdocs.org/documentation/test/latest/index.html#test/test@id_setUp
 [tearDown]: http://www.dartdocs.org/documentation/test/latest/index.html#test/test@id_tearDown
 
 ## Running Tests
 
-A single test file can be run just using `pub run test:test path/to/test.dart`
-(on Dart 1.10, this can be shortened to `pub run test path/to/test.dart`).
+A single test file can be run just using `pub run test path/to/test.dart`.
 
 ![Single file being run via pub run"](https://raw.githubusercontent.com/dart-lang/test/master/image/test1.gif)
 
-Many tests can be run at a time using `pub run test:test path/to/dir`.
+Many tests can be run at a time using `pub run test path/to/dir`.
 
 ![Directory being run via "pub run".](https://raw.githubusercontent.com/dart-lang/test/master/image/test2.gif)
 
 It's also possible to run a test on the Dart VM only by invoking it using `dart
 path/to/test.dart`, but this doesn't load the full test runner and will be
 missing some features.
 
 The test runner considers any file that ends with `_test.dart` to be a test
 file. If you don't pass any paths, it will run all the test files in your
 `test/` directory, making it easy to test your entire application at once.
 
 By default, tests are run in the Dart VM, but you can run them in the browser as
-well by passing `pub run test:test -p chrome path/to/test.dart`.
-`test` will take care of starting the browser and loading the tests, and all
-the results will be reported on the command line just like for VM tests. In
-fact, you can even run tests on both platforms with a single command: `pub run
-test:test -p "chrome,vm" path/to/test.dart`.
+well by passing `pub run test -p chrome path/to/test.dart`. `test` will take
+care of starting the browser and loading the tests, and all the results will be
+reported on the command line just like for VM tests. In fact, you can even run
+tests on both platforms with a single command: `pub run test -p "chrome,vm"
+path/to/test.dart`.
 
 ### Restricting Tests to Certain Platforms
 
 Some test files only make sense to run on particular platforms. They may use
 `dart:html` or `dart:io`, they might test Windows' particular filesystem
 behavior, or they might use a feature that's only available in Chrome. The
 [`@TestOn`][TestOn] annotation makes it easy to declare exactly which platforms
 a test file should run on. Just put it at the top of your file, before any
 `library` or `import` declarations:
 
@@ skipping 471 matching lines @@
 ```shell
 $ pub serve
 Loading source assets...
 Loading test/pub_serve transformers...
 Serving my_app web on http://localhost:8080
 Serving my_app test on http://localhost:8081
 Build completed successfully
 ```
 
 In this case, the port is `8081`. In another terminal, pass this port to
-`--pub-serve` and otherwise invoke `pub run test:test` as normal:
+`--pub-serve` and otherwise invoke `pub run test` as normal:
 
 ```shell
-$ pub run test:test --pub-serve=8081 -p chrome
+$ pub run test --pub-serve=8081 -p chrome
 "pub serve" is compiling test/my_app_test.dart...
 "pub serve" is compiling test/utils_test.dart...
 00:00 +42: All tests passed!
 ```
 
 ## Further Reading
 
 Check out the [API docs][api] for detailed information about all the functions
 available to tests.
 
 [api]: http://www.dartdocs.org/documentation/test/latest/index.html
 
 The test runner also supports a machine-readable JSON-based reporter. This
 reporter allows the test runner to be wrapped and its progress presented in
 custom ways (for example, in an IDE). See [the protocol documentation][json] for
 more details.
 
 [json]: https://github.com/dart-lang/test/blob/master/doc/json_reporter.md