Remove mention of `no-remote-cache` from internal docs.
it's treated as a remote cache and disabled entirely unless <code>--incompatible_remote_results_ignore_disk</code>
is set in which case the local components will be used.
</li>
-
<li><code>no-remote-exec</code> keyword results in the action or test never being
executed remotely (but it may be cached remotely).
</li>
- <li><code>no-remote</code> keyword prevents the action or test from being executed remotely
- or cached remotely. This is equivalent to using both no-remote-cache and no-remote-exec.
+ <li><code>no-remote</code> keyword prevents the action or test from being executed remotely or
+ cached remotely. This is equivalent to using both
+ <code>no-remote-cache</code> and <code>no-remote-exec</code>.
</li>
<li><code>local</code> keyword precludes the action or test from being remotely cached,
