X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Funderstanding-lttng%2Fcore-concepts%2Fevent.md;h=5526e27c23e705f689f219d10b48803b840c0791;hb=85ccb28b9a18a29b9515e2d445185f8d0241c5f2;hp=3a632d5cb4d841375bd893d76d828aa26770e8b3;hpb=4280f59215672366f9c47f76c2a2f6dee9757ff7;p=lttng-docs.git

diff --git a/contents/understanding-lttng/core-concepts/event.md b/contents/understanding-lttng/core-concepts/event.md
index 3a632d5..5526e27 100644
--- a/contents/understanding-lttng/core-concepts/event.md
+++ b/contents/understanding-lttng/core-concepts/event.md
@@ -21,8 +21,7 @@ having multiple definitions depending on the context:
 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
-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):
@@ -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.
-
-The following illustration summarizes how tracing sessions, domains,
-channels and events are related:
-
-<div class="img img-90">
-<object data="/images/docs26/core-concepts.svg" type="image/svg+xml">
-  <img src="/images/docs26/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.