Various minor whitespace fixes

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Author: mhei

README.rst

@@ -7,13 +7,15 @@ This documentation is hosted on Read the Docs and can be accessed at
 https://chargebyte-docs.readthedocs.io/en/latest/.
 
 
-Contents:
----------
+Contents
+--------
 
 - Charge SOM User Guide
 
-Repo initialization:
+
+Repo Initialization
 -------------------
+
 This repository is using git submodules to share documents between the user guides.
 After cloning of the project please execute the following commands:
 
@@ -22,8 +24,8 @@ git checkout everest/charge_som
 git submodule update --init --force --remote
 
 
-Building the documentation locally:
------------------------------------
+Building the Documentation Locally
+----------------------------------
 
 To build the documentation locally, you need to have Python and pip installed on your system.
 You can install the required dependencies by running the following command:
@@ -37,8 +39,8 @@ sphinx-build -a docs/source {output_directory}
 The output directory is the directory where the generated HTML files will be stored.
 
 
-Contributing:
--------------
+Contributing
+------------
 
 If you would like to contribute to the documentation, please fork the repository and create a pull
 request with your changes. Please make sure to follow the guidelines for contributing to the
@@ -56,14 +58,14 @@ documentation:
 - First letters of section and chapter titles should be capitalized (e.g. "Charge SOM User Guide")
 
 
-License:
---------
+License
+-------
 
 See the LICENSE file for license rights and limitations (Apache 2.0).
 
 
-Contact:
---------
+Contact
+-------
 
 If you have any questions or inquiries, please contact our support team at https://chargebyte.com/support.
 

docs/source/cb_energy.rst

@@ -1,8 +1,8 @@
 .. _cb_energy.rst:
 
-**********************
-CB energy
-**********************
+*********
+CB Energy
+*********
 
 .. note::
     CB Energy is currently intended only for connecting an EVerest AC charger. In the future, bi-directional

docs/source/development.rst

@@ -30,7 +30,7 @@ The following steps describe how to cross-compile a module for the Charge SOM pl
       Alternatively, if the above command does not work, you can use the following command:
 
        .. code-block:: console
-       
+
           unsquashfs -d bundle-staging <shipped_firmware>.image
 
       However, this will not verify the signature of the firmware image.
@@ -42,7 +42,7 @@ The following steps describe how to cross-compile a module for the Charge SOM pl
       sudo mkdir -p /mnt/rootfs
       sudo mount bundle-staging/core-image-minimal-chargesom.ext4 /mnt/rootfs
 
-#. Create a new directory in your `everest-workspace` directory (in parallel to the `everest-core` directory) and  
+#. Create a new directory in your `everest-workspace` directory (in parallel to the `everest-core` directory) and
    create a new file named :code:`toolchain.cmake`:
 
    .. code-block:: console
@@ -113,8 +113,8 @@ The following steps describe how to cross-compile a module for the Charge SOM pl
       dist/libexec/everest/modules/{MyEVerestModule}/{MyEVerestModule}: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV),
       dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=ad2342fdd3b8fb1949fc3e13b77382d3da72f28a, for GNU/Linux 3.7.0, stripped
 
-#. The resulting binary and manifest can be found in the :code:`dist/libexec/everest/modules/{MyEVerestModule}`  
-   directory. If you want to test the module on the target system, you can copy the module directory using  
+#. The resulting binary and manifest can be found in the :code:`dist/libexec/everest/modules/{MyEVerestModule}`
+   directory. If you want to test the module on the target system, you can copy the module directory using
    :code:`scp` or :code:`rsync`:
 
   .. code-block:: console
@@ -139,7 +139,7 @@ The following steps describe how to cross-compile a module for the Charge SOM pl
 
       fsck.ext4 -f bundle-staging/core-image-minimal-chargesom.ext4
 
-#. Follow the steps under the section :ref:`firmware_customization` to install your PKI certificate, repackage  
+#. Follow the steps under the section :ref:`firmware_customization` to install your PKI certificate, repackage
 the modified root filesystem into a firmware update image, and test the new firmware.
 
 .. _creating_fw_images:

docs/source/everest_charging_stack.rst

@@ -1,7 +1,7 @@
 .. _everest_charging_stack.rst:
 
 **********************
-EVerest charging stack
+EVerest Charging Stack
 **********************
 
 .. include:: ../../includes/everest_introduction_to_everest.inc

docs/source/getting_started.rst

