spelling: retrieve

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

src/fw/applib/graphics/gcontext.h

@@ -231,7 +231,7 @@ GSize graphics_context_get_framebuffer_size(GContext *ctx);
 
 //! @internal
 //! Retreives the destination bitmap for the graphics context.
-//! @param ctx The graphics context to retreive the bitmap for.
+//! @param ctx The graphics context to retrieve the bitmap for.
 GBitmap* graphics_context_get_bitmap(GContext* ctx);
 
 //! @internal

src/fw/drivers/flash.h

@@ -35,7 +35,7 @@ void flash_init(void);
 void flash_stop(void);
 
 /**
- * Retreieve the first 3 bytes of the flash's device id. This ID
+ * Retrieve the first 3 bytes of the flash's device id. This ID
  * should remain fixed across all chips.
  */
 uint32_t flash_whoami(void);

src/fw/process_management/pebble_process_md.h

@@ -64,7 +64,7 @@ typedef enum {
 //! This structure is used internally to describe the process. This struct here is actually a polymorphic base
 //! class, and can be casted to either \ref PebbleProcessMdSystem or \ref PebbleProcessMdFlash depending on the value
 //! of \ref is_flash_based. Clients shouldn't do this casting themselves though, and instead should use the
-//! process_metadata_get_* functions to safely retreive values from this struct.
+//! process_metadata_get_* functions to safely retrieve values from this struct.
 typedef struct PebbleProcessMd {
   Uuid uuid;
 

src/fw/util/shared_circular_buffer.h

@@ -74,7 +74,7 @@ void shared_circular_buffer_remove_client(SharedCircularBuffer* buffer, SharedCi
 //!
 //! If the circular buffer wraps in the middle of the requested data, this function call will return true but will
 //! provide fewer bytes that requested. When this happens, the length_out parameter will be set to a value smaller
-//! than length. A second read call can be made with the remaining smaller length to retreive the rest.
+//! than length. A second read call can be made with the remaining smaller length to retrieve the rest.
 //!
 //! The reason this read doesn't consume is to avoid having to copy out the data. The data_out pointer should be
 //! stable until you explicitly ask for it to be consumed with circular_buffer_consume.

src/libutil/includes/util/circular_buffer.h

@@ -68,7 +68,7 @@ void circular_buffer_write_finish(CircularBuffer *buffer, uint16_t written_lengt
 //!
 //! If the circular buffer wraps in the middle of the requested data, this function call will return true but will
 //! provide fewer bytes that requested. When this happens, the length_out parameter will be set to a value smaller
-//! than length. A second read call can be made with the remaining smaller length to retreive the rest.
+//! than length. A second read call can be made with the remaining smaller length to retrieve the rest.
 //!
 //! The reason this read doesn't consume is to avoid having to copy out the data. The data_out pointer should be
 //! stable until you explicitly ask for it to be consumed with circular_buffer_consume.

tests/fw/services/settings/test_settings_file.c

@@ -405,7 +405,7 @@ static RecordResult write_and_change_record_aborting_after_bytes(int after_n_byt
       return RecordResultNew;
     }
     // Should not get here! This means that neither the old nor the new value
-    // could be retreived, and thus the atomicity is broken! Aaaaaaaaaaaaaah!!
+    // could be retrieved, and thus the atomicity is broken! Aaaaaaaaaaaaaah!!
     cl_assert(false);
   }
   fake_spi_flash_force_future_failure(after_n_bytes, &jmp);