lttng-modules-tp-fields: since 2.7

[lttng-docs.git] / contents / using-lttng / instrumenting / instrumenting-linux-kernel / instrumenting-out-of-tree-linux-kernel.md

diff --git a/contents/using-lttng/instrumenting/instrumenting-linux-kernel/instrumenting-out-of-tree-linux-kernel.md b/contents/using-lttng/instrumenting/instrumenting-linux-kernel/instrumenting-out-of-tree-linux-kernel.md
index ce1ae11dab953baeb0c69febc31f943ed7647dc8..2eecabd80f8cb6f92fe8f7a8a838a499912cb5ec 100644 (file)
--- a/contents/using-lttng/instrumenting/instrumenting-linux-kernel/instrumenting-out-of-tree-linux-kernel.md
+++ b/contents/using-lttng/instrumenting/instrumenting-linux-kernel/instrumenting-out-of-tree-linux-kernel.md
@@ -26,7 +26,7 @@ build time verification:
 
 The preferred, flexible way to include your module's mainline
 tracepoint definition header is to put it in a specific directory
-relative to your module's root, e.g., `tracepoints`, and include it
+relative to your module's root (`tracepoints`, for example) and include it
 relative to your module's root directory in the LTTng custom probe's
 source: