Add suggestions from review

Author: Jon Vegard Venås

docs/src/how-to/improve-performance.md

@@ -1,6 +1,7 @@
 # [Improve performance](@id how_to-improve_performance)
 
-Due to the just-in-time (JIT) compilation of Julia, the instantiation of the `EnergyModelsGUI` window takes some time (but reopening the windo will take less time) and this also includes interactive features in the GUI (plotting a plot over `OperationalPeriod`s is a lot faster compared to the first plot).
+Due to the just-in-time (JIT) compilation of Julia, the instantiation of the `EnergyModelsGUI` window takes some time (but reopening the window will take less time). 
+This also includes interactive features in the GUI (creating a the first plot is a lot lower than the subsequent plots).
 
 That being said, it is possible to boost startup time by turning of redundant features. 
 One can for example plot sub-areas only on demand (which for large system significantly reduces setup of the `GUI`) through 

docs/src/how-to/use-custom-background-map.md

@@ -1,6 +1,6 @@
 # [Use custom backgruond map](@id how_to-use_custom_backgruond_map)
 
-The GUI enables user defined background maps in `.geojson` format through the `GUI` constructor parameter `String::map_boundary_file`. One could for example download NUTS boundaries as GeoJSON from [datahub.io](https://datahub.io/core/geo-nuts-administrative-boundaries) and save this file at a desired location and use this file path as `map_boundary_file`.
+The GUI enables user defined background maps in `.geojson` format through the `GUI` constructor parameter `String::map_boundary_file`. One could for example download NUTS boundaries as GeoJSON from [datahub.io](https://datahub.io/core/geo-nuts-administrative-boundaries), save this file at a desired location and use this file path as `map_boundary_file`.
 
 Downloading [NUTS2](https://r2.datahub.io/clt98mkvt000ql70811z8xj6l/main/raw/data/NUTS_RG_60M_2024_4326_LEVL_2.geojson), one can with a EMX-case variable `case`
 

test/example_all_structures.jl

@@ -34,8 +34,13 @@ This comprehensive example includes:
 - Sink-source examples: both operational and investment variants, connected via hub for `Power`.
 
 All subsystems are connected through the global multi-carrier hub, demonstrating integration of:
-- EnergyModelsBase, EnergyModelsGeography, EnergyModelsHydrogen, EnergyModelsCO2,
-  EnergyModelsRenewableProducers, EnergyModelsHeat, EnergyModelsInvestments
+- EnergyModelsBase v0.9.3
+- EnergyModelsCO2 v0.7.6
+- EnergyModelsGeography v0.11.3
+- EnergyModelsHeat v0.1.3
+- EnergyModelsHydrogen v0.8.3
+- EnergyModelsInvestments v0.8.1
+- EnergyModelsRenewableProducers v0.6.7
 """
 function generate_all_in_one_case()
     # -----------------------------