diff --git a/tutorial/2-2-ofc22.md b/tutorial/2-2-ofc22.md
index 5a0547d640267ebd45030d10ce8673d984c6b137..d70d72661b733c484d787c3abc10a1cd967ff558 100644
--- a/tutorial/2-2-ofc22.md
+++ b/tutorial/2-2-ofc22.md
@@ -30,8 +30,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD
 ## 2.2.3. Deployment and Dependencies
 
 To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN
-controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured
-the Python environment as described in
+controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python
+environment as described in
 [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md).
 Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal
 you open.
diff --git a/tutorial/2-4-ecoc22.md b/tutorial/2-4-ecoc22.md
index 0cf285faa4ce797ed0d490482f1691d141129bc0..b28fdfd1cc0fc740d5b65df069e75f6cb99c654c 100644
--- a/tutorial/2-4-ecoc22.md
+++ b/tutorial/2-4-ecoc22.md
@@ -13,6 +13,8 @@ folder has been defined.
 This functional test has only been tested with emulated devices; however, if you have access to real devices, you can
 modify the files `./ecoc22/tests/Objects.py` and `./ecoc22/tests/Credentials.py` to point to your devices, and map to
 your network topology.
+Otherwise, you can modify the `./ecoc22/tests/descriptors_emulated.json` that is designed to be uploaded through the
+WebUI instead of using the command line scripts.
 
 __Important__: The device drivers operating with real devices, e.g., OpenConfigDriver, P4Driver, and TransportApiDriver,
                have to be considered as experimental. The configuration and monitoring capabilities they support are
@@ -22,8 +24,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD
 ## 2.4.3. Deployment and Dependencies
 
 To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN
-controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the
-Python environment as described in
+controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python
+environment as described in
 [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md).
 Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal
 you open.
@@ -62,7 +64,7 @@ expected results are:
 - The devices to be added into the Topology.
 - The devices to be pre-configured and initialized as ENABLED by the Automation component.
 - The monitoring for the device ports (named as endpoints in TeraFlowSDN) to be activated and data collection to
-automatically start.
+  automatically start.
 - The links to be added to the topology.
 
 To run this step, you can do it from the WebUI by uploading the file `./ecoc22/tests/descriptors_emulated.json` that
@@ -90,6 +92,7 @@ the optical layer and another for the packet layer. Besides, you can check the "
 rules that have been configured in each device. In the Grafana Dashboard, given that there is now a service configured,
 you should see the plots with the monitored data for the device. By default, device R1-EMU is selected.
 
+
 ### 2.4.5.3. L3VPN Service removal
 
 This step deconfigures the previously created services emulating the request an OSM WIM would make by means of a Mock
@@ -101,6 +104,7 @@ When the script finishes, check the WebUI "Services" tab. You should see that th
 Besides, in the "Devices" tab you can see that the appropriate configuration rules have been deconfigured. In the
 Grafana Dashboard, given that there is no service configured, you should see a 0-valued flat plot again.
 
+
 ### 2.4.5.4. Cleanup
 
 This last step performs a cleanup of the scenario removing all the TeraFlowSDN entities for completeness.