installing-lttng: minor fixes

[lttng-docs.git] / contents / using-lttng / controlling-tracing / enabling-disabling-events.md

diff --git a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
index 98828c4e9c1fa108e7ada6cd575a2cd7beebce52..e41a9336716fd4685c9183da12718c6354ad9b7c 100644 (file)
--- a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
+++ b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
@@ -12,7 +12,7 @@ in source code/binary program, logical processor and time capturing
 some payload) being recorded as trace data. This specific condition is
 composed of:
 
-  1. A **domain** (kernel, user space, `java.util.loggin`, or log4j)
+  1. A **domain** (kernel, user space, `java.util.logging`, or log4j)
      (required).
   2. One or many **instrumentation points** in source code or binary
      program (tracepoint name, address, symbol name, function name,
@@ -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