[bootlin/training-materials updates] master: labs/sysdev-accessing-hardware-beagleplay: typo and style fixes (6a415279)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/6a415279bca33190861e48168097265be03c8056

>---------------------------------------------------------------

commit 6a415279bca33190861e48168097265be03c8056
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Jul 28 10:21:21 2023 +0200

    labs/sysdev-accessing-hardware-beagleplay: typo and style fixes
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

6a415279bca33190861e48168097265be03c8056
 .../sysdev-accessing-hardware-beagleplay.tex       | 31 +++++++++++-----------
 1 file changed, 16 insertions(+), 15 deletions(-)

diff --git a/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex b/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
index 9789e36a..6313e633 100644
--- a/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
+++ b/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
@@ -102,9 +102,9 @@ The first thing to do is to enable this legacy interface by enabling
 \kconfig{CONFIG_GPIO_SYSFS} in the kernel configuration.
 To do so, in recent linux kernel versions the \kconfig{CONFIG_EXPERT}
 needs to be enable to have access to some legacy options and in our
-case to \kconfig{CONFIG_GPIO_SYSFS}
+case to \kconfig{CONFIG_GPIO_SYSFS}.
 
-Also make sure{\em Debugfs} is enabled (\kconfig{CONFIG_DEBUG_FS} and
+Also make sure {\em Debugfs} is enabled (\kconfig{CONFIG_DEBUG_FS} and
 \kconfig{CONFIG_DEBUG_FS_ALLOW_ALL}).
 
 After rebooting the new kernel, the first thing to do is to mount
@@ -125,8 +125,8 @@ We are going to use one of the MIKROBUS connector of the board,
 
 Take one of the M-M breadboard wires provided by your instructor and:
 \begin{itemize}
-  \item Connect one end to \code{INT} pin of the \code{MIKROBUS} connector
-  \item Connect the other end to \code{GND} pin of the \code{MIKROBUS} connector
+  \item Connect one end to the \code{INT} pin of the \code{MIKROBUS} connector
+  \item Connect the other end to the \code{GND} pin of the \code{MIKROBUS} connector
 \end{itemize}
 
 \includegraphics[width=\textwidth]{labs/sysdev-accessing-hardware-beagleplay/System-Block-Diagram.png}
@@ -140,8 +140,8 @@ Referring to the upper image, we could also have chosen \code{PWM}, \code{AN}
 or \code{RST} pin to do this lab, because there are all GPIOs.
 
 Now that we've selected our pin on the board, we need to know where it
-is connected on the SoC. To do so BeagleBoard provide us the schematics 
-of the mikrobus header we are using:
+is connected on the SoC. To do so BeagleBoard.org provides us with the schematics
+of the Mikrobus header we are using:
 
 \includegraphics[width=\textwidth]{labs/sysdev-accessing-hardware-beagleplay/mikroBUS1.png}
 {\small Source: \url{https://docs.beagleboard.org/latest/boards/beagleplay/03-design.html}}
@@ -182,7 +182,7 @@ And check its value:
 
 The value should be \code{0} as the pin is connected to a ground level.
 
-Now, let's connect our GPIO pin to \code{+3.3V} pin.
+Now, let's connect our GPIO pin to the \code{+3.3V} pin.
 
 Let's check the value again:
 
@@ -273,7 +273,7 @@ busses available through different connectors:
 
 The AM62x SoC has 3 others I2C controllers but are not used on
 the BeaglePlay board. However because the default device-tree
-we are using enables all the I2C controllers except one, we except
+we are using enables all the I2C controllers except one, we expect
 to see 5 busses to be detected by the kernel, let's check this,
 
 \begin{bashinput}
@@ -317,7 +317,7 @@ datasheet}, in the \code{Memory Map} section:
 \item I2C2 is indeed at address \code{0x20020000}
 \item I2C3 is indeed at address \code{0x20030000}
 \item I2C4 doesn't exist in datasheet but corresponds to
-      WKUP\_I2C0 at address \code{0x2B200000}
+      WKUP\_I2C0 at address \code{0x2b200000}
 \item I2C5 doesn't exist in datasheet but corresponds to
       MCU\_I2C0 at address \code{0x04900000}
 \end{itemize}
@@ -325,12 +325,12 @@ datasheet}, in the \code{Memory Map} section:
 So, we are lucky that the first 4 Linux I2C names corresponds to the first 4
 datasheet names.
 
-In this Labs we will be using the I2C3 to connect the nunchuk
+In this lab we will be using the I2C3 bus to connect the nunchuk
 because it is located on the MIKROBUS connector and is easily
 accessible.
 
-However because this I2C controller is already enable, we will
-first play with the I2C4 (WKUP\_I2C0 in datasheet) and demonstrate
+However because this I2C controller is already enabled, we will
+first play with I2C4 (WKUP\_I2C0 in datasheet) and demonstrate
 how to enable it, even we don't use I2C4 in the rest of the labs.
 
 \subsection{Customizing the Device Tree}
@@ -546,10 +546,11 @@ Go back to the kernel source directory.
 The Linux kernel has a generic driver supporting all USB audio devices
 supporting the standard USB audio class. This driver can be enabled
 using the \kconfig{CONFIG_SND_USB_AUDIO} configuration option. Look
-for this parameter in the kernel configuration, and enable it.
+for this parameter in the kernel configuration, and configure it
+as a module.
 
-So, instead of compiling the corresponding driver as a built-in, that's
-a good opportunity to practice with kernel modules.
+So, instead of compiling the corresponding driver as a built-in as
+we did before, that's a good opportunity to practice with kernel modules.
 
 So, compile your modules:
 \begin{bashinput}