X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;ds=sidebyside;f=contents%2Fusing-lttng%2Finstrumenting%2Fc-application%2Fusing-tracepoint-classes.md;h=b6d4fc303c19fb7a4c4402e44450b722f1e071ea;hb=47bfcb757a0192864b56d12d775f65dc8b180aaf;hp=ba872b4de5eff372bb579a8c053d711021d964b5;hpb=6d30cd92b72a789ccdd2c881271dd4e51441a862;p=lttng-docs.git

diff --git a/contents/using-lttng/instrumenting/c-application/using-tracepoint-classes.md b/contents/using-lttng/instrumenting/c-application/using-tracepoint-classes.md
index ba872b4..b6d4fc3 100644
--- a/contents/using-lttng/instrumenting/c-application/using-tracepoint-classes.md
+++ b/contents/using-lttng/instrumenting/c-application/using-tracepoint-classes.md
@@ -18,7 +18,7 @@ your situation requires multiple tracepoints with different names, but
 with the same fields layout, the best practice is to manually create
 a tracepoint class and instantiate as many tracepoint instances as
 needed. One positive effect of such a design, amongst other advantages,
-is that all tracepoint instances of the same tracepoint class will
+is that all tracepoint instances of the same tracepoint class
 reuse the same serialization function, thus reducing cache pollution.
 
 As an example, here are three tracepoint definitions as we know them: