Clarify that unlisted enumeration values are allowed

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

diff --git a/common-trace-format-specification.md b/common-trace-format-specification.md
index d98417601c11be852d72231d3e7a5f3dbe1e0860..203f13f51133e1cb0424d0683375ed107eb98542 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
@@ -886,13 +889,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.