plumbing-overview: minor fixes

[lttng-docs.git] / contents / understanding-lttng / core-concepts / event.md

diff --git a/contents/understanding-lttng/core-concepts/event.md b/contents/understanding-lttng/core-concepts/event.md
index bca5fcced659000f02bfcf7173bbd74f4eabc3e8..5526e27c23e705f689f219d10b48803b840c0791 100644 (file)
--- a/contents/understanding-lttng/core-concepts/event.md
+++ b/contents/understanding-lttng/core-concepts/event.md
@@ -18,11 +18,10 @@ having multiple definitions depending on the context:
      specific rules which could lead to the transfer of actual
      occurring events (1) to recorded events (2).
 
      specific rules which could lead to the transfer of actual
      occurring events (1) to recorded events (2).
 

-The whole [Core concepts](#doc-core-concepts) section focusses on the
+The whole [Core concepts](#doc-core-concepts) section focuses on the

 third definition. An event is always registered to _one or more_
 channels and may be enabled or disabled at will per channel. A disabled
 third definition. An event is always registered to _one or more_
 channels and may be enabled or disabled at will per channel. A disabled

-event will never lead to a recorded event, even if its channel
-is enabled.
+event never leads to a recorded event, even if its channel is enabled.

 
 An event (3) is enabled with a few conditions that must _all_ be met
 when an event (1) happens in order to generate a recorded event (2):
 
 An event (3) is enabled with a few conditions that must _all_ be met
 when an event (1) happens in order to generate a recorded event (2):


@@ -33,16 +32,3 @@ when an event (1) happens in order to generate a recorded event (2):
      log level range specified when enabling the event.
   3. **Optionally**, the occurring event must satisfy a custom
      expression, or _filter_, specified when enabling the event.
      log level range specified when enabling the event.
   3. **Optionally**, the occurring event must satisfy a custom
      expression, or _filter_, specified when enabling the event.

-
-The following illustration summarizes how tracing sessions, domains,
-channels and events are related:
-
-<div class="img img-90">
-<object data="/images/docs/core-concepts.svg" type="image/svg+xml">
-  <img src="/images/docs/core-concepts.svg">
-</object>
-</div>
-
-This diagram also shows how events may be individually enabled/disabled
-(green/grey) and how a given event may be registered to more than one
-channel.