doc: update info about flame graphs in diagnostics.html

Use Brendan Gregg's FlameGraphs page link.
Mention the flame graph is available from the upstream pprof.

Change-Id: Ife1d5a5f4f93f20cd5952a09083f798b77d25a60
Reviewed-on: https://go-review.googlesource.com/83798
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

diff --git a/doc/diagnostics.html b/doc/diagnostics.html
index 8f5b59ecee77eb7282e6fbad55a2c24ea20c5802..ea419d2c409daab4298e2d66c35c3207a7449d0c 100644 (file)
--- a/doc/diagnostics.html
+++ b/doc/diagnostics.html
@@ -119,7 +119,7 @@ so it is recommended to collect only a single profile at a time.
 
 <p>
 The Go tools provide text, graph, and <a href="http://valgrind.org/docs/manual/cl-manual.html">callgrind</a>
-visualization of the profile data via
+visualization of the profile data using
 <code><a href="https://github.com/google/pprof/blob/master/doc/pprof.md">go tool pprof</a></code>.
 Read <a href="https://blog.golang.org/profiling-go-programs">Profiling Go programs</a>
 to see them in action.
@@ -149,9 +149,11 @@ in the listing.</p>
 </p>
 
 <p>
-Another way to visualize profile data is a <a href="https://github.com/uber/go-torch">flame graph</a>.
+Another way to visualize profile data is a <a href="http://www.brendangregg.com/flamegraphs.html">flame graph</a>.
 Flame graphs allow you to move in a specific ancestry path, so you can zoom
-in/out specific sections of code more easily.
+in/out of specific sections of code.
+The <a href="https://github.com/google/pprof">upstream pprof</a>
+has support for flame graphs.
 </p>
 
 <p>