2.7, 2.8, 2.9: occurance -> occurrence

[lttng-docs.git] / 2.8 / lttng-docs-2.8.txt

diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt
index 9ff38988821008896ba057b03af3534169e69e32..78952fc5b63e1ca28c43585c5b90c61f87bd62f0 100644 (file)
--- a/2.8/lttng-docs-2.8.txt
+++ b/2.8/lttng-docs-2.8.txt
@@ -1,7 +1,7 @@
 The LTTng Documentation
 =======================
 Philippe Proulx <pproulx@efficios.com>
-v2.8, 14 March 2017
+v2.8, 24 July 2017
 
 
 include::../common/copyright.txt[]
@@ -586,14 +586,14 @@ sudo depmod -a
 .Java and Python application instrumentation and tracing
 ====
 If you need to instrument and trace <<java-application,Java
-applications>> on openSUSE, you need to build and install
+applications>> on Fedora, you need to build and install
 LTTng-UST{nbsp}{revision} <<building-from-source,from source>> and pass
 the `--enable-java-agent-jul`, `--enable-java-agent-log4j`, or
 `--enable-java-agent-all` options to the `configure` script, depending
 on which Java logging framework you use.
 
 If you need to instrument and trace <<python-application,Python
-applications>> on openSUSE, you need to build and install
+applications>> on Fedora, you need to build and install
 LTTng-UST{nbsp}{revision} from source and pass the
 `--enable-python-agent` option to the `configure` script.
 ====
@@ -658,14 +658,14 @@ If you use Hob:
 .Java and Python application instrumentation and tracing
 ====
 If you need to instrument and trace <<java-application,Java
-applications>> on openSUSE, you need to build and install
+applications>> on Yocto/OpenEmbedded, you need to build and install
 LTTng-UST{nbsp}{revision} <<building-from-source,from source>> and pass
 the `--enable-java-agent-jul`, `--enable-java-agent-log4j`, or
 `--enable-java-agent-all` options to the `configure` script, depending
 on which Java logging framework you use.
 
 If you need to instrument and trace <<python-application,Python
-applications>> on openSUSE, you need to build and install
+applications>> on Yocto/OpenEmbedded, you need to build and install
 LTTng-UST{nbsp}{revision} from source and pass the
 `--enable-python-agent` option to the `configure` script.
 ====
@@ -1713,7 +1713,7 @@ With so many similar terms, it's easy to get confused.
 An **event** is the consequence of the execution of an _instrumentation
 point_, like a tracepoint that you manually place in some source code,
 or a Linux kernel KProbe. An event is said to _occur_ at a specific
-time. Different actions can be taken upon the occurance of an event,
+time. Different actions can be taken upon the occurrence of an event,
 like record the event's payload to a buffer.
 
 An **event record** is the representation of an event in a sub-buffer. A
@@ -5331,12 +5331,12 @@ MODULE_VERSION(__stringify(LTTNG_MODULES_MAJOR_VERSION) "."
 ----
 --
 
-. Edit path:{probes/Makefile} and add your new kernel module object
+. Edit path:{probes/KBuild} and add your new kernel module object
   next to the existing ones:
 +
 --
 [source,make]
-.path:{probes/Makefile}
+.path:{probes/KBuild}
 ----
 # ...
 
@@ -7200,7 +7200,7 @@ event::
   or a Linux kernel KProbe.
 +
 An event is said to _occur_ at a specific time. Different actions can
-be taken upon the occurance of an event, like record the event's payload
+be taken upon the occurrence of an event, like record the event's payload
 to a sub-buffer.
 
 <<channel-overwrite-mode-vs-discard-mode,event loss mode>>::