X-Git-Url: http://git.efficios.com/?p=ctf.git;a=blobdiff_plain;f=common-trace-format-specification.txt;h=b4d9dc3135f5df88beda3a95fce2914e4cdf0697;hp=1400952f94d2cf2872e1ec83a529df35e3a4bdfd;hb=32254806d53c32616a31f075713ce89939c036c5;hpb=284724ae8895cdf4df18eac62690b9d7c0a407ed

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index 1400952..b4d9dc3 100644
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -93,8 +93,9 @@ subset of the trace event types.
 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,
-a stored trace can be represented as a directory containing one file per stream.
+being recorded, each is associated with a distinct set of files for
+output. Therefore, 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