X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fusing-lttng%2Finstrumenting%2Fintro.md;h=a75227d902cfedaf5c69869d64b551d4a1b9bb6b;hb=ba3b19940f99233f69286f343aaf47b0bb0cdb99;hp=e34bdc5dfd1cc6992290f6af6b8dbea6bb703e7f;hpb=5e0cbfb01373c18e521217342fd8a9159cc186b1;p=lttng-docs.git

diff --git a/contents/using-lttng/instrumenting/intro.md b/contents/using-lttng/instrumenting/intro.md
index e34bdc5..a75227d 100644
--- a/contents/using-lttng/instrumenting/intro.md
+++ b/contents/using-lttng/instrumenting/intro.md
@@ -15,8 +15,8 @@ All the previous examples have something in common: they rely on
 skin, cardiac monitoring would be futile.
 
 LTTng, as a tracer, is no different from the real life examples above.
-If you're about to trace a software system, i.e. record its history of
-execution, you better have probes in the subject you're
+If you're about to trace a software system or, put in other words, record its
+history of execution, you better have probes in the subject you're
 tracing: the actual software. Various ways were developed to do this.
 The most straightforward one is to manually place probes, called
 _tracepoints_, in the software's source code. The Linux kernel tracing
@@ -26,7 +26,7 @@ If you're only interested in tracing the Linux kernel, it may very well
 be that your tracing needs are already appropriately covered by LTTng's
 built-in Linux kernel tracepoints and other probes. Or you may be in
 possession of a user space application which has already been
-instrumented. In such cases, the work will reside entirely in the design
+instrumented. In such cases, the work resides entirely in the design
 and execution of tracing sessions, allowing you to jump to
 [Controlling tracing](#doc-controlling-tracing) right now.