X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fgetting-started%2Fviewing-and-analyzing.md;h=988ddec12cfd05c6177ee5b7b6068989f0873c5f;hb=3b5b45ec9eeae44744acb849c1a04eddd9d971c4;hp=e49cc5a0c464010d09797e2df18f4088e7496a9e;hpb=a345f8e04ecd928a93d445ed55daaaa18a2c317b;p=lttng-docs.git

diff --git a/contents/getting-started/viewing-and-analyzing.md b/contents/getting-started/viewing-and-analyzing.md
index e49cc5a..988ddec 100644
--- a/contents/getting-started/viewing-and-analyzing.md
+++ b/contents/getting-started/viewing-and-analyzing.md
@@ -20,11 +20,7 @@ Many ways exist to read your LTTng traces:
     is an Eclipse plugin used to visualize and analyze various types of
     traces, including LTTng's. It also comes as a standalone application
     and can be downloaded from
-    <a href="http://secretaire.dorsal.polymtl.ca/~gbastien/TracingRCP/TraceCompass/" class="ext">here</a>
-    for a daily build of the latest source code. A version containing
-    some experimental features like Virtual Machine analysis and
-    Critical Path analysis is also available
-    <a href="http://secretaire.dorsal.polymtl.ca/~gbastien/TracingRCP/DorsalExperimental/" class="ext">here</a>.
+    <a href="http://projects.eclipse.org/projects/tools.tracecompass/downloads" class="ext">here</a>.
 
 LTTng trace files are usually recorded in the `~/lttng-traces` directory.
 Let's now view the trace and perform a basic analysis using
@@ -37,8 +33,8 @@ path to `babeltrace` with no options:
 babeltrace ~/lttng-traces/my-session
 </pre>
 
-`babeltrace` will find all traces within the given path recursively and
-output all their events, merging them intelligently.
+`babeltrace` finds all traces within the given path recursively and
+prints all their events, merging them in order of time.
 
 Listing all the system calls of a Linux kernel trace with their arguments is
 easy with `babeltrace` and `grep`:
@@ -147,8 +143,8 @@ python3 top5proc.py ~/lttng-sessions/my-session-.../kernel
 </pre>
 
 Make sure the path you provide is the directory containing actual trace
-files (`channel0_0`, `metadata`, etc.): the `babeltrace` utility recurses
-directories, but the Python binding does not.
+files (`channel0_0`, `metadata`, and the rest): the `babeltrace` utility
+recurses directories, but the Python binding does not.
 
 Here's an example of output: