labs/sysdev lab: fix typos

Replace "straighforward" with "straightforward" Signed-off-by: Nasser Afshin <[email protected]> Signed-off-by: Michael Opdenacker <[email protected]>
bootlin · Dec 1, 2023 · ffd6035 · ffd6035
1 parent 0522a0e
commit ffd6035
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/labs/kernel-i2c-describing-hardware/kernel-i2c-describing-hardware.tex b/labs/kernel-i2c-describing-hardware/kernel-i2c-describing-hardware.tex
@@ -146,7 +146,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 suppose that:
+That's not completely straightforward, 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/kernel-i2c-input-interface/kernel-i2c-input-interface.tex b/labs/kernel-i2c-input-interface/kernel-i2c-input-interface.tex
@@ -271,7 +271,7 @@ \subsubsection{Extend your driver}
 \sourcecode{labs/kernel-i2c-input-interface/declare-classic-buttons.c}
 
 The next thing to do is to retrieve and report the joystick X and Y
-coordinates in the polling routine. This should be very straighforward.
+coordinates in the polling routine. This should be very straightforward.
 You will just need to go back to the nunchuk datasheet to find out
 which bytes contain the X and Y values.
 

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 suppose that:
+That's not completely straightforward, 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 suppose that:
+That's not completely straightforward, 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
@@ -194,7 +194,7 @@ \section{Understanding automatic module loading with Udev}
 \end{verbatim}
 
 For \code{snd_usb_audio}, there are many possible matching values,
-so it's not straighforward to be sure which matched your particular
+so it's not straightforward to be sure which matched your particular
 device.
 
 However, you can find in {\em sysfs} which \code{MODALIAS}