From 586db5b9428b2fa3084789c67622f0e39a3f54d4 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Tue, 28 Jan 2025 15:40:53 -0500 Subject: [PATCH] spelling: separate Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- .../recovery_first_use_app/getting_started_button_combo.h | 2 +- src/fw/console/dbgserial_input.c | 4 ++-- src/fw/drivers/rtc.h | 4 ++-- src/fw/services/normal/data_logging/dls_list.h | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) 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 a440a42d..d8f7d294 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 @@ -32,7 +32,7 @@ //! The reason it's not just a boring set of long click handlers is because we don't support //! 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 +//! I tried to split this out from a separate file from the recovery_first_use.c file so I could //! 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. diff --git a/src/fw/console/dbgserial_input.c b/src/fw/console/dbgserial_input.c index b2d2c33f..bb745d12 100644 --- a/src/fw/console/dbgserial_input.c +++ b/src/fw/console/dbgserial_input.c @@ -36,7 +36,7 @@ static void dbgserial_interrupt_handler(bool *should_context_switch); static DbgSerialCharacterCallback s_character_callback; static TimerID s_stop_mode_timeout_timer; -//! Use a seperate variable so it's safe to check from the ISR. +//! Use a separate variable so it's safe to check from the ISR. static bool s_stop_mode_inhibited = false; //! We DMA into this buffer as a circular buffer @@ -64,7 +64,7 @@ static bool prv_uart_irq_handler(UARTDevice *dev, uint8_t data, const UARTRXErro void dbgserial_input_init(void) { exti_configure_pin(BOARD_CONFIG.dbgserial_int, ExtiTrigger_Falling, dbgserial_interrupt_handler); - // some platforms have a seperate pin for the EXTI int and the USART + // some platforms have a separate pin for the EXTI int and the USART if (BOARD_CONFIG.dbgserial_int_gpio.gpio != NULL) { gpio_input_init(&BOARD_CONFIG.dbgserial_int_gpio); } diff --git a/src/fw/drivers/rtc.h b/src/fw/drivers/rtc.h index 3a2b0e4b..e0eeff1e 100644 --- a/src/fw/drivers/rtc.h +++ b/src/fw/drivers/rtc.h @@ -30,11 +30,11 @@ typedef uint64_t RtcTicks; void rtc_init(void); //! Calibrate the RTC driver using the given crystal frequency (in mHz). -//! This is a seperate step because rtc_init needs to run incredibly early in the startup process +//! This is a separate step because rtc_init needs to run incredibly early in the startup process //! and the manufacturing registry won't be initialized yet. void rtc_calibrate_frequency(uint32_t frequency); -//! Initialize any timers the RTC driver may need. This is a seperate step than rtc_init because +//! Initialize any timers the RTC driver may need. This is a separate step than rtc_init because //! rtc_init needs to run incredibly early in the startup process and at that time the timer //! system won't be initialized yet. void rtc_init_timers(void); diff --git a/src/fw/services/normal/data_logging/dls_list.h b/src/fw/services/normal/data_logging/dls_list.h index 5f7966a0..2266eec0 100644 --- a/src/fw/services/normal/data_logging/dls_list.h +++ b/src/fw/services/normal/data_logging/dls_list.h @@ -40,7 +40,7 @@ void dls_list_insert_session(DataLoggingSession *logging_session); //! Creates a new DataLoggingSession object that is only initialized with the parameters given. The //! session will only be initialized with the given parameters. The .storage and .comm members must -//! be seperately initialized. Also, the resulting object will need to be added to the list of +//! be separately initialized. Also, the resulting object will need to be added to the list of //! sessions using one of dls_list_add_new_session and dls_list_insert_session. May return NULL if //! we've created too many sessions. DataLoggingSession *dls_list_create_session(uint32_t tag, DataLoggingItemType type, uint16_t size,