update-w3c-deps import using blink 9d3793ee56e5bb1aa1eef078d848e1b0e6e4d355:

LayoutTests/imported/web-platform-tests/README.md

 The Web Platform Tests Project [![IRC chat](https://goo.gl/6nCIks)](http://irc.w3.org/?channels=testing)
 ==============================
 
 The Web Platform Tests Project is a W3C-coordinated attempt to build a
 cross-browser testsuite for the Web-platform stack. Writing tests in a
 way that allows them to be run in all browsers gives browser projects
 confidence that they are shipping software that is compatible with other
 implementations, and that later implementations will be compatible with
 their implementations. This in turn gives Web authors/developers
 confidence that they can actually rely on the Web platform to deliver on
@@ skipping 154 matching lines @@
 
 * Fork this repository (and make sure you're still relatively in sync
   with it if you forked a while ago).
 * Create a branch for your changes:
   `git checkout -b your-name/topic`.
 * Make your changes.
 * Run the lint script described below.
 * Commit locally and push that to your repo.
 * Send in a pull request based on the above.
 
-A lint is available to test for common mistakes in testcases. It can
-be run with:
+Lint tool
+---------
+
+We have a lint tool for catching common mistakes in test files. You
+can run it manually by starting the `lint` executable from the root of
+your local web-platform-tests working directory like this:
 
 ```
 ./lint
 ```
 
-in the root of the checkout. It is also run for every submitted pull
-request, and branches with lint errors will not get merged. In the
-unusual case that the lint is reporting an error for something that is
-essential to your test, there is a whitelist at
-`tools/lint/lint.whitelist` that may be updated.
+The lint tool is also run automatically for every submitted pull
+request, and reviewers will not merge branches with tests that have
+lint errors, so you must fix any errors the lint tool reports. For
+details on doing that, see the [lint-tool documentation][lint-tool].
+
+But in the unusual case of error reports for things essential to a
+certain test or that for other exceptional reasons shouldn't prevent
+a merge of a test, update and commit the `lint.whitelist` file in the
+web-platform-tests root directory to suppress the error reports. For
+details on doing that, see the [lint-tool documentation][lint-tool].
+
+[lint-tool]: https://github.com/w3c/web-platform-tests/blob/master/docs/lint-tool.md
 
 Adding command-line scripts ("tools" subdirs)
 ---------------------------------------------
 
 Sometimes you may want to add a script to the repository that's meant
 to be used from the command line, not from a browser (e.g., a script
 for generating test files). If you want to ensure (e.g., for security
 reasons) that such scripts won't be handled by the HTTP server, but
 will instead only be usable from the command line, then place them in
 either:
@@ skipping 40 matching lines @@
 [contributing]: https://github.com/w3c/web-platform-tests/blob/master/CONTRIBUTING.md
 [ircw3org]: https://www.w3.org/wiki/IRC
 [ircarchive]: http://krijnhoetmer.nl/irc-logs/testing/
 [mailarchive]: http://lists.w3.org/Archives/Public/public-test-infra/
 
 Documentation
 =============
 
 * [How to write and review tests](http://testthewebforward.org/docs/)
 * [Documentation for the wptserve server](http://wptserve.readthedocs.org/en/latest/)