From 6e24a37d6dcd78f808415567f16db585ca7f92af Mon Sep 17 00:00:00 2001
From: Janak Ramakrishnan <janakr@google.com>
Date: Wed, 6 Jan 2016 01:56:12 +0000
Subject: [PATCH] Fix error in documentation -- SIGQUIT not SIGINT will make
 Bazel dump its threads!

Fixes #748

--
MOS_MIGRATED_REVID=111468883
---
 site/docs/bazel-user-manual.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/docs/bazel-user-manual.html b/site/docs/bazel-user-manual.html
index c72545eeb2ecff..2564a3102fd39c 100644
--- a/site/docs/bazel-user-manual.html
+++ b/site/docs/bazel-user-manual.html
@@ -3752,8 +3752,8 @@ <h2 id='profiling'>Troubleshooting performance by profiling</h2>
   </ul></li>
 </ul>
 
-<p>If Bazel appears to be hung, you can hit <kbd>&langle;Control&rangle;</kbd>-<kbd>\</kbd> or send Bazel
-  a <code>SIGINT</code> signal (<code>kill -3 $(bazel info server_pid)</code>) to get a
+<p>If Bazel appears to be hung, you can hit <kbd><kbd>ctrl</kbd> + <kbd>\</kbd></kbd> or send
+  Bazel a <code>SIGQUIT</code> signal (<code>kill -3 $(bazel info server_pid)</code>) to get a
   thread dump in the file <code>$(bazel info output_base)/server/jvm.out</code>.
 </p>