X-Git-Url: http://git.efficios.com/?p=ctf.git;a=blobdiff_plain;f=common-trace-format-reqs.txt;h=e5e7c7a595709e9dd446486151952bc06ae1bc43;hp=8a9f3b65157a2d2b3335bcb53c22aa52196a5166;hb=ddd045b0ac45dcefe02f9e9320814b3e4adfc015;hpb=5ba9f19825d69b9bd6316094bb735b34e61856bb

diff --git a/common-trace-format-reqs.txt b/common-trace-format-reqs.txt
index 8a9f3b6..e5e7c7a 100644
--- a/common-trace-format-reqs.txt
+++ b/common-trace-format-reqs.txt
@@ -16,7 +16,7 @@ Aaron Spear <aaron_spear@mentor.com>
 Philippe Maisonneuve <Philippe.Maisonneuve@windriver.com>
 Felix Burton <Felix.Burton@windriver.com>
 Andrew McDermott <Andrew.McDermott@windriver.com>
-"Frank Ch. Eigler" <fche@redhat.com>
+Frank Ch. Eigler <fche@redhat.com>
 Michel Dagenais <michel.dagenais@polymtl.ca>
 Stefan Hajnoczi <stefanha@gmail.com>
 Multi-Core Association Tool Infrastructure Workgroup
@@ -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