Address review comments: add Noop WAL link and simplify descriptions

Co-authored-by: WenyXu <[email protected]>

Author: Copilot

docs/user-guide/deployments-administration/configuration.md

@@ -364,7 +364,7 @@ Read [Performance Tuning Tips](/user-guide/deployments-administration/performanc
 
 ### WAL options
 
-GreptimeDB supports three WAL storage options—Local WAL, Remote WAL, and Noop WAL. See the [WAL Overview](/user-guide/deployments-administration/wal/overview.md) for a comparison of the options. For detailed configurations, refer to the [Local WAL](/user-guide/deployments-administration/wal/local-wal.md) and [Remote WAL](/user-guide/deployments-administration/wal/remote-wal/configuration.md) documentation.
+GreptimeDB supports three WAL storage options—Local WAL, Remote WAL, and Noop WAL. See the [WAL Overview](/user-guide/deployments-administration/wal/overview.md) for a comparison of the options. For detailed configurations, refer to the [Local WAL](/user-guide/deployments-administration/wal/local-wal.md), [Remote WAL](/user-guide/deployments-administration/wal/remote-wal/configuration.md), and [Noop WAL](/user-guide/deployments-administration/wal/noop-wal.md) documentation.
 
 
 ### Logging options
@@ -673,7 +673,6 @@ tcp_nodelay = true
 # Available wal providers:
 # - `raft_engine` (default): there're none raft-engine wal config since metasrv only involves in remote wal currently.
 # - `kafka`: metasrv **have to be** configured with kafka wal config when using kafka wal provider in datanode.
-# Note: `noop` provider is only available for datanode configuration, not metasrv.
 provider = "raft_engine"
 
 # Kafka wal config.

docs/user-guide/deployments-administration/wal/local-wal.md

@@ -22,7 +22,7 @@ If you are using Helm Chart to deploy GreptimeDB, you can refer to [Common Helm
 
 | Configuration Option | Description                                                                                                          | Default Value     |
 | -------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------- |
-| `provider`           | The provider of the WAL. Options: `raft_engine` (local file system storage), `kafka` (remote WAL storage in Kafka), or `noop` (no-op WAL provider, see [Noop WAL](/user-guide/deployments-administration/wal/noop-wal.md)) | `"raft_engine"`   |
+| `provider`           | The provider of the WAL. Options: `raft_engine` (local file system storage), `kafka` (remote WAL storage in Kafka), or `noop` (no-op WAL provider) | `"raft_engine"`   |
 | `dir`                | The directory where to write logs                                                                                    | `{data_home}/wal` |
 | `file_size`          | The size of single WAL log file                                                                                      | `128MB`           |
 | `purge_threshold`    | The threshold of the WAL size to trigger purging                                                                     | `1GB`             |

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/configuration.md

@@ -356,7 +356,7 @@ write_cache_size = "10GiB"
 
 ### WAL 选项
 
-GreptimeDB 支持三种 WAL 存储方式：本地 WAL、Remote WAL 和 Noop WAL。关于它们的对比，请参见 [WAL 概述](/user-guide/deployments-administration/wal/overview.md)。具体配置可参考 [本地 WAL](/user-guide/deployments-administration/wal/local-wal.md) 和 [Remote WAL](/user-guide/deployments-administration/wal/remote-wal/configuration.md) 文档。
+GreptimeDB 支持三种 WAL 存储方式：本地 WAL、Remote WAL 和 Noop WAL。关于它们的对比，请参见 [WAL 概述](/user-guide/deployments-administration/wal/overview.md)。具体配置可参考 [本地 WAL](/user-guide/deployments-administration/wal/local-wal.md)、[Remote WAL](/user-guide/deployments-administration/wal/remote-wal/configuration.md) 和 [Noop WAL](/user-guide/deployments-administration/wal/noop-wal.md) 文档。
 
 
 ### Logging 选项
@@ -665,7 +665,6 @@ tcp_nodelay = true
 # 可用的 WAL 提供者：
 # - `raft_engine`（默认）：由于 metasrv 目前仅涉及远程 WAL，因此没有 raft-engine WAL 配置。
 # - `kafka`：在 datanode 中使用 kafka WAL 提供者时，metasrv **必须** 配置 kafka WAL 配置。
-# 注意：`noop` 提供者仅适用于 datanode 配置，不适用于 metasrv。
 provider = "raft_engine"
 
 # Kafka WAL 配置。

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/wal/local-wal.md

@@ -23,7 +23,7 @@ sync_write = false
 
 | 配置项            | 描述                                                                                            | 默认值            |
 | ----------------- | ----------------------------------------------------------------------------------------------- | ----------------- |
-| `provider`        | WAL 的提供者。可选项：`raft_engine`（本地文件系统存储）、`kafka`（使用 Kafka 的远程 WAL 存储）或 `noop`（无操作 WAL 提供者，参见 [Noop WAL](/user-guide/deployments-administration/wal/noop-wal.md)） | `"raft_engine"`   |
+| `provider`        | WAL 的提供者。可选项：`raft_engine`（本地文件系统存储）、`kafka`（使用 Kafka 的远程 WAL 存储）或 `noop`（无操作 WAL 提供者） | `"raft_engine"`   |
 | `dir`             | 日志写入目录                                                                                    | `{data_home}/wal` |
 | `file_size`       | 单个 WAL 日志文件的大小                                                                         | `128MB`           |
 | `purge_threshold` | 触发清理的 WAL 总大小阈值                                                                       | `1GB`             |