From f1134abde7ae26c7b008a66b1caaf6a95c510328 Mon Sep 17 00:00:00 2001
From: alrvid <126816223+alrvid@users.noreply.github.com>
Date: Wed, 19 Apr 2023 18:11:59 +0200
Subject: [PATCH] Added a missing "a"

Added a missing "a"
---
 .../boards/portenta-h7/tutorials/secure-boot/secure-boot.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/hardware/04.pro/boards/portenta-h7/tutorials/secure-boot/secure-boot.md b/content/hardware/04.pro/boards/portenta-h7/tutorials/secure-boot/secure-boot.md
index 46bb213f34..be4911ccf7 100644
--- a/content/hardware/04.pro/boards/portenta-h7/tutorials/secure-boot/secure-boot.md
+++ b/content/hardware/04.pro/boards/portenta-h7/tutorials/secure-boot/secure-boot.md
@@ -15,7 +15,7 @@ software:
 ## Introduction
 This short tutorial will guide the user through enabling the secure boot on the Portenta H7, generating custom security keys, and using them with the MCUboot bootloader.
 
-Secure boot is the process where compiled sketch is authenticated against the hardware before it is authorized to be used in the boot process. The hardware is pre-configured to authenticate code using trusted security credentials.
+Secure boot is the process where a compiled sketch is authenticated against the hardware before it is authorized to be used in the boot process. The hardware is pre-configured to authenticate code using trusted security credentials.
 
 In other words, secure boot ensures that the boot technology and operating system software are the legitimate manufacturer version and have not been altered or tampered with by any malicious actor or process.