X-Git-Url: http://git.efficios.com/?p=ctf.git;a=blobdiff_plain;f=common-trace-format-reqs.txt;h=e5e7c7a595709e9dd446486151952bc06ae1bc43;hp=66fe55a53358ebef60ba6545d0b826993cc33880;hb=ed8509fc3bdc87500e78fd93c617aa0b867a4266;hpb=cf59b3003b66fe61d42e954bb07e9497b42e6ef2

diff --git a/common-trace-format-reqs.txt b/common-trace-format-reqs.txt
index 66fe55a..e5e7c7a 100644
--- a/common-trace-format-reqs.txt
+++ b/common-trace-format-reqs.txt
@@ -268,7 +268,7 @@ Enumerating these higher-level requirements influence the trace format in many
 ways. For instance, a requirement for compactness leads to schemes where all
 information repetition should be eliminated. Thus the need for optional
 per-section context information. Another example is the requirement for speed
-and streaming. The requirement for speed ans treaming leads to zero-copy
+and streaming. The requirement for speed and streaming leads to zero-copy
 implementations, which imply that the trace format should be written natively by
 the tracer.  The tracer requirements stated in this section are stated to ensure
 that the trace format structure makes it possible for a tracer to cope with the