Update docs/source/carrierboard_development.rst

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

Author: mhei

docs/source/carrierboard_development.rst

@@ -95,7 +95,7 @@ Additional notes regarding the content:
   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 also be used for customer specific data. The C structure reflects what chargebyte
-  is going to use as example.
+  is going to use as an 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
   little-endianess) for its boards. Customers can choose arbitrary values ​​here, but it is recommended (though not