From: Jérémie Galarneau Date: Fri, 15 Mar 2013 21:36:05 +0000 (-0400) Subject: Typo fix in the tracers requirements X-Git-Tag: v1.8.3~22 X-Git-Url: http://git.efficios.com/?p=ctf.git;a=commitdiff_plain;h=fbf2fa4f7c15cfcde273e35cbc5ff2f9e7289043 Typo fix in the tracers requirements Signed-off-by: Jérémie Galarneau Signed-off-by: Mathieu Desnoyers --- 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