Mention that blaze run doesn't run in PWD.
RELNOTES: None.
PiperOrigin-RevId: 230809572
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index f9e57a3..9502e96 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -2030,7 +2030,7 @@
<h2 id='run'>Running executables with Bazel</h2>
<p>
The <code>bazel run</code> command is similar to <code>bazel build</code>, except
- it is used to build and run a single target. Here is a typical session:
+ it is used to build <em>and run</em> a single target. Here is a typical session:
</p>
<pre>
% bazel run -- java/myapp:myapp --arg1 --arg2
@@ -2058,6 +2058,11 @@
(The program being run simply says hello and prints out its args.)
</p>
+<p><code>bazel run</code> is similar, but not identical, to directly invoking
+the binary built by Bazel. In particular, this command does not run the target
+in the current working directory. <code>bazel run</code> should not be used if
+the binary's behavior depends on the directory it's invoked in.
+
<h3>Options for <code>bazel run</code></h3>
<h4 id='flag--run_under_run'><code class='flag'>--run_under=<var>command-prefix</var></code></h4>
