[Improvement-18045][Doc]Improvement Parameter passing behavior doc (#18046)

Author: njnu-seafish

docs/docs/en/guide/parameter/context.md

@@ -16,7 +16,8 @@ DolphinScheduler allows parameter transfer between tasks. Currently, transfer di
 * [Python](../task/python.md)
 * [SubWorkflow](../task/sub-workflow.md)
 * [Kubernetes](../task/kubernetes.md)
-* [zeppelin](../task/zeppelin.md)
+* [Zeppelin](../task/zeppelin.md)
+* [Http](../task/http.md)
 
 When defining an upstream node, if there is a need to transmit the result of that node to a dependency related downstream node. You need to set an `OUT` direction parameter to [Custom Parameters] of the [Current Node Settings]. If it is a sub-workflow node, there is no need to set a parameter in [Current Node Settings], but an `OUT` direction parameter needs to be set in the workflow definition of the sub-workflow.
 
@@ -27,8 +28,8 @@ Upstream parameter will be override when defining parameter with the same name i
 > Note:
 >
 > 1. Parameter passing behavior has changed in version 3.3.x**
->    In older version before 3.2.2, downstream node B could obtain the out type output X of upstream node A without configuring an IN type local variable X.
->    In the new version after 3.3.0, the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.
+>    In legacy versions (3.2.2 and earlier), downstream node B could obtain the OUT type output X of upstream node A without configuring an IN type local variable X.
+>    In new versions (3.3.0 and later), the logic for obtaining local variables has been modified: downstream node B can only use the OUT type output X of upstream node A if it has configured an IN type local variable X.
 >    See the Node_B and Node_mysql examples below for details.
 >
 > 2. If there are no dependencies between nodes, local parameters cannot be passed upstream.

docs/docs/en/guide/task/switch.md

@@ -40,6 +40,7 @@ The switch task needs to be connected with the downstream task to configure the
 
 Configure the conditions and default branches. If the conditions are met, the specified branch will be taken. If the conditions are not met, the default branch will be taken.
 In the figure, if the value of the variable is "A", the branch taskA is executed, if the value of the variable is "B", the branch taskB is executed, and default is executed if both are not satisfied.
+Since the switch task type does not support configuring custom parameters, there is no need to define an IN-type local variable X. You can directly use the OUT-type output X from the upstream node. For more details, please refer to [Parameter Context](../parameter/context.md).
 
 ![switch_02](../../../../img/tasks/demo/switch_02.png)
 

docs/docs/zh/guide/parameter/context.md

@@ -16,7 +16,8 @@ DolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支
 * [Python](../task/python.md)
 * [SubWorkflow](../task/sub-workflow.md)
 * [Kubernetes](../task/kubernetes.md)
-* [zeppelin](../task/zeppelin.md)
+* [Zeppelin](../task/zeppelin.md)
+* [Http](../task/http.md)
 
 当定义上游节点时，如果有需要将该节点的结果传递给有依赖关系的下游节点，需要在【当前节点设置】的【自定义参数】设置一个方向是 OUT 的变量。如果是 SubWorkflow 节点无需在【当前节点设置】中设置变量，需要在子流程的工作流定义中设置一个方向是 OUT 的变量。
 
@@ -25,8 +26,8 @@ DolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支
 如果定义了同名的传递参数，上游节点的参数将被覆盖。
 
 > 1. 参数传递的行为在3.3.x版本中发生了变化**
->    在旧版本低于3.2.2中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X；
->    在版本高于3.3.0中修改领了局部变量的获取逻辑：只有下游节点B配置了IN类型的局部变量X，才可使用上游节点A的out类型输出X。
+>    在旧版本（≤ 3.2.2）中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的OUT类型输出X；
+>    新版本（≥ 3.3.0）中修改了局部变量的获取逻辑：只有下游节点B配置了IN类型的局部变量X，才可使用上游节点A的OUT类型输出X。
 >    详情参考下文的Node_B 和 Node_mysql 样例
 >
 > 2. 若节点之间没有依赖关系，则局部参数无法通过上游传递。

docs/docs/zh/guide/task/switch.md

@@ -36,6 +36,7 @@ switch 任务需要和下游任务连线配置关系后，才可以进行下游
 
 配置条件和默认分支，满足条件会走指定分支，都不满足则走默认分支。
 图中如果变量的值为 "A" 则执行分支 taskA，如果变量的值为 "B" 则执行分支 taskB ，都不满足则执行 default。
+由于switch任务类型不支持配置自定义参数，因此无需配置IN类型的局部变量X，即可直接使用上游节点的OUT类型输出X，请参考[参数传递](../parameter/context.md)。
 
 ![switch_02](../../../../img/tasks/demo/switch_02.png)