Fix MegaLinter

Author: FabrizioMoggio

code/API_definitions/Traffic_Influence.yaml

@@ -122,12 +122,13 @@ info:
     CAMARA APIs (“MEC Exposure & Experience Management API” and “Simple Edge
     Discovery”). To add more regions the TI API must be invoked (POST) for each
     region. If in a "region" there are many Application instances active in
-    different "zones", the TI API can be invoked to configure the optimal routing
-    for all the instances with just one API call specifying the region. If just
-    the Application instances in some regions must be affected, the TI API can be
-    invoked for the regions of interest, without specifying "zone" in the API call.
-    If just some specific Application instance must be affected, it is not required
-    to specify any "region" or "zone", the parameter "appInstanceId" can be used.\
+    different "zones", the TI API can be invoked to configure the optimal 
+    routing for all the instances with just one API call specifying the region.
+    If just the Application instances in some regions must be affected, the TI
+    API can be invoked for the regions of interest, without specifying "zone" in
+    the API call. If just some specific Application instance must be affected,
+    it is not required to specify any "region" or "zone", the parameter
+    "appInstanceId" can be used.\
     \
     **zone:**
     A "zone" is a smaller geographical area inside a "region". A "zone" is where
@@ -144,7 +145,7 @@ info:
     **appInstanceId:**
     A globally unique identifier generated by the Operator Platform to identify
     a specific instance of the Application in a specific zone. To influence a
-    traffic toward a specific Application instance. If just some specific 
+    traffic toward a specific Application instance. If just some specific
     Application instance must be affected, it is not required to specify any
     "region" or "zone", the parameter "appInstanceId" can be used.\
     \
@@ -224,10 +225,10 @@ info:
     a TI API invocation is required.
     ## Release Notes
     The Traffic Influence API reduces the complexity of activating the optimal
-    routing toward an Application Instance and o provides the optimal routing for
-    an user moving among geographical areas maybe served by different Application
-    instances. In this release it is up to the API Consumer to detect the user
-    moving among geographical areas.\
+    routing toward an Application Instance and o provides the optimal routing
+    for an user moving among geographical areas maybe served by different
+    Application instances. In this release it is up to the API Consumer to
+    detect the user moving among geographical areas.\
     \
     **Enhancements with respect to the previous release V0.8.1:**
     - These release also effects existing data sessions