Update docs / scripts for tracedump -> apitrace dump change.

[apitrace] / README.markdown

diff --git a/README.markdown b/README.markdown
index 82f5e975d9e6c48266bf97d893876f094f63a327..d35f2c46d9c96dfa702d3bb29339712c4a9dd0f9 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -7,7 +7,9 @@ About **apitrace**
 
 * retrace OpenGL calls from a file;
 
-* visualize trace files, and inspect state.
+* inspect OpenGL state at any call while retracing;
+
+* visualize and edit trace files.
 
 
 Basic usage
@@ -27,7 +29,7 @@ directory.  You can specify the written trace filename by setting the
 
 View the trace with
 
-    /path/to/tracedump application.trace | less -R
+    /path/to/apitrace dump --color application.trace | less -R
 
 Replay the trace with
 
@@ -86,7 +88,7 @@ Windows
 
 * View the trace with
 
-        \path\to\tracedump application.trace
+        \path\to\apitrace dump application.trace
 
 * Replay the trace with
 
@@ -106,7 +108,7 @@ and
 [`GL_GREMEDY_frame_terminator`](http://www.opengl.org/registry/specs/GREMEDY/frame_terminator.txt)
 GL extensions.
 
-*apitrace* will advertise and intercept these GL extensions independently of
+**apitrace** will advertise and intercept these GL extensions independently of
 the GL implementation.  So all you have to do is to use these extensions when
 available.
 
@@ -171,7 +173,7 @@ There are several advanced usage examples meant for OpenGL implementors.
 Regression testing
 ------------------
 
-These are the steps to create a regression test-suite around apitrace:
+These are the steps to create a regression test-suite around **apitrace**:
 
 * obtain a trace