From 120c7e248c6419242fbbe85561cadc074f0eaae8 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Tue, 28 Jan 2025 15:50:23 -0500
Subject: [PATCH] spelling: traditional

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
 src/fw/apps/system_apps/timeline/text_node.h   | 2 +-
 src/fw/popups/bluetooth_pairing_ui.c           | 2 +-
 src/fw/services/normal/timeline/layout_layer.h | 2 +-
 src/fw/util/mbuf.h                             | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/fw/apps/system_apps/timeline/text_node.h b/src/fw/apps/system_apps/timeline/text_node.h
index dae72e95..67d9588a 100644
--- a/src/fw/apps/system_apps/timeline/text_node.h
+++ b/src/fw/apps/system_apps/timeline/text_node.h
@@ -102,7 +102,7 @@ struct GTextNode {
   //! adjusts the bottom-right margin, causing extra space to be between this node and nodes to the
   //! bottom and/or right.
   //!
-  //! Used in-conjunction with offset, many of the normal layout position behavior in tradditional
+  //! Used in-conjunction with offset, many of the normal layout position behavior in traditional
   //! systems can be achieved. Below are diagrams of a node (denoted with Xs) with its boundary
   //! increased by `a`, a certain length.
   //!
diff --git a/src/fw/popups/bluetooth_pairing_ui.c b/src/fw/popups/bluetooth_pairing_ui.c
index 4d7c80b2..a7bf0813 100644
--- a/src/fw/popups/bluetooth_pairing_ui.c
+++ b/src/fw/popups/bluetooth_pairing_ui.c
@@ -145,7 +145,7 @@ static void prv_update_prf_info_text_layers_text(BTPairingUIData *data) {
     { "Associare?",  font_key_default }, // Italian
     { "Emparelhar?", font_key_default }, // Portuguese
     { "ペアリング",  font_key_japanese }, // Japanese
-    { "配对",        font_key_default }, // Chinese (tradditional?)
+    { "配对",        font_key_default }, // Chinese (traditional?)
     { "配對",        font_key_default }  // Chinese (simplified?)
   };
 
diff --git a/src/fw/services/normal/timeline/layout_layer.h b/src/fw/services/normal/timeline/layout_layer.h
index 923e5b90..9e07e091 100644
--- a/src/fw/services/normal/timeline/layout_layer.h
+++ b/src/fw/services/normal/timeline/layout_layer.h
@@ -31,7 +31,7 @@ typedef enum {
 
 //! LayoutLayer is a type of Layer that is used to display templated 3.0 content
 //! including \ref TimelineItem (pins, reminders, notifications) as well as AppFaces.
-//! LayoutLayers depart from tradditional Layers in a few meaningful way.
+//! LayoutLayers depart from traditional Layers in a few meaningful way.
 //! 1) LayoutLayers are modulated by a "mode", which is the context in which the LayoutLayer
 //! is displayed. Examples of modes are the "card" mode which displays detailed pin info
 //! and the "minimized" mode which is used to display a "toast" like mode of a pin.
diff --git a/src/fw/util/mbuf.h b/src/fw/util/mbuf.h
index de02ec2f..e9e12f08 100644
--- a/src/fw/util/mbuf.h
+++ b/src/fw/util/mbuf.h
@@ -23,7 +23,7 @@
 /*
  * Generally, an mbuf is a header for a buffer which adds some useful functionality with regards to
  * grouping multiple distinct buffers together into a single packet. They are primarily used for
- * networking. As you go down a tradditional network stack, headers need to be added to the data.
+ * networking. As you go down a traditional network stack, headers need to be added to the data.
  * Rather than having to allocate and copy every time a new header needs to be added, or forcing the
  * upper layer to leave room for the header, mbufs allows for buffers to be chained together into an
  * mbuf chain. With mbufs, as you go down the stack, you simply add the headers as new mbufs at the