Update docs/source/carrierboard_development.rst

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

Author: mhei

docs/source/carrierboard_development.rst

@@ -118,7 +118,7 @@ using e.g. ``openssl cms …`` and thus creating a *detached* signature of the b
 To keep the DT overlay signature small, the certificate could be *not* included in this signature (and thus not stored
 inside the EEPROM), but to verify this signature, accessing the signing certificate must then be possible (e.g. placed in
 and loaded from the root filesystem). This raises other topics, so chargebyte's start point is to include it as
-complete X.509 signature in the EEPROM even if this requires a larger EEPROM type.
+a complete X.509 signature in the EEPROM even if this requires a larger EEPROM type.
 
 Such a signature can be created for example using the following command line: