diff options
| author | José Fonseca <jose.r.fonseca@gmail.com> | 2011-09-23 08:24:28 +0100 |
|---|---|---|
| committer | José Fonseca <jose.r.fonseca@gmail.com> | 2011-09-23 08:24:28 +0100 |
| commit | 892cad6f24175221d2e7bdf3c7fe6c34b64ee50a (patch) | |
| tree | 68d50bd2157a95b37194a91c8eb0ed49e547a2bc | |
| parent | ceef54be9c9f8573122e2d1b60c2dd48066acbbb (diff) | |
Formatting fixes.
| -rw-r--r-- | README.markdown | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/README.markdown b/README.markdown index 82f5e97..c388042 100644 --- 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 @@ -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 |