From 294f626792426a3a90f536015df811c7885f5e44 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Tue, 28 Jan 2025 14:49:10 -0500 Subject: [PATCH] spelling: independent Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- docs/tasks.txt | 2 +- src/fw/applib/graphics/framebuffer.c | 2 +- .../recovery_first_use_app/getting_started_button_combo.h | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tasks.txt b/docs/tasks.txt index 2b5ed8b5..e3d3841c 100644 --- a/docs/tasks.txt +++ b/docs/tasks.txt @@ -1,4 +1,4 @@ -FreeRTOS lets us create tasks, which are independant threads of execution. We create a few ourselves, and more are created internally by FreeRTOS. We have pre-emption enabled in our FreeRTOS configuration, so we must be mindful of which other tasks are mucking with the same data. This document describes the tasks that exist in our system. +FreeRTOS lets us create tasks, which are independent threads of execution. We create a few ourselves, and more are created internally by FreeRTOS. We have pre-emption enabled in our FreeRTOS configuration, so we must be mindful of which other tasks are mucking with the same data. This document describes the tasks that exist in our system. FreeRTOS Tasks ============== diff --git a/src/fw/applib/graphics/framebuffer.c b/src/fw/applib/graphics/framebuffer.c index 3939424c..5549b16d 100644 --- a/src/fw/applib/graphics/framebuffer.c +++ b/src/fw/applib/graphics/framebuffer.c @@ -15,7 +15,7 @@ */ //! @file framebuffer.c -//! Bitdepth independant routines for framebuffer.h +//! Bitdepth independent routines for framebuffer.h //! Bitdepth dependent routines can be found in the 1_bit & 8_bit folders in their //! respective framebuffer.c files. diff --git a/src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h b/src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h index 24bda27d..0a45250f 100644 --- a/src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h +++ b/src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h @@ -33,7 +33,7 @@ //! registering a long click handler for a combination of buttons like up+down. //! //! I tried to split this out from a seperate file from the recovery_first_use.c file so I could -//! test this behaviour in a unit test independant in the UI. I think it turned out /okay/. The +//! test this behaviour in a unit test independent in the UI. I think it turned out /okay/. The //! callback specification is a little odd (only for select but not for the other ones, should we //! be blowing memory on static behaviour like this?) but it was worth a shot.