Merge pull request #73 from chargebyte/everest/ccy_adaptations_for_2025.8.0

Everest/ccy adaptations for 2025.8.0

Author: FaHaGit

docs/source/_static/images/admin_panel_bsp_only.png

@@ -96,6 +96,7 @@ content of the configuration file, you will see that it is only a reference to t
 .. note::
    If you create an own configuration file, you can also store it in the "/etc/everest" directory
    and create a symbolic link to it like "ln -sf /etc/everest/my-config.yaml /etc/everest/config.yaml".
+   The file where the "config.yaml" symbolic link points to is preserved during the update process.
 
 .. code-block:: bash
 

docs/source/getting_started.rst

@@ -69,7 +69,7 @@ The most important points are summarised here:
    `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?
+I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can I fix this?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The EVerest mainline development is very dynamic and doesn't guarantee any