Copilot commented on code in PR #18079: URL: https://github.com/apache/dolphinscheduler/pull/18079#discussion_r2960495480
########## docs/docs/en/guide/task/grpc.md: ########## @@ -12,7 +12,6 @@ This node is used to execute gRPC tasks and supports checking gRPC status codes, ## Task Parameters -[//]: # (TODO: use the commented anchor below once our website template supports this syntax) [//]: # (- For default parameter descriptions, please refer to [DolphinScheduler Task Parameter Appendix](appendix.md#默认任务参数) under `Default Task Parameters`.) - For default parameter descriptions, please refer to [DolphinScheduler Task Parameter Appendix](appendix.md) under `Default Task Parameters`. Review Comment: There’s a leftover commented-out link under “## Task Parameters” that still points to a Chinese anchor (`appendix.md#默认任务参数`) and uses the inconsistent name “Task Parameter Appendix”. This should be removed (to match other task docs) or updated to the correct English anchor (`appendix.md#default-task-parameters`) and consistent appendix name (“Task Parameters Appendix”) to avoid stale/broken references. ########## docs/docs/zh/guide/task/dinky.md: ########## @@ -12,9 +12,6 @@ ## Task Parameter Review Comment: This Chinese guide mixes English section headers (e.g., “## Overview”, “## Create Task”, “## Task Parameter”), which is inconsistent with the surrounding zh task docs that use Chinese headings (e.g., “## 综述/## 创建任务/## 任务参数”). Consider translating these headings for consistency and readability in the zh docs set. ########## docs/docs/zh/guide/start/quick-start.md: ########## @@ -11,82 +10,80 @@ ### 设置 Dolphinscheduler Review Comment: Section heading uses inconsistent product capitalization: “### 设置 Dolphinscheduler” should be “### 设置 DolphinScheduler” (matching the rest of the page and official name). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
