Update docs/source/carrierboard_development.rst

mhei · barsnick · web-flow · commit ba49e6f1b394 · 2026-03-13T15:03:37.000+01:00
Co-authored-by: barsnick &lt;barsnick@users.noreply.github.com&gt;
diff --git a/docs/source/carrierboard_development.rst b/docs/source/carrierboard_development.rst
@@ -94,7 +94,7 @@ Additional notes regarding the content:
 - The ``DT offset`` can point to any location in the EEPROM. It is not required that the DT Overlay Blob starts directly
   after the header. This allows for vendors to store custom data and/or additional fields in the EEPROM.
 - The same applies to the DT Overlay Signature Blob.
-- The vendor specific header part can be used also for customer specific data. The C structure reflects what chargebyte
+- The vendor specific header part can also be used for customer specific data. The C structure reflects what chargebyte
   is going to use as example.
 - The ``Vendor Code`` can be used by customers to identify different carrier boards and/or to determine how the vendor
   specific area is structured. chargebyte will use the fixed-value 0x63624342 (ASCII “cbCB” → 0x42 0x43 0x62 0x63 in
