plumbing-overview: minor fixes

[lttng-docs.git] / contents / understanding-lttng / core-concepts / channel / channel-overwrite-mode-vs-discard-mode.md

diff --git a/contents/understanding-lttng/core-concepts/channel/channel-overwrite-mode-vs-discard-mode.md b/contents/understanding-lttng/core-concepts/channel/channel-overwrite-mode-vs-discard-mode.md
index 2879bf27a0cb717e8e7d8a7af46da119256d77c6..53d799b644f27df866a9a92262bfd9267d161426 100644 (file)
--- a/contents/understanding-lttng/core-concepts/channel/channel-overwrite-mode-vs-discard-mode.md
+++ b/contents/understanding-lttng/core-concepts/channel/channel-overwrite-mode-vs-discard-mode.md
@@ -9,7 +9,7 @@ As events occur, they are serialized as trace data into a specific
 sub-buffer (yellow arc in the following animation) until it is full:
 when this happens, the sub-buffer is marked as consumable (red) and
 another, _empty_ (white) sub-buffer starts receiving the following
-events. The marked sub-buffer will be consumed eventually by a consumer
+events. The marked sub-buffer is eventually consumed by a consumer
 daemon (returns to white).
 
 <script type="text/javascript">
@@ -70,7 +70,7 @@ Beware that, in overwrite mode, a whole sub-buffer is abandoned as soon
 as a new event doesn't find an empty sub-buffer, whereas in discard
 mode, only the event that doesn't fit is discarded.
 
-Also note that a count of lost events will be incremented and saved in
+Also note that a count of lost events is incremented and saved in
 the trace itself when an event is lost in discard mode, whereas no
 information is kept when a sub-buffer gets overwritten before being
 committed.