diff --git a/docs/deploy-to-api.md b/docs/deploy-to-api.md
index 9c14d6bdb4..e925945644 100644
--- a/docs/deploy-to-api.md
+++ b/docs/deploy-to-api.md
@@ -21,8 +21,8 @@
### Example cURL request
```
-curl -X POST --location "" \\
--H "Content-Type: application/json" \\
+curl -X POST --location ""
+-H "Content-Type: application/json"
-d '{ "callback": "" }'
```
@@ -52,7 +52,7 @@ When the CURL command and the respective object are executed, you will receive t
## SaltInput node
-The `SaltInput` node is an official node developed by the Salt team. Each one present in the workflow allows you to expose input parameters for the end user to interact with.
+The `SaltInput` node allows you to expose input parameters for end-user interaction within your workflow. Each one represents an input property in the `workflow_input` object of your API call's request body.
-You can plug a SaltInput node in place of a text box or node parameter by right-clicking the node and converting it to an input.
+You can plug a `SaltInput` node in place of a text box or node parameter by right-clicking the node and converting it to an input.
![workflows9](images/workflows9.png)
-Your outputs can be configured using SaltOutput nodes, which is where you are able to specify your file types & frame rate. Each node can handle batch outputs, and you can have multiple nodes with different file types. It can help to name your outputs to differentiate them.
+Your outputs can be configured using `SaltOutput` nodes, which is where you are able to specify your file types & frame rate. Each node can handle batch outputs, and you can have multiple nodes with different file types. It can help to name your outputs to differentiate them.
![workflows10](images/workflows10.png)