Clarify number of files per stream

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index 918b47218343c3bf5cae09b512a0dfa785efc119..9cd39ded0b898159da9672b4262014b0b924ee88 100644 (file)
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -94,8 +94,8 @@ The final output of the trace, after its generation and optional transport over
 the network, is expected to be either on permanent or temporary storage in a
 virtual file system. Because each event stream is appended to while a trace is
 being recorded, each is associated with a separate file for output.  Therefore,
 the network, is expected to be either on permanent or temporary storage in a
 virtual file system. Because each event stream is appended to while a trace is
 being recorded, each is associated with a separate file for output.  Therefore,

-a stored trace can be represented as a directory containing at least one
-file per stream.
+a stored trace can be represented as a directory containing zero, one or
+more files per stream.

 
 Meta-data description associated with the trace contains information on
 trace event types expressed in the Trace Stream Description Language
 
 Meta-data description associated with the trace contains information on
 trace event types expressed in the Trace Stream Description Language