bootlin · michaelopdenacker · Nov 15, 2023 · Oct 19, 2023 · Oct 19, 2023 · Oct 19, 2023
diff --git a/labs/sysdev-accessing-hardware-bbb/sysdev-accessing-hardware-bbb.tex b/labs/sysdev-accessing-hardware-bbb/sysdev-accessing-hardware-bbb.tex
@@ -285,7 +285,7 @@ \subsection{Enabling an I2C bus}
 lrwxrwxrwx    1         0 Jan  1 00:59 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/ocp/48000000.interconnect/48000000.interconnect:segment@100000/4819c000.target-module/4819c000.i2c/i2c-2
 \end{bashinput}
 
-That's not completely straighforward, but you can supposed that:
+That's not completely straighforward, but you can suppose that:
 \begin{itemize}
 \item I2C0 is at address \code{0x44e0b000}
 \item I2C2 is at address \code{0x4819c000}

diff --git a/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex b/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
@@ -298,7 +298,7 @@ \subsection{Enabling an I2C bus}
 lrwxrwxrwx    1 root     root             0 Jan  1 02:02 /sys/bus/i2c/devices/i2c-5 -> ../../../devices/platform/bus@f0000/bus@f0000:bus@4000000/4900000.i2c/i2c-5
 \end{bashinput}
 
-That's not completely straighforward, but you can supposed that:
+That's not completely straighforward, but you can suppose that:
 \begin{itemize}
 \item I2C0 is at address \code{0x20000000}
 \item I2C1 is at address \code{0x20010000}

diff --git a/labs/sysdev-system-integration/sysdev-system-integration.tex b/labs/sysdev-system-integration/sysdev-system-integration.tex
@@ -220,7 +220,7 @@ \section{Understanding automatic module loading with Udev}
 
 Then plug in your headset again. You will find all the events emitted
 by the kernel, and with the same string (with \code{UDEV} instead of
-\code{KERNEL}, the time when {\em Udev} finished processing each event.
+\code{KERNEL}), the time when {\em Udev} finished processing each event.
 
 You can also see the \code{MODALIAS} values carried by these events:
 

diff --git a/labs/sysdev-u-boot-bbb/sysdev-u-boot-bbb.tex b/labs/sysdev-u-boot-bbb/sysdev-u-boot-bbb.tex
@@ -189,7 +189,7 @@ \section{Preparing a bootable micro-SD card}
 than 2 TB.
 
 In the \code{cfdisk} interface, delete existing partitions, then
-create only one primary partition, starting from the
+create only one primary partition, starting from the beginning, with the 
 following properties:
 
 \begin{itemize}

diff --git a/slides/boot-time-c-libraries/boot-time-c-libraries.tex b/slides/boot-time-c-libraries/boot-time-c-libraries.tex
@@ -129,7 +129,7 @@
 \end{frame}
 
 \begin{frame}
-  \frametitle{Advise for choosing the C library}
+  \frametitle{Advice for choosing the C library}
   \begin{itemize}
   \item Advice to start developing and debugging your applications with
         {\em glibc}, which is the most standard solution, and is best

diff --git a/slides/initramfs/initramfs.tex b/slides/initramfs/initramfs.tex
@@ -12,8 +12,8 @@
       filesystem is completely loaded at boot time, application
       startup is very fast.
     \item As an intermediate step before switching to a real root
-      filesystem, located on devices for which drivers not part of the
-      kernel image are needed (storage drivers, filesystem drivers,
+      filesystem, located on devices for which drivers are not part of the
+      kernel image (storage drivers, filesystem drivers,
       network drivers). This is always used on the kernel of
       desktop/server distributions to keep the kernel image size
       reasonable.

diff --git a/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex b/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
@@ -176,7 +176,7 @@ \subsection{The U-boot bootloader}
   \begin{itemize}
   \item The {\em Device Tree} is a data structure that describes the
     topology of the hardware
-  \item Allows software to known which hardware peripherals are
+  \item Allows software to know which hardware peripherals are
     available and how they are connected to the system
   \item Initially mainly used by Linux, now also used by U-Boot,
     Barebox, TF-A, etc.
@@ -835,7 +835,7 @@ \subsection{The U-boot bootloader}
 	don't overlap in memory.
   \item Interestingly, relies on the {\em Device Tree Compiler}
     \begin{itemize}
-    \item \code{.its} file describe the contents of the image
+    \item \code{.its} file describes the contents of the image
     \item Device Tree Compiler compiles it into an \code{.itb}
     \end{itemize}
   \item U-Boot can load an \code{.itb} image and use its different

diff --git a/slides/sysdev-kernel-building/sysdev-kernel-building.tex b/slides/sysdev-kernel-building/sysdev-kernel-building.tex
@@ -467,7 +467,7 @@ \subsection{Compiling and installing the kernel}
       Tells which module a given symbol belongs to (related to
       module dependencies).
     \item \code{modules.builtin}\\
-      List of modules that are builtin the kernel.
+      List of built-in modules of the kernel.
     \end{itemize}
   \end{itemize}
 \end{frame}

diff --git a/slides/sysdev-toolchains-definition/sysdev-toolchains-definition.tex b/slides/sysdev-toolchains-definition/sysdev-toolchains-definition.tex
@@ -106,7 +106,7 @@ \subsection{Definition and Components}
   \begin{columns}
     \column{0.7\textwidth}
     \begin{itemize}
-    \item The C standard library and compiled programs needs to interact with the kernel
+    \item The C standard library and compiled programs need to interact with the kernel
       \begin{itemize}
       \item Available system calls and their numbers
       \item Constant definitions
@@ -295,7 +295,7 @@ \subsection{Definition and Components}
 \end{frame}
 
 \begin{frame}
-  \frametitle{Advise for choosing the C standard library}
+  \frametitle{Advice for choosing the C standard library}
   \begin{itemize}
   \item Advice to start developing and debugging your applications
     with {\em glibc}, which is the most standard solution