X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fusing-lttng%2Fcontrolling-tracing%2Fenabling-disabling-events.md;h=26ab44eafbbbdd9ae61681c3597ccf5b9a61433e;hb=d9a0e8b1a2834c9fa52c6df79217800ac3581a77;hp=5701543197730d05faeaccace3b9626e9d222607;hpb=f11aa623d30b8d6b3b6a2b8d677c491474ecb018;p=lttng-docs.git

diff --git a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
index 5701543..26ab44e 100644
--- a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
+++ b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
@@ -16,7 +16,7 @@ composed of:
      (required).
   2. One or many **instrumentation points** in source code or binary
      program (tracepoint name, address, symbol name, function name,
-     logger name, etc.) to be executed (required).
+     logger name, amongst other types of probes) to be executed (required).
   3. A **log level** (each instrumentation point declares its own log
      level) or log level range to match (optional; only valid for user
      space domain).
@@ -139,7 +139,7 @@ Disabling an event does not add it to some blacklist: it simply removes
 it from its channel's whitelist. This is why you cannot disable an event
 which wasn't previously enabled.
 
-A disabled event will not generate any trace data, even if all its
+A disabled event doesn't generate any trace data, even if all its
 specified conditions are met.
 
 Events may be enabled and disabled at will, either when LTTng tracers