From 3655495b49acc681cb0b7aa79f5533daf5c91368 Mon Sep 17 00:00:00 2001 From: Sylvestre Ledru Date: Sat, 12 Aug 2017 15:08:11 +0000 Subject: [PATCH] Fix some minor typos in the llvm XRay exemple llvm-svn: 310777 --- llvm/docs/XRayExample.rst | 2 +- llvm/docs/XRayFDRFormat.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/llvm/docs/XRayExample.rst b/llvm/docs/XRayExample.rst index 5dfb0bf..fff5bbe 100644 --- a/llvm/docs/XRayExample.rst +++ b/llvm/docs/XRayExample.rst @@ -100,7 +100,7 @@ this data in a spreadsheet, we can output the results as CSV using the If we want to get a textual representation of the raw trace we can use the ``llvm-xray convert`` tool to get YAML output. The first few lines of that -ouput for an example trace would look like the following: +output for an example trace would look like the following: :: diff --git a/llvm/docs/XRayFDRFormat.rst b/llvm/docs/XRayFDRFormat.rst index 233e96a..8a4088a 100644 --- a/llvm/docs/XRayFDRFormat.rst +++ b/llvm/docs/XRayFDRFormat.rst @@ -28,7 +28,7 @@ Each trace file corresponds to a sequence of events in a particular thread. The file has a header followed by a sequence of discriminated record types. -The endianess of byte fields matches the endianess of the platform which +The endianness of byte fields matches the endianess of the platform which produced the trace file. -- 2.7.4