Update docs/source/carrierboard_development.rst

Co-authored-by: barsnick <barsnick@users.noreply.github.com>

Author: mhei

docs/source/carrierboard_development.rst

@@ -101,7 +101,7 @@ Additional notes regarding the content:
   little-endianess) for its boards. Customers can choose arbitrary values ​​here, but it is recommended (though not
   mandatory) to coordinate the value with chargebyte. If desired, chargebyte can also record such values here in this
   documentation.
-- As example, chargegyte will use the vendor specific part to store a hardware board revision and an order code
+- As example, chargebyte will use the vendor specific part to store a hardware board revision and an order code
   of this board model. It can be accessed in the field later by the firmware for debugging and/or maintainance purpose.
   Customers might have their own requirements to store individual board specific, or general product information.
 - The header check in U-Boot will be very simple for the moment: only the CRC32 is validated and when it is correct,