Add doc (#68)

* adding the documentation

* spotlessApply for documentation

documentation/1-connection-endpoints.md

@@ -29,4 +29,4 @@
 
 **Body:**
 
-**Reply: None**
+**Reply: None**

documentation/2-cloud-endpoints.md

@@ -152,6 +152,6 @@
 ```json
 [
     "<CLOUD_ID>",
-    "<CLOUD_ID>" 
+    "<CLOUD_ID>"
 ]
-```
+```

documentation/3-byon-endpoints.md

@@ -92,7 +92,7 @@
 
 ```Json
 {
-	"<BYON_ID>":"<DEPLOYMENT_NAME>/<COMPONENT_NAME>"
+    "<BYON_ID>":"<DEPLOYMENT_NAME>/<COMPONENT_NAME>"
 }
 ```
 
@@ -110,4 +110,4 @@
 
 **Headers:** sessionid
 
-**Body:** None
+**Body:** None

documentation/4-edge-endpoints.md

@@ -93,7 +93,7 @@
 
 ```Json
 {
-	"<Edge_ID>":"<DEPLOYMENT_NAME>/<COMPONENT_NAME>"
+    "<Edge_ID>":"<DEPLOYMENT_NAME>/<COMPONENT_NAME>"
 }
 ```
 
@@ -111,4 +111,4 @@
 
 **Headers:** sessionid
 
-**Body:** None
+**Body:** None

documentation/5-job-endpoints.md

@@ -337,4 +337,4 @@ Also a job can define a Docker container:
 
 **Headers:** sessionid
 
-**Returns**: True if the removing of all the jobs was successful, false otherwise.
+**Returns**: True if the removing of all the jobs was successful, false otherwise.

documentation/6-monitoring-endpoints.md

@@ -38,4 +38,4 @@ In this case the node name refers to the component name defined in the job descr
 
 **Headers:** sessionid
 
-**Returns**: A JSON list of all the defined EMS deployments.
+**Returns**: A JSON list of all the defined EMS deployments.

documentation/7-node-endpoints.md

@@ -34,7 +34,7 @@ For more details about these filters you can check the SAL code [NodeCandidateUt
         "requirementClass": "hardware",
         "requirementAttribute": "cores",
         "requirementOperator": "EQ",
-        "value": "2" 
+        "value": "2"
     },
         {
         "type": "AttributeRequirement",
@@ -80,18 +80,18 @@ For more details about these filters you can check the SAL code [NodeCandidateUt
 
 ```json
 [
-	{
-		"nodeName": "component-App-1-0",
-		"taskName": "Component_App",
-		"nodeCandidateId": "<NODE_CANDIDATE_ID>",
-		"cloudId": "<CLOUD_ID>"
-	},
-	{
-		"nodeName": "component-LB-1-0",
-		"taskName": "Component_LB",
-		"nodeCandidateId": "<NODE_CANDIDATE_ID>",
-		"cloudId": "<CLOUD_ID>"
-	}
+    {
+        "nodeName": "component-App-1-0",
+        "taskName": "Component_App",
+        "nodeCandidateId": "<NODE_CANDIDATE_ID>",
+        "cloudId": "<CLOUD_ID>"
+    },
+    {
+        "nodeName": "component-LB-1-0",
+        "taskName": "Component_LB",
+        "nodeCandidateId": "<NODE_CANDIDATE_ID>",
+        "cloudId": "<CLOUD_ID>"
+    }
 ]
 ```
 
@@ -128,8 +128,8 @@ For more details about these filters you can check the SAL code [NodeCandidateUt
 ```json
 [
     "<NODE_ID>",
-    "<NODE_ID>", 
+    "<NODE_ID>",
 ]
 ```
 
-**Returns**: True if the node was successfully removed, false otherwise.
+**Returns**: True if the node was successfully removed, false otherwise.

documentation/8-scaling-endpoints.md

@@ -52,4 +52,4 @@ A JSON list of nodes to be removed
 
 **Returns**: True if the scaling was successful, false otherwise.
 
-* * *
+* * *

documentation/9-vault-endpoints.md

@@ -34,4 +34,4 @@ A JSON body of the key/secret pairs:
 
 **Headers:** sessionid
 
-**Returns**: True if the secrets were successfully removed, false otherwise.
+**Returns**: True if the secrets were successfully removed, false otherwise.

documentation/README.md

@@ -159,4 +159,4 @@ SAL provides multiple endpoints that you can use to interact with the ProActive
             </tr>
         </tbody>
     </table>
-</figure>
+</figure>