Clarify that the timeout is for all tests in the BUILD target, not for each individual test.
<p><code>String "enormous", "large" "medium" or "small",
default is "medium"; optional; <a href="#configurable-attributes">nonconfigurable</a></code></p>
-<p>Specifies a test's "heaviness": how much time/resources it needs to run.</p>
+<p>Specifies a test target's "heaviness": how much time/resources it needs to run.</p>
<p>Unit tests are considered "small", integration tests "medium", and end-to-end tests "large" or
"enormous". Bazel uses the size to determine a default timeout, which can be overridden using the
-<code>timeout</code> attribute. When the test is run locally, the <code>size</code> is additionally
-used for scheduling purposes: Bazel tries to respect <code>--local_{ram,cpu}_resources</code> and
-not overwhelm the local machine by running lots of heavy tests at the same time.</p>
+<code>timeout</code> attribute. The timeout is for all tests in the BUILD target, not for each
+individual test. When the test is run locally, the <code>size</code> is additionally used for
+scheduling purposes: Bazel tries to respect <code>--local_{ram,cpu}_resources</code> and not
+overwhelm the local machine by running lots of heavy tests at the same time.</p>
<p>Test sizes correspond to the following default timeouts and assumed peak local resource
usages:</p>
