Improvement Parameter passing behavior doc

Author: 苏义超

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

@@ -27,8 +27,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.(Note: This restriction does not apply to Switch tasks, as they lack an interface for configuring custom parameters.)
 >    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/zh/guide/parameter/context.md

@@ -25,8 +25,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。（例外情况：Switch类型任务不受此限制。由于该任务类型不支持配置自定义参数（无输入参数配置入口），因此无需定义 IN 变量即可直接获取上游输出。）
 >    详情参考下文的Node_B 和 Node_mysql 样例
 >
 > 2. 若节点之间没有依赖关系，则局部参数无法通过上游传递。