diff --git a/docs/guides/passing-data-task-to-task.md b/docs/guides/passing-data-task-to-task.md
index 66b1e549..afb2fe2b 100644
--- a/docs/guides/passing-data-task-to-task.md
+++ b/docs/guides/passing-data-task-to-task.md
@@ -201,16 +201,21 @@ This results in **"variable_name": "Orkes"**.
 JSONPath error messages occur when there is an issue with the JSON expression due to incorrect syntax or an invalid path. 
 
 **2. What happens when an incorrect task reference name is provided in the JSON expression?**
+
 The task reference names should be unique in a workflow. You may get errors while executing the workflow if you have provided an incorrect task reference name.
 
 **3. What happens if my JSONPath expression is incorrect?**
+
 Incorrect JSONPath expressions may result in a null value instead of the expected output.
 
 **4. How can I check if the data was passed correctly?**
+
 You can verify if the data was passed correctly by checking the input/output fields of the task. 
 
 **5. Can I hard code inputs?**
+
 Yes, you can provide hard-coded inputs. This becomes useful when you have a reusable task with configurable options that can be applied in different workflow contexts.
 
 **6. When should I use Set Variables (Global Variables)?**
+
 Set Variable can be used when you need to store a variable and use it later across different tasks & workflows.