[xray] Fix xray document spelling

[yao]

Summary

fix a couple of words spelling

[dberris]

Thanks for this!

Some of these changes LGTM but the conversions from analyzing to analysing doesn't seem necessary (UK vs US English).

llvm/docs/XRay.rst

29

Thanks, though analysing is also a valid English spelling (not US English).

[yao]

revert the change for "analysing"

[dberris]

LGTM

Thanks!

PS. Do you need someone to land this for you?

[yao]

In D96658#2564522, @dberris wrote:

LGTM

Thanks!

PS. Do you need someone to land this for you?

I guess I have no permission to commit. If so, please give a hand.

thanks,
yao

[yao]

Please help to commit

[yao]

Is it committed?

[dberris]

Apologies for the delay, not yet. I'm going to land it ~now.

[dberris]

Actually, looks like this doesn't apply cleanly anymore. Sorry about that, can you rebase?

[yao]

updated.

[yao]

can you please land it? I had already rebased.

[dberris]

I'm trying to commit it now, but I need some information first: What should I put in the Author: line in the commit?

[yao]

Yao Zhao
[e-mail]

thanks

llvm/docs/XRay.rst

 
 XRay in LLVM
 ============
 
 XRay consists of three main parts:
 
 - Compiler-inserted instrumentation points.
 - A runtime library for enabling/disabling tracing at runtime.
 - A suite of tools for analysing the traces.
 
   **NOTE:** As of July 25, 2018 , XRay is only available for the following
   architectures running Linux: x86_64, arm7 (no thumb), aarch64, powerpc64le,
   mips, mipsel, mips64, mips64el, NetBSD: x86_64, FreeBSD: x86_64 and
   OpenBSD: x86_64.
 
 The compiler-inserted instrumentation points come in the form of nop-sleds in
 the final generated binary, and an ELF section named ``xray_instr_map`` which
 contains entries pointing to these instrumentation points. The runtime library
 relies on being able to access the entries of the ``xray_instr_map``, and
 overwrite the instrumentation points at runtime.
 
 Using XRay
 ==========
 
 You can use XRay in a couple of ways:
 
 - Instrumenting your C/C++/Objective-C/Objective-C++ application.
 - Generating LLVM IR with the correct function attributes.
 
-The rest of this section covers these main ways and later on how to customise
+The rest of this section covers these main ways and later on how to customize
 what XRay does in an XRay-instrumented binary.
 
 Instrumenting your C/C++/Objective-C Application
 ------------------------------------------------
 
 The easiest way of getting XRay instrumentation for your application is by
 enabling the ``-fxray-instrument`` flag in your clang invocation.
 

llvm/docs/XRayExample.rst

 We then build the above with XRay instrumentation:
 
 ::
 
   $ clang++ -o sample -O3 sample.cc -std=c++11 -fxray-instrument -fxray-instruction-threshold=1
   $ XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic" ./sample
 
 We can then explore the graph rendering of the trace generated by this sample
-application. We assume you have the graphviz toosl available in your system,
+application. We assume you have the graphviz tools available in your system,
 including both ``unflatten`` and ``dot``. If you prefer rendering or exploring
 the graph using another tool, then that should be feasible as well. ``llvm-xray
 graph`` will create DOT format graphs which should be usable in most graph
 rendering applications. One example invocation of the ``llvm-xray graph``
 command should yield some interesting insights to the workings of C++
 applications:
 
 ::