From 808be075ae1a2d76dec983c72cb43f301ee985f0 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Tue, 28 Jan 2025 15:13:36 -0500
Subject: [PATCH] spelling: necessarily

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
 src/fw/services/normal/data_logging/dls_syscalls.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/fw/services/normal/data_logging/dls_syscalls.c b/src/fw/services/normal/data_logging/dls_syscalls.c
index 6bdf1f52..2fa6e75d 100644
--- a/src/fw/services/normal/data_logging/dls_syscalls.c
+++ b/src/fw/services/normal/data_logging/dls_syscalls.c
@@ -31,7 +31,7 @@ DEFINE_SYSCALL(DataLoggingSessionRef, sys_data_logging_create, uint32_t tag,
 
 DEFINE_SYSCALL(void, sys_data_logging_finish, DataLoggingSessionRef session_ref) {
   // TODO: It would be nice to verify the session itself, because they could be
-  // passing us any memory address (not necesarilly a valid DataLoggingSession).
+  // passing us any memory address (not necessarily a valid DataLoggingSession).
   // An evil developer could potentially use this to confuse the data_logging
   // logic, and do evil things with kernel rights. However, it's pretty unlikely
   // (especially since our executable code lives in microflash, and hence can't