diff --git a/labs/kernel-beagleplay-compiling-and-nfs-booting/kernel-beagleplay-compiling-and-nfs-booting.tex b/labs/kernel-beagleplay-compiling-and-nfs-booting/kernel-beagleplay-compiling-and-nfs-booting.tex
index 84cb008245..6284e5e2a0 100644
--- a/labs/kernel-beagleplay-compiling-and-nfs-booting/kernel-beagleplay-compiling-and-nfs-booting.tex
+++ b/labs/kernel-beagleplay-compiling-and-nfs-booting/kernel-beagleplay-compiling-and-nfs-booting.tex
@@ -232,7 +232,7 @@ \section{Automate the boot process}
 you power on or reset your board, you can use U-Boot's \code{bootcmd}
 environment variable:
 
-{\scriptsize
+{\footnotesize
 \begin{verbatim}
 setenv bootcmd 'tftp 0x80000000 Image.gz; tftp 0x83000000 k3-am625-beagleplay.dtb; booti 0x80000000 - 0x83000000'
 saveenv
@@ -253,18 +253,14 @@ \section{Save your kernel configuration}
 Now that you have a working (and satisfying) kernel configuration, you
 can save it under the \code{configs} folder:
 
-{\scriptsize
 \begin{verbatim}
 make savedefconfig
 cp defconfig arch/arm64/configs/beagleplay_defconfig
 \end{verbatim}
-}
 
 So if you later overwrite the \code{.config} file inadvertently, you can
 just get back to a working configuration by running:
 
-{\scriptsize
 \begin{verbatim}
 make beagleplay_defconfig
 \end{verbatim}
-}