domain: add Python domain to list

[lttng-docs.git] / contents / getting-started / tracing-your-own-user-application.md

diff --git a/contents/getting-started/tracing-your-own-user-application.md b/contents/getting-started/tracing-your-own-user-application.md
index 95d2f37824033fff0ee87a7b5eef843e292ec57f..252edce998d0021ef463fecc5389ac5f28d6e929 100644 (file)
--- a/contents/getting-started/tracing-your-own-user-application.md
+++ b/contents/getting-started/tracing-your-own-user-application.md
@@ -10,7 +10,7 @@ Make sure the LTTng-tools and LTTng-UST packages
 [are installed](#doc-installing-lttng).
 
 Tracing is just like having `printf()` calls at specific locations of
-your source code, albeit LTTng is much more faster and flexible than
+your source code, albeit LTTng is much faster and more flexible than
 `printf()`. In the LTTng realm, **`tracepoint()`** is analogous to
 `printf()`.
 
@@ -72,7 +72,7 @@ TRACEPOINT_EVENT(
 The exact syntax is well explained in the
 [C application](#doc-c-application) instrumentation guide of the
 [Using LTTng](#doc-using-lttng) chapter, as well as in the
-<a href="/man/3/lttng-ust" class="ext">LTTng-UST man page</a>.
+<a href="/man/3/lttng-ust/v2.7" class="ext">LTTng-UST man page</a>.
 
 Save the above snippet as `hello-tp.h`.
 
@@ -154,6 +154,9 @@ Here's the whole build process:
 
 <figure class="img img-100">
 <img src="/images/docs26/ust-flow.png" alt="User space tracing's build process">
+<figcaption>
+    User space tracing build process
+</figcaption>
 </figure>
 
 If you followed the