fix: correct capitalization and grammatical errors

docs/source/firmware.rst

@@ -2,7 +2,7 @@
 
 ********
 Firmware
 ********
 
 Introduction to Yocto
 =====================
@@ -297,7 +297,7 @@
   When updating from chargebyte's proprietary charging stack to this EVerest-based charging stack,
   the configuration files (e.g. the :code:`"/etc/secc/customer.json"`) are not preserved and you
   start with a basic, default EVerest configuration.
-  It is therefore inevitable that Everest must be reconfigured after starting the board.
+  It is therefore inevitable that EVerest must be reconfigured after starting the board.
   In the worst case EVerest stack does not start up correctly. Also note, that the return path from
   EVerest to chargebyte's proprietary charging stack (when doing a firmware update) is affected:
   since the EVerest configuration files differ significantly from chargebyte's proprietary ones,

includes/cb_energy.inc

@@ -26,9 +26,9 @@ Features like generating charging session report and the energy management are c
 from chargebyte GmbH. For more information have a look `on our website <https://chargebyte.com/software/energy-manager>`_.
 
 
-Both parts have to be in the same network. In order to monitor and control the wallboxes, the Everest charging stack is needed. The Everest stack provides an API module, that is used by CB Energy either on localhost (on the same hardware) or to access other instances in the same local network. 
+Both parts have to be in the same network. In order to monitor and control the wallboxes, the EVerest charging stack is needed. The EVerest stack provides an API module, that is used by CB Energy either on localhost (on the same hardware) or to access other instances in the same local network.
 
-Note: This documentation is a quick start to get the nymea ecosystem running as fast as possible with Everest charging stack. If you are testing CB Energy on one of chargebyte's Linux controllers, both EVerest and CB Energy are preinstalled in the latest firmware images. A more detailed documentation can be found `on the nymea website <https://nymea.io>`_.
+Note: This documentation is a quick start to get the nymea ecosystem running as fast as possible with EVerest charging stack. If you are testing CB Energy on one of chargebyte's Linux controllers, both EVerest and CB Energy are preinstalled in the latest firmware images. A more detailed documentation can be found `on the nymea website <https://nymea.io>`_.
 
 .. important::
   The `API module <https://github.com/EVerest/everest-core/tree/main/modules/API>`_ must be installed and active in the EVerest configuration.
@@ -65,7 +65,7 @@ The CB energy app can be installed from the official stores.
 Setup and configuration
 =======================
 
-On a chargebyte controller, the nymea Daemon will start automatically, together with the Everest stack while the system is booting up.
+On a chargebyte controller, the nymea daemon will start automatically, together with the EVerest stack while the system is booting up.
 Once the services are running the app will be able to detect the instance automatically on localhost or in the local network.
 
 
@@ -74,7 +74,7 @@ Once the services are running the app will be able to detect the instance automa
 Client discovery
 ================
 
-The CB energy App (client) automatically discovers available instances (servers) in your local network. Please make sure to allow the Smartphone App to have access to your local network devices after installing it.
+The CB energy app (client) automatically discovers available instances (servers) in your local network. Please make sure to allow the smartphone app to have access to your local network devices after installing it.
 
 .. figure:: ../../includes/_static/images/cbenergy/discover.png
 	:height: 600px

includes/development.inc

@@ -107,7 +107,7 @@ Creating a Development Image
 ============================
 
 In order to build the custom image, follow the section "`Building an image <https://github.com/chargebyte/chargebyte-bsp/tree/kirkstone-everest/README.md#user-content-build>`_"
-found in "chargebyte-bsp" repository which produces a Linux root filesystem. This can be either
+found in the "chargebyte-bsp" repository which produces a Linux root filesystem. This can be either
 `flashed <https://github.com/chargebyte/chargebyte-bsp/tree/kirkstone-everest/README.md#user-content-flash>`_
 directly, or used to `create a firmware image using RAUC <https://github.com/chargebyte/chargebyte-bsp/tree/kirkstone-everest/README.md#user-content-flash>`_.
 

includes/everest_overview_of_everest_modules.inc

@@ -35,7 +35,7 @@ actual RFID reader. It listens to the AuthRequired event from evse_manager modul
 
 **DummyTokenValidator** (`view on GitHub <https://github.com/EVerest/everest-core/tree/main/modules/DummyTokenValidator>`__)
 
-This module always returning the same configured token validation result for every token. The
+This module always returns the same configured token validation result for every token. The
 validation result is a configuration key in the manifest of the module.
 
 **CbSystem** (`view on GitHub <https://github.com/chargebyte/everest-chargebyte/tree/main/modules/CbSystem>`__)
@@ -57,4 +57,4 @@ This module implements and integrates OCPP 2.0.1 support within EVerest.
 
 **AuthListValidator**
 
-This module validating if an incoming token exists in a in a predefined list of authorized tokens.
+This module validates if an incoming token exists in a predefined list of authorized tokens.