[FE training-materials-updates] Remove improper usage of "those"
Michael Opdenacker
michael.opdenacker at free-electrons.com
Thu Oct 9 06:31:40 CEST 2014
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=cbdb70b178f7ec88928e5f958c8dd8a14620a9cf
>---------------------------------------------------------------
commit cbdb70b178f7ec88928e5f958c8dd8a14620a9cf
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Thu Oct 9 06:28:29 2014 +0200
Remove improper usage of "those"
- "those" is the plural of "that", not "this"
Using "those" implies that there are "these" objects
too, being closer.
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
cbdb70b178f7ec88928e5f958c8dd8a14620a9cf
README | 4 ++--
agenda/kernel-agenda.tex | 2 +-
labs/android-new-board/android-new-board.tex | 6 +++---
labs/kernel-debugging/kernel-debugging.tex | 2 +-
.../sysdev-application-development.tex | 2 +-
labs/sysdev-thirdparty/sysdev-thirdparty.tex | 2 +-
.../android-build-system-basics-envsetup.tex | 4 ++--
.../android-build-system-basics-results.tex | 2 +-
.../android-native-layer-toolbox.tex | 2 +-
slides/boottime-application/boottime-application.tex | 4 ++--
slides/kernel-device-model/kernel-device-model.tex | 4 ++--
.../kernel-driver-development-debugging.tex | 10 +++++-----
slides/kernel-frameworks/kernel-frameworks.tex | 2 +-
slides/kernel-input/kernel-input.tex | 2 +-
slides/kernel-misc-subsystem/kernel-misc-subsystem.tex | 2 +-
slides/kernel-porting-content/kernel-porting-content.tex | 2 +-
.../sysdev-application-development.tex | 2 +-
slides/sysdev-busybox/sysdev-busybox.tex | 2 +-
slides/sysdev-dev-environment/sysdev-dev-environment.tex | 4 ++--
slides/sysdev-intro/sysdev-intro.tex | 4 ++--
.../sysdev-linux-intro-configuration.tex | 4 ++--
.../sysdev-linux-intro-versioning.tex | 2 +-
.../sysdev-root-filesystem-minimal.tex | 2 +-
.../sysdev-root-filesystem-principles.tex | 2 +-
24 files changed, 37 insertions(+), 37 deletions(-)
diff --git a/README b/README
index 102c6c9..b4fa573 100644
--- a/README
+++ b/README
@@ -129,7 +129,7 @@ In your ~/.emacs.el file, add the following lines:
The important point here is that this tells Emacs to consider the
\code{} and \url{} macros as a verbatim macro, so that even if special
-characters such as $, _ or % are not escaped inside those macros,
+characters such as $, _ or % are not escaped inside these macros,
Emacs text colorization will not go crazy.
Nice keyboard shortcuts with AUCTex:
@@ -187,7 +187,7 @@ to look at.
borders: #CC1F1A
background: #FFACAC
-If you want to easily add all those colors to Dia, add the following
+If you want to easily add all these colors to Dia, add the following
fragment to ~/.dia/persistence (or replace the existing
role="color-menu" XML tag) :
diff --git a/agenda/kernel-agenda.tex b/agenda/kernel-agenda.tex
index 1094ed0..b493cdb 100644
--- a/agenda/kernel-agenda.tex
+++ b/agenda/kernel-agenda.tex
@@ -156,7 +156,7 @@ Embedded Linux kernel and driver development training\\
\end{itemize}
While our explanations will be focused on specifically the Linux
- subsystems needed to implement those drivers, they will always be
+ subsystems needed to implement these drivers, they will always be
generic enough to convey the general design philosophy of the Linux
kernel. The information learnt will therefore apply beyond just
I2C, input or memory-mapped devices.
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index b51e59e..fc3fbc8 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -263,7 +263,7 @@ kernel, we're going to build the libraries and modules, and store them
in our device folder.
We're then going to add to the device configuration that the build
-system has to copy those files into the images at compilation time.
+system has to copy these files into the images at compilation time.
The first thing to do is to download the SGX drivers source code from
rowboat. Modify your local manifest to download them from
@@ -306,10 +306,10 @@ After the android logo, the screen will turn black. This is actually
the backlight turning almost off.
You can find the controls for the backlight in
-\code{/sys/class/backlight}. Play with those controls until you find
+\code{/sys/class/backlight}. Play with these controls until you find
the values that are working.
-To make those changes permanently, you will have to edit the kernel
+To make these changes permanently, you will have to edit the kernel
code. The used PWM is defined is the \code{am335xevm} board file, in
the \code{arch/arm/mach-omap2} folder. The PWM work by switching on
and off at a fast pace the power supply to be able to adjust the
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index c3f7758..55cd6c8 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -26,7 +26,7 @@ debug documentation in the kernel sources, do the following things:
\item List all available debug messages in the kernel.
\item Enable all debugging messages of your serial module, and check
- that you indeed see those messages.
+ that you indeed see these messages.
\item Enable just one single debug message in your serial module, and
check that you see just this message and not the other debug
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index ea13612..d065ca4 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -17,7 +17,7 @@ integrate this simple application to our Linux system.
Buildroot has generated toolchain wrappers in
\code{output/host/usr/bin}, which make it easier to use the toolchain,
-since those wrappers pass some mandatory flags (especially the
+since these wrappers pass some mandatory flags (especially the
\code{--sysroot} gcc flag, which tells gcc where to look for the
headers and libraries).
diff --git a/labs/sysdev-thirdparty/sysdev-thirdparty.tex b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
index dc2a179..c176717 100644
--- a/labs/sysdev-thirdparty/sysdev-thirdparty.tex
+++ b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
@@ -633,7 +633,7 @@ configure: error: Ogg >= 1.0 required !
By running \code{./configure --help}, you will find the
\code{--with-ogg-libraries} and \code{--with-ogg-includes} options.
-Use those:
+Use these:
\begin{verbatim}
CC=arm-linux-gcc ./configure --host=arm-linux --prefix=/usr \
diff --git a/slides/android-build-system-basics-envsetup/android-build-system-basics-envsetup.tex b/slides/android-build-system-basics-envsetup/android-build-system-basics-envsetup.tex
index 89762b2..6efd813 100644
--- a/slides/android-build-system-basics-envsetup/android-build-system-basics-envsetup.tex
+++ b/slides/android-build-system-basics-envsetup/android-build-system-basics-envsetup.tex
@@ -5,8 +5,8 @@
\begin{itemize}
\item Obviously modifies the current environment, that's why we have
to \code{source} it
- \item It adds a lot of useful shell macro
- \item Those macros will serve several purposes:
+ \item It adds many useful shell macros
+ \item These macros will serve several purposes:
\begin{itemize}
\item Configure and setup the build system
\item Ease the navigation in the source code
diff --git a/slides/android-build-system-basics-results/android-build-system-basics-results.tex b/slides/android-build-system-basics-results/android-build-system-basics-results.tex
index 50a9f8f..ed7ecf5 100644
--- a/slides/android-build-system-basics-results/android-build-system-basics-results.tex
+++ b/slides/android-build-system-basics-results/android-build-system-basics-results.tex
@@ -44,7 +44,7 @@
line, where to load the kernel, but also the image of the kernel,
and an optional initramfs image
\item A custom \code{mkbootimg} tool is used by Android to generate
- those images at compilation time from the kernel and the system
+ these images at compilation time from the kernel and the system
it's generating
\item We can tweak the behaviour of that tool from the build system
configuration, that allows a great flexibility
diff --git a/slides/android-native-layer-toolbox/android-native-layer-toolbox.tex b/slides/android-native-layer-toolbox/android-native-layer-toolbox.tex
index 1e8bf01..f07444d 100644
--- a/slides/android-native-layer-toolbox/android-native-layer-toolbox.tex
+++ b/slides/android-native-layer-toolbox/android-native-layer-toolbox.tex
@@ -17,7 +17,7 @@
\item Various basic utilities for file manipulation and system
configuration
\end{itemize}
- \item In normal Linux systems, those programs are provided by
+ \item In normal Linux systems, these programs are provided by
different projects
\begin{itemize}
\item \code{coreutils}, \code{bash}, \code{grep}, \code{sed},
diff --git a/slides/boottime-application/boottime-application.tex b/slides/boottime-application/boottime-application.tex
index 64f54cd..4ee78c2 100644
--- a/slides/boottime-application/boottime-application.tex
+++ b/slides/boottime-application/boottime-application.tex
@@ -232,7 +232,7 @@ you'll have to benchmark near the end of your project.
Results may vary depending on the size/features of your root filesystem.
Here, we mainly benchmark the kernel performance as the root filesystem
doesn't take much time. Note: Don't compare with a Buildroot toolchain as
-those are using {\em glibc}/{\em eglibc} and not {\em uClibc} and then
+these are using {\em glibc}/{\em eglibc} and not {\em uClibc} and then
the initramfs has a quite different size. Compiling the kernel with a
Linaro toolchain and using a Buildroot generated root filesystem yields
the same results as compiling everything with Buildroot.
@@ -244,7 +244,7 @@ Group application code used at startup
\begin{itemize}
\item Find the functions called during startup, for example using
the \code{-finstrument-functions} gcc option.
- \item Create a custom linker script to reorder those functions in
+ \item Create a custom linker script to reorder these functions in
the call order. You can achieve that by putting each function
in their own section using the \code{-ffunction-sections} gcc
option.
diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 3181799..ed9a061 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -9,7 +9,7 @@
reusability} of code between platforms.
\item For example, we want the same {\em USB device driver} to be
usable on a x86 PC, or an ARM platform, even though the USB
- controllers used on those platforms are different.
+ controllers used on these platforms are different.
\item This requires a clean organization of the code, with the {\em
device drivers} separated from the {\em controller drivers}, the
hardware description separated from the drivers themselves, etc.
@@ -300,7 +300,7 @@ static int rtl8150_probe(struct usb_interface *intf,
identifiers for devices.
\item For example, the devices on I2C buses or SPI buses, or the
devices directly part of the system-on-chip.
- \item However, we still want all of those devices to be part of the
+ \item However, we still want all of these devices to be part of the
device model.
\item Such devices, instead of being dynamically detected, must be
statically described in either:
diff --git a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
index 8012bdd..73dcefd 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -35,12 +35,12 @@
\frametitle{pr\_debug() and dev\_dbg()}
\begin{itemize}
\item When the driver is compiled with \code{DEBUG} defined, all
- those messages are compiled and printed at the debug level.
+ these messages are compiled and printed at the debug level.
\code{DEBUG} can be defined by {\tt \#define DEBUG} at the
beginning of the driver, or using
\code{ccflags-$(CONFIG_DRIVER) += -DDEBUG} in the \code{Makefile}
\item When the kernel is compiled with \code{CONFIG_DYNAMIC_DEBUG},
- then those messages can dynamically be enabled on a per-file,
+ then these messages can dynamically be enabled on a per-file,
per-module or per-message basis
\begin{itemize}
\item See \kerneldoc{dynamic-debug-howto.txt} for details
@@ -48,7 +48,7 @@
interested in.
\end{itemize}
\item When \code{DEBUG} is not defined and
- \code{CONFIG_DYNAMIC_DEBUG} is not enabled, those messages are not
+ \code{CONFIG_DYNAMIC_DEBUG} is not enabled, these messages are not
compiled in.
\end{itemize}
\end{frame}
@@ -224,10 +224,10 @@
\begin{itemize}
\item Two types of JTAG dongles
\begin{itemize}
- \item Those offering a \code{gdb} compatible interface, over a
+ \item The ones offering a \code{gdb} compatible interface, over a
serial port or an Ethernet connection. \code{gdb} can directly
connect to them.
- \item Those not offering a gdb compatible interface are generally
+ \item The ones not offering a gdb compatible interface are generally
supported by OpenOCD (Open On Chip Debugger):
\url{http://openocd.sourceforge.net/}
\begin{itemize}
diff --git a/slides/kernel-frameworks/kernel-frameworks.tex b/slides/kernel-frameworks/kernel-frameworks.tex
index e1738f0..b9be039 100644
--- a/slides/kernel-frameworks/kernel-frameworks.tex
+++ b/slides/kernel-frameworks/kernel-frameworks.tex
@@ -36,7 +36,7 @@
as {\em device files} in \code{/dev}.
\end{itemize}
$\rightarrow$ Most devices are {\em character devices}, so we will
- study those in more details.
+ study these in more details.
\end{frame}
\begin{frame}
diff --git a/slides/kernel-input/kernel-input.tex b/slides/kernel-input/kernel-input.tex
index b2f3a9f..d743f83 100644
--- a/slides/kernel-input/kernel-input.tex
+++ b/slides/kernel-input/kernel-input.tex
@@ -91,7 +91,7 @@ struct input_dev {
\item Depending on the type of event that will be generated, the
input bit fields \code{evbit} and \code{keybit} must be configured:
For example, for a button we only generate
- \ksym{EV_KEY} type events, and from those only \ksym{BTN_0} events
+ \ksym{EV_KEY} type events, and from these only \ksym{BTN_0} events
code:
\begin{block}{}
\begin{minted}[fontsize=\footnotesize]{c}
diff --git a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
index 1c8aa8f..939b0bf 100644
--- a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
+++ b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
@@ -6,7 +6,7 @@
a wide range of device types: input, network, video, audio,
etc.
\begin{itemize}
- \item Those frameworks allow to factorize common functionality
+ \item These frameworks allow to factorize common functionality
between drivers and offer a consistent API to user space
applications.
\end{itemize}
diff --git a/slides/kernel-porting-content/kernel-porting-content.tex b/slides/kernel-porting-content/kernel-porting-content.tex
index 031523d..2fe8ee4 100644
--- a/slides/kernel-porting-content/kernel-porting-content.tex
+++ b/slides/kernel-porting-content/kernel-porting-content.tex
@@ -36,7 +36,7 @@
\item \code{mach-*} directories: \code{mach-pxa} for PXA CPUs,
\code{mach-imx} for Freescale iMX CPUs, etc.
\begin{itemize}
- \item Before the ARM cleanup, those directories contained
+ \item Before the ARM cleanup, these directories contained
support for the SoC family (GPIO, clocks, pinmux, power
management, interrupt controller, etc.) and for the various
boards.
diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index b6d5a03..e082dc1 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -252,7 +252,7 @@ clean:
\item {\bf CodeBlocks} is also quite popular, since it's also
available on the Windows platform.
\end{itemize}
- All those editors are available in most Linux distributions, simply
+ All these editors are available in most Linux distributions, simply
install them and try them out!
\column{0.4\textwidth}
{\small Vim \\
diff --git a/slides/sysdev-busybox/sysdev-busybox.tex b/slides/sysdev-busybox/sysdev-busybox.tex
index 90ba84f..1d42414 100644
--- a/slides/sysdev-busybox/sysdev-busybox.tex
+++ b/slides/sysdev-busybox/sysdev-busybox.tex
@@ -10,7 +10,7 @@
\item Various basic utilities for file manipulation and system
configuration
\end{itemize}
- \item In normal Linux systems, those programs are provided by
+ \item In normal Linux systems, these programs are provided by
different projects
\begin{itemize}
\item \code{coreutils}, \code{bash}, \code{grep}, \code{sed},
diff --git a/slides/sysdev-dev-environment/sysdev-dev-environment.tex b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
index 42352e2..5b67742 100644
--- a/slides/sysdev-dev-environment/sysdev-dev-environment.tex
+++ b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
@@ -27,7 +27,7 @@
system to embedded Linux developers, for multiple reasons.
\item All community tools are developed and designed to run on
Linux. Trying to use them on other operating systems (Windows, Mac
- OS X) will lead to trouble, and their usage on those systems is
+ OS X) will lead to trouble, and their usage on these systems is
generally not supported by community developers.
\item As Linux also runs on the embedded device, all the knowledge
gained from using Linux on the desktop will apply similarly to the
@@ -72,7 +72,7 @@
the network, creating device files, changing the system
configuration, installing or removing software
\item All {\bf other users are unprivileged}, and cannot perform
- those administrator-level operations
+ these administrator-level operations
\end{itemize}
\item On an Ubuntu system, it is not possible to log in as
\code{root}, only as a normal user.
diff --git a/slides/sysdev-intro/sysdev-intro.tex b/slides/sysdev-intro/sysdev-intro.tex
index 3de94f0..ab66d6c 100644
--- a/slides/sysdev-intro/sysdev-intro.tex
+++ b/slides/sysdev-intro/sysdev-intro.tex
@@ -29,7 +29,7 @@
\item Freedom to redistribute copies
\item Freedom to distribute copies of modified versions
\end{itemize}
- \item Those freedoms are granted for both commercial and
+ \item These freedoms are granted for both commercial and
non-commercial use
\item They imply the availability of source code, software can be
modified and distributed to customers
@@ -283,7 +283,7 @@
access all other peripherals. Can be used to build end products
for small to medium quantities.
\item {\bf Community development platforms}, a new trend to make a
- particular SoC popular and easily available. Those are
+ particular SoC popular and easily available. These are
ready-to-use and low cost, but usually have less peripherals than
evaluation platforms. To some extent, can also be used for real
products.
diff --git a/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex b/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
index 3f004c6..4a3f85a 100644
--- a/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
+++ b/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
@@ -77,7 +77,7 @@
\item Some features (device drivers, filesystems, etc.) can however
be compiled as {\bf modules}
\begin{itemize}
- \item Those are {\em plugins} that can be loaded/unloaded dynamically to
+ \item These are {\em plugins} that can be loaded/unloaded dynamically to
add/remove features to the kernel
\item Each {\bf module is stored as a separate file in the
filesystem}, and therefore access to a filesystem is mandatory
@@ -124,7 +124,7 @@
\item \code{select} dependencies. In this case, with option A
depending on option B, when option A is enabled, option B is
automatically enabled
- \item \code{make xconfig} allows to see all options, even those
+ \item \code{make xconfig} allows to see all options, even the ones
that cannot be selected because of missing dependencies. In this
case, they are displayed in gray
\end{itemize}
diff --git a/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex b/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
index 3fff865..f7b2cee 100644
--- a/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
+++ b/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
@@ -117,7 +117,7 @@ Date: Wed Jul 13 11:29:17 2011 +0200
Several USB power switches (AIC1526 or MIC2026) have a digital output
that is used to notify that an overcurrent situation is taking
place. This digital outputs are typically connected to GPIO inputs of
- the processor and can be used to be notified of those overcurrent
+ the processor and can be used to be notified of these overcurrent
situations.
Therefore, we add a new overcurrent_pin[] array in the at91_usbh_data
diff --git a/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex b/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
index c389a64..58aaf6f 100644
--- a/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
+++ b/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
@@ -22,7 +22,7 @@
\item Basic Unix applications, to copy files, move files, list files
(commands like \code{mv}, \code{cp}, \code{mkdir}, \code{cat},
etc.)
- \item Those basic components have to be integrated into the root
+ \item These basic components have to be integrated into the root
filesystem to make it usable
\end{itemize}
\end{frame}
diff --git a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
index 59ff432..15414a5 100644
--- a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
+++ b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
@@ -59,7 +59,7 @@
\begin{itemize}
\item This is needed before rebooting, or before unplugging a USB
key, because the Linux kernel caches writes in memory to
- increase performance. \code{umount} makes sure that those writes are
+ increase performance. \code{umount} makes sure that these writes are
committed to the storage.
\end{itemize}
\end{itemize}
More information about the training-materials-updates
mailing list