@@ -4,7 +4,7 @@ Getting Started
 ===============
 
 This chapter is intended to help you get started as easily as possible with EV charging together
-with the Charge SOM Evaluation Kit and the EVerest charging stack. For this purpose, a basic DC 
+with the Charge SOM Evaluation Kit and the EVerest charging stack. For this purpose, a basic DC
 charger is set up as an example and explained step by step.
 
 
@@ -71,7 +71,7 @@ carrier board provide information about the current status of the boot process.
 shows the meaning of the LED status indicators:
 
 .. raw:: html
- 
+
    <div style="text-align: center;">
      Table: Charge SOM Evaluation Kit LED Status Indicators
    </div>
@@ -87,6 +87,7 @@ shows the meaning of the LED status indicators:
 
 .. include:: ../../includes/connecting.inc
 
+.. include:: ../../includes/first_fw_update.inc
 
 Initial Configuration
 ---------------------
@@ -287,7 +288,7 @@ The EVerest log messages should look like this:
    2024-12-13T15:52:03.155499+0100 chargesom manager[263]: [INFO] connector:EvseM  :: EVSE IEC Transaction Started (0 kWh)
    2024-12-13T15:52:03.156415+0100 chargesom manager[263]: [INFO] connector:EvseM  :: EVSE IEC DC mode. We are in 5percent mode so we can continue without further action.
    2024-12-13T15:52:03.156895+0100 chargesom manager[263]: [INFO] connector:EvseM  :: EVSE IEC Charger state: Wait for Auth->PrepareCharging
-   
+
 After that, the EV simulator should establish a powerline connection to the Charge SOM via SLAC.
 
 .. code-block:: sh

docs/source/index.rst

@@ -4,12 +4,11 @@
    contain the root `toctree` directive.
 
 Welcome to Charge SOM User Guide!
-=======================================================
+=================================
 
 **Charge SOM** is an IEC 61851 and ISO 15118 compliant charging controller, born to beat in
 every kind of electric DC vehicle charging station. This user guide explains the possibilities of
-setting up such a system with the Charge SOM, based on the open source charging stack 
-EVerest.
+setting up such a system with the Charge SOM, based on the open source charging stack EVerest.
 
 This documentation starts with a short introduction and then goes straight into a hands-on chapter
 :doc:`getting_started` with a simple example of how to set up a simple DC charger based on the

docs/source/troubleshooting.rst

@@ -25,7 +25,7 @@ connected to USB.
 
 
 Is it possible to use the Charge SOM as an EV simulator?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The Charge SOM hardware is not designed to be used as an EV simulator. Please refer to our
 `website <https://www.chargebyte.com/>`_ for more suitable products.
@@ -80,22 +80,22 @@ The device tree sources of the Charge SOM are divided into multiple layers:
 
 
 How can I access the EVerest admin panel on Charge SOM?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Currently, the Charge SOM does not have integrated the `EVerest admin panel <https://github.com/EVerest/everest-admin-panel>`_
 Please use your development environment to set up your configuration file. Alternatively, you can use a plain text
 editor.
 
 
 Does EVerest on Charge SOM support ISO 15118-20 yet?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The required module for ISO 15118-20 has been included in the image since the Charge SOM EVerest release 0.2.0.
 Please note that the implementation is still under development.
 
 
 How do I set up OCPP 2.0.1 on Charge SOM with EVerest?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 To support OCPP 2.0.1, the EVerest OCPP201 module must be integrated into the EVerest configuration.
 This module uses the `libocpp library <https://github.com/EVerest/libocpp>`_ to implement the OCPP 2.0.1
@@ -107,7 +107,7 @@ and the initial creation of the OCPP 2.0.1 database.
 The most important points are summarised here:
 
 1. The OCPP201 module must be included in your EVerest configuration.
-2. The CbSystem module can be used to fulfill the requirement of the system interface. 
+2. The CbSystem module can be used to fulfill the requirement of the system interface.
 3. While configuring the OCPP 2.0.1 module, ensure that you are using OCPP configuration and database
    paths which are covered by the update mechanism. The following paths are recommended:
 
@@ -133,6 +133,7 @@ The most important points are summarised here:
    For further information about the device model initialization, please refer to the
    `libocpp documentation <https://github.com/EVerest/libocpp/blob/main/doc/v2/ocpp_201_device_model_initialization.md>`_.
 
+
 I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can it fix this?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^