Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/06c6fc97d0fdda02216198cabf337aa66f41f36f
>---------------------------------------------------------------
commit 06c6fc97d0fdda02216198cabf337aa66f41f36f
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date: Mon Mar 27 14:35:09 2023 +0200
treewide: fix typos
Fix typos in English slides and labs:
developper -> developer
adress -> address
Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>
>---------------------------------------------------------------
06c6fc97d0fdda02216198cabf337aa66f41f36f
labs/debugging-application-crash/debugging-application-crash.tex | 2 +-
slides/debugging-kernel-debugging/debugging-kernel-debugging.tex | 2 +-
slides/kernel-driver-development-dma/kernel-driver-development-dma.tex | 2 +-
slides/realtime-linux-benchmarking/realtime-linux-benchmarking.tex | 2 +-
slides/sysdev-customizing-dt/sysdev-customizing-dt.tex | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/labs/debugging-application-crash/debugging-application-crash.tex b/labs/debugging-application-crash/debugging-application-crash.tex
index 87369748..5ef57107 100644
--- a/labs/debugging-application-crash/debugging-application-crash.tex
+++ b/labs/debugging-application-crash/debugging-application-crash.tex
@@ -114,7 +114,7 @@ crash.
\section{GDB Python support}
-When developping and debugging applications, sometimes we often uses the same
+When developing and debugging applications, sometimes we often uses the same
set of commands over and over under GDB. Rather than doing so, we can create
python scripts that are integrated with GDB.
diff --git a/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex b/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 99ecc604..7cb81c0c 100644
--- a/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -304,7 +304,7 @@
\begin{frame}
\frametitle{{\em KASAN}}
\begin{itemize}
- \item Kernel Adress Space Sanitizer
+ \item Kernel Address Space Sanitizer
\item Allows to find use-after-free and out-of-bounds memory accesses
\item Uses GCC to instrument the kernel at compile-time
\item Supported by almost all architectures (ARM, ARM64, PowerPC, RISC-V,
diff --git a/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex b/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
index 256e9671..38a7fac4 100644
--- a/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
+++ b/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
@@ -218,7 +218,7 @@ void dma_unmap_single(struct device *dev, dma_addr_t handdle,
\kfunc{dma_request_channel}, or one of its variants
\item Configure it for our use case, by filling a
\kstruct{dma_slave_config} structure with various parameters
- (source and destination adresses, accesses width, etc.) and
+ (source and destination addresses, accesses width, etc.) and
passing it as an argument to \kfunc{dmaengine_slave_config}
\item Start a new transaction with
\kfunc{dmaengine_prep_slave_single} or
diff --git a/slides/realtime-linux-benchmarking/realtime-linux-benchmarking.tex b/slides/realtime-linux-benchmarking/realtime-linux-benchmarking.tex
index 7ee5bcf8..ee532362 100644
--- a/slides/realtime-linux-benchmarking/realtime-linux-benchmarking.tex
+++ b/slides/realtime-linux-benchmarking/realtime-linux-benchmarking.tex
@@ -161,7 +161,7 @@ cat /sys/kernel/tracing/tracing_max_latency
\frametitle{rtla}
\textbf{R}eal\textbf{T}ime \textbf{L}inux \textbf{A}nalysis tool
\begin{itemize}
- \item Developped by Daniel Bristot de Oliveira
+ \item Developed by Daniel Bristot de Oliveira
\item High-level interface to the \code{timerlat} and \code{osnoise} tracers
\item \code{rtla osnoise|timerlat top|hist} gives high-level view of noise and latencies
\item Can generate histograms, that can then be visualized
diff --git a/slides/sysdev-customizing-dt/sysdev-customizing-dt.tex b/slides/sysdev-customizing-dt/sysdev-customizing-dt.tex
index 140d3f76..13ccaf6e 100644
--- a/slides/sysdev-customizing-dt/sysdev-customizing-dt.tex
+++ b/slides/sysdev-customizing-dt/sysdev-customizing-dt.tex
@@ -1,7 +1,7 @@
\begin{frame}
\frametitle{Customize your board device tree!}
\begin{itemize}
- \item Kernel developpers write {\em Device Tree Sources (DTS)},
+ \item Kernel developers write {\em Device Tree Sources (DTS)},
which become {\em Device Tree Blobs (DTB)} once compiled.
\item There is one different Device Tree for each board/platform
supported by the kernel, available in