Fix EVerest upstream URLs

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

Author: mhei

docs/source/everest_charging_stack.rst

@@ -24,7 +24,7 @@ An overview of the EVerest modules is shown in the next section.
 
 .. include:: ../../includes/everest_overview_of_everest_modules.inc
 
-**DCSupplySimulator** (`view on GitHub <https://github.com/EVerest/everest-core/blob/main/modules/simulation/DCSupplySimulator/manifest.yaml>`__)
+**DCSupplySimulator** (`view on GitHub <https://github.com/EVerest/everest-core/blob/main/modules/Simulation/DCSupplySimulator/manifest.yaml>`__)
 
 This module simulates a DC power supply device.
 

docs/source/troubleshooting.rst

@@ -34,10 +34,11 @@ The Charge SOM hardware is not designed to be used as an EV simulator. Please re
 I want to control EVerest via CAN, how can I achieve this?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Currently, there is no such EVerest module available, you will need to implement it on your own. But
-at least there is a `module <https://github.com/EVerest/everest-core/tree/main/modules/DPM1000>`_
-and a `library <https://github.com/EVerest/everest-core/tree/main/lib/staging/can_dpm1000>`_,
-which uses the CAN interface.
+Currently there is no such EVerest module available, you will need to implement it on your own.
+
+But at least there is are `DC power supply modules <https://github.com/EVerest/everest-core/tree/main/modules/HardwareDrivers/PowerSupplies>`_
+and a `library <https://github.com/EVerest/everest-core/tree/main/lib/everest/can_dpm1000>`_,
+which uses the CAN interface. This might help as a starting point.
 
 
 What is the difference between CHSTOP_IN and SAFETY_ESTOPx?
@@ -100,7 +101,7 @@ 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
 protocol.
-The `OCPP201 module documentation <https://github.com/EVerest/everest-core/blob/main/modules/OCPP201/doc.rst>`_
+The `OCPP201 module documentation <https://github.com/EVerest/everest-core/blob/main/modules/EVSE/OCPP201/doc.rst>`_
 already contains some information about the module parameters, the provided and required interfaces,
 and the initial creation of the OCPP 2.0.1 database.
 
@@ -121,8 +122,8 @@ The most important points are summarised here:
 5. The OCPP 2.0.1 device model initialization is done automatically by the OCPP201 module after the
    first start of EVerest. The database is stored the `DeviceModelDatabasePath`.
 6. The component config files are stored in the `DeviceModelConfigPath`. Component config files are
-   used to initialize or update the device model database. To update a component config file, just the
-   place a `component config file <https://github.com/EVerest/libocpp/tree/v0.16.2/config/v201/component_config>`_
+   used to initialize or update the device model database. To update a component config file, just
+   place a `component config file <https://github.com/EVerest/libocpp/tree/main/config/v2/component_config>`_
    in the same directory structure in the DeviceModelConfigPath and change the values accordingly.
    Important keys of the component config files are: