Improve blaze query documentation.
Fixes https://github.com/bazelbuild/bazel/issues/5929
RELNOTES: None
PiperOrigin-RevId: 308993631
diff --git a/site/docs/query.html b/site/docs/query.html
index fe2c330..0875aac 100644
--- a/site/docs/query.html
+++ b/site/docs/query.html
@@ -580,10 +580,12 @@
<p>
The <code>deps</code> operator accepts an optional second argument,
which is an integer literal specifying an upper bound on the depth
- of the search. So <code>deps(foo:*, 1)</code> evaluates to all the
- direct prerequisites of any target in the <code>foo</code> package,
- and <code>deps(foo:*, 2)</code> further includes the nodes directly
- reachable from the nodes in <code>deps(foo:*, 1)</code>, and so on.
+ of the search. So <code>deps(foo:*, 0)</code> returns all targets
+ in the <code>foo</code> package, while <code>deps(foo:*, 1)</code>
+ further includes the direct prerequisites of any target in the
+ <code>foo</code> package, and <code>deps(foo:*, 2)</code> further
+ includes the nodes directly reachable from the nodes in
+ <code>deps(foo:*, 1)</code>, and so on.
(These numbers correspond to the ranks shown in
the <a href='#output-ranked'><code>minrank</code></a> output
format.) If the <var>depth</var> parameter is omitted, the search
