Clarify monotonicity requirement on timestamp begin

[ctf.git] / common-trace-format-specification.md

diff --git a/common-trace-format-specification.md b/common-trace-format-specification.md
index d98417601c11be852d72231d3e7a5f3dbe1e0860..372285c23f461e163ab20e092e493f9210fd09df 100644 (file)
--- a/common-trace-format-specification.md
+++ b/common-trace-format-specification.md
@@ -464,6 +464,9 @@ enum {
 }
 ~~~
 
+An enumeration field can have an integral value for which the associated
+enumeration type does not map to a string.
+
 ### 4.2 Compound types
 
 Compound are aggregation of type declarations. Compound types include
@@ -833,10 +836,12 @@ TSDL metadata):
     range between these timestamps should include all event timestamps
     assigned to events contained within the packet. The timestamp at the
     beginning of an event packet is guaranteed to be below or equal the
-    timestamp at the end of that event packet. The timestamp at the end
-    of an event packet is guaranteed to be below or equal the
-    timestamps at the end of any following packet within the same stream.
-    See [Clocks](#spec8) for more detail.
+    timestamp at the end of that event packet. The timestamp at the
+    beginning of an event packet is guaranteed to be above or equal the
+    timestamps at the beginning of any prior packet within the same
+    stream. The timestamp at the end of an event packet is guaranteed to
+    be below or equal the timestamps at the end of any following packet
+    within the same stream. See [Clocks](#spec8) for more detail.
   * **Events discarded count**. Snapshot of a per-stream
     free-running counter, counting the number of events discarded that
     were supposed to be written in the stream after the last event in
@@ -886,13 +891,13 @@ trace {
 };
 ~~~
 
-If the magic number is not present, tools such as `file` will have no
-mean to discover the file type.
+If the magic number (`magic` field) is not present,
+tools such as `file` will have no mean to discover the file type.
 
-If the uuid is not present, no validation that the metadata actually
-corresponds to the stream is performed.
+If the `uuid` field is not present, no validation that the metadata
+actually corresponds to the stream is performed.
 
-If the stream_id packet header field is missing, the trace can only
+If the `stream_id` packet header field is missing, the trace can only
 contain a single stream. Its `id` field can be left out, and its events
 don't need to declare a `stream_id` field.