docs: update Docker Compose cluster guidance

Revise Chinese and English docs for HugeGraph Docker deployment to standardize on Docker Compose wording and usage. Add notes that users should clone/pull the HugeGraph repo (or at least the docker/ directory), include a reminder to keep the HUGEGRAPH_VERSION aligned with releases, and adjust memory recommendations for Mac (3-node cluster ~12 GB) with platform guidance. Clarify compose file descriptions, emphasize container hostnames for HG_* env vars, change some example log years to 2026, reformat deprecated-alias lines, and number/troubleshooting items for clarity. Minor phrasing and section-title tweaks across hugegraph-docker-cluster.md, hugegraph-hstore.md, hugegraph-pd.md, and hugegraph-server.md (EN & CN).

Signed-off-by: imbajin <jin@apache.org>

Author: imbajin

content/cn/docs/guides/hugegraph-docker-cluster.md

@@ -6,32 +6,33 @@ weight: 5
 
 ## 概述
 
-HugeGraph 支持通过 Docker 桥接网络运行完整的分布式集群（PD + Store + Server）。该方式适用于 Linux 和 Mac（Docker Desktop）。
-
-早期版本使用 `network_mode: host`，仅在 Linux 上可用。集群现在使用 Docker 桥接网络（`hg-net`），服务通过容器主机名而非 `127.0.0.1` 进行通信。
+HugeGraph 通过 Docker-Compose 可快速运行完整的分布式集群版（PD + Store + Server）。该方式适用于 Linux 和 Mac。
 
 ## 前置条件
 
 - Docker Engine 20.10+ 或 Docker Desktop 4.x+
 - Docker Compose v2
-- Mac（Docker Desktop）运行 3 节点集群时，需分配至少 **12 GB** 内存（设置 → 资源 → 内存）。Linux 上 Docker 直接使用宿主机内存，无需额外分配
+- Mac 运行 3 节点集群时，建议分配至少 **12 GB** 内存（设置 → 资源 → 内存）。[其他平台根据实际情况调整]
 
-> **已测试平台**：Linux（原生 Docker）和 macOS（Docker Desktop，已在 Apple M4 上测试）。Windows Docker Desktop 未经测试。
+> **已测试环境**：Linux（原生 Docker）和 macOS（Docker Desktop with ARM M4）
 
 ## Compose 文件
 
-[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了三个 compose 文件：
+在 HugeGraph 主仓库 [`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了三个 compose 文件：
 
 | 文件 | 描述 |
 |------|------|
-| `docker-compose.yml` | 使用预构建镜像的单节点快速启动 |
-| `docker-compose.dev.yml` | 从源码构建的单节点开发模式 |
-| `docker-compose-3pd-3store-3server.yml` | 3 节点分布式集群 |
+| `docker-compose.yml` | 使用预构建镜像的** 1x3 单进程(节点)**快速启动 |
+| `docker-compose.dev.yml` | 从源码构建的单节点**开发模式** |
+| `docker-compose-3pd-3store-3server.yml` | ** 3x3 进程**(模拟节点)分布式集群 |
+
+> 注: 后续步骤皆为假设你本地**已拉取** `hugegraph` 主仓库代码 (至少是 docker 目录)
 
 ## 单节点快速启动
 
 ```bash
 cd hugegraph/docker
+ # 注意版本号请随时保持更新 → 1.x.0 
 HUGEGRAPH_VERSION=1.7.0 docker compose up -d
 ```
 
@@ -47,12 +48,12 @@ cd hugegraph/docker
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
-启动顺序自动强制执行：
-1. PD 节点首先启动，必须通过 `/v1/health` 健康检查
-2. Store 节点在所有 PD 节点健康后启动
-3. Server 节点在所有 Store 节点健康后启动
+默认内置的启动顺序：
+1. PD (节点)最先启动，且必须通过 `/v1/health` 健康检查
+2. Store (节点)在所有 PD 健康后再启动
+3. Server (节点)在所有 Store + PD 健康后最后启动
 
-验证集群：
+验证集群正常：(重要)
 ```bash
 curl http://localhost:8620/v1/health      # PD 健康检查
 curl http://localhost:8520/v1/health      # Store 健康检查
@@ -76,7 +77,7 @@ curl http://localhost:8620/v1/partitions   # 分区分配
 | `HG_PD_DATA_PATH` | 否 | `/hugegraph-pd/pd_data` | `pd.data-path` |
 | `HG_PD_INITIAL_STORE_COUNT` | 否 | `1` | `pd.initial-store-count` |
 
-**已弃用的别名**：`GRPC_HOST` → `HG_PD_GRPC_HOST`、`RAFT_ADDRESS` → `HG_PD_RAFT_ADDRESS`、`RAFT_PEERS` → `HG_PD_RAFT_PEERS_LIST`
+> **已弃用的别名**：`GRPC_HOST` → `HG_PD_GRPC_HOST`、`RAFT_ADDRESS` → `HG_PD_RAFT_ADDRESS`、`RAFT_PEERS` → `HG_PD_RAFT_PEERS_LIST`
 
 ### Store 变量
 
@@ -89,7 +90,7 @@ curl http://localhost:8620/v1/partitions   # 分区分配
 | `HG_STORE_REST_PORT` | 否 | `8520` | `server.port` |
 | `HG_STORE_DATA_PATH` | 否 | `/hugegraph-store/storage` | `app.data-path` |
 
-**已弃用的别名**：`PD_ADDRESS` → `HG_STORE_PD_ADDRESS`、`GRPC_HOST` → `HG_STORE_GRPC_HOST`、`RAFT_ADDRESS` → `HG_STORE_RAFT_ADDRESS`
+> **已弃用的别名**：`PD_ADDRESS` → `HG_STORE_PD_ADDRESS`、`GRPC_HOST` → `HG_STORE_GRPC_HOST`、`RAFT_ADDRESS` → `HG_STORE_RAFT_ADDRESS`
 
 ### Server 变量
 
@@ -100,7 +101,7 @@ curl http://localhost:8620/v1/partitions   # 分区分配
 | `STORE_REST` | 否 | — | `wait-partition.sh` 使用 |
 | `PASSWORD` | 否 | — | 启用鉴权模式 |
 
-**已弃用的别名**：`BACKEND` → `HG_SERVER_BACKEND`、`PD_PEERS` → `HG_SERVER_PD_PEERS`
+> **已弃用的别名**：`BACKEND` → `HG_SERVER_BACKEND`、`PD_PEERS` → `HG_SERVER_PD_PEERS`
 
 ## 端口参考
 
@@ -124,10 +125,10 @@ curl http://localhost:8620/v1/partitions   # 分区分配
 
 ## 故障排查
 
-**容器 OOM 被杀（退出码 137）**：将 Docker Desktop 内存增加到 12 GB 以上。
+1. **容器 OOM 退出（exit code 137）**：将 Docker Desktop 内存增加到 12 GB 以上 (或调整被 kill 的启动 jvm 内存设置)
 
-**Raft 选举超时**：检查所有 PD 节点的 `HG_PD_RAFT_PEERS_LIST` 是否一致。验证连通性：`docker exec hg-pd0 ping pd1`
+2. **Raft 选举超时**：检查所有 PD 节点的 `HG_PD_RAFT_PEERS_LIST` 是否一致。验证连通性：`docker exec hg-pd0 ping pd1`
 
-**分区分配未完成**：检查 `curl http://localhost:8620/v1/stores` — 所有 3 个 Store 必须显示 `"state":"Up"` 才能完成分区分配。
+3. **分区分配未完成**：检查 `curl http://localhost:8620/v1/stores` — 3 个 Store 必须都显示 `"state":"Up"` 才能完成分区分配
 
-**连接被拒**：确保 `HG_*` 环境变量使用容器主机名（`pd0`、`store0`），而非 `127.0.0.1`。
+4. **连接被拒**：确保 `HG_*` 环境变量使用容器主机名（`pd0`、`store0`），而非 `127.0.0.1`

content/cn/docs/quickstart/hugegraph/hugegraph-hstore.md

@@ -1,3 +1,4 @@
+
 ---
 title: "HugeGraph-Store Quick Start"
 linkTitle: "安装/构建 HugeGraph-Store"
@@ -52,12 +53,15 @@ mvn clean install -DskipTests=true
 
 #### 3.3 Docker 部署
 
-HugeGraph-Store Docker 镜像已发布在 Docker Hub，镜像名为 `hugegraph/store:1.7.0`。
+HugeGraph-Store Docker 镜像已发布在 DockerHub，镜像名是 `hugegraph/store`。
+
+> 注: 后续步骤皆假设你本地**已拉取** `hugegraph` 主仓库代码 (至少是 docker 目录)
 
-使用 compose 文件部署完整的 3 节点集群（PD + Store + Server）：
+使用 docker-compose 文件部署完整的 3 节点集群（PD + Store + Server）：
 
 ```bash
 cd hugegraph/docker
+# 注意版本号请随时保持更新 → 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
@@ -157,7 +161,7 @@ logging:
 启动成功后，可以在 `logs/hugegraph-store-server.log` 中看到类似以下的日志：
 
 ```
-2024-xx-xx xx:xx:xx [main] [INFO] o.a.h.s.n.StoreNodeApplication - Started StoreNodeApplication in x.xxx seconds (JVM running for x.xxx)
+2026-xx-xx xx:xx:xx [main] [INFO] o.a.h.s.n.StoreNodeApplication - Started StoreNodeApplication in x.xxx seconds (JVM running for x.xxx)
 ```
 
 #### 5.2 停止 Store
@@ -229,7 +233,7 @@ pdserver:
   address: 127.0.0.1:8686,127.0.0.1:8687,127.0.0.1:8688
 ```
 
-#### 6.3 Docker 集群快速启动
+#### 6.3 Docker 分布式集群配置
 
 3 节点 Store 集群包含在 `docker/docker-compose-3pd-3store-3server.yml` 中。每个 Store 节点拥有独立的主机名和环境变量：
 

content/cn/docs/quickstart/hugegraph/hugegraph-pd.md

@@ -51,12 +51,14 @@ mvn clean install -DskipTests=true
 
 #### 3.3 Docker 部署
 
-HugeGraph-PD Docker 镜像已发布在 Docker Hub，镜像名为 `hugegraph/pd:1.7.0`。
+HugeGraph-PD Docker 镜像已发布在 Docker Hub，镜像名为 `hugegraph/pd`。
+> 注: 后续步骤皆假设你本地**已拉取** `hugegraph` 主仓库代码 (至少是 docker 目录)
 
-使用 compose 文件部署完整的 3 节点集群（PD + Store + Server）：
+使用 docker-compose 模式部署完整的 3 节点集群（PD + Store + Server）：
 
 ```bash
 cd hugegraph/docker
+# 注意版本号请随时保持更新 → 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
@@ -164,7 +166,7 @@ partition:
 启动成功后，可以在 `logs/hugegraph-pd-stdout.log` 中看到类似以下的日志：
 
 ```
-2024-xx-xx xx:xx:xx [main] [INFO] o.a.h.p.b.HugePDServer - Started HugePDServer in x.xxx seconds (JVM running for x.xxx)
+2026-xx-xx xx:xx:xx [main] [INFO] o.a.h.p.b.HugePDServer - Started HugePDServer in x.xxx seconds (JVM running for x.xxx)
 ```
 
 #### 5.2 停止 PD

content/cn/docs/quickstart/hugegraph/hugegraph-server.md

@@ -57,14 +57,15 @@ Core 模块是 Tinkerpop 接口的实现，Backend 模块用于管理数据存
 
 > **注意**：Docker compose 文件使用桥接网络（`hg-net`），适用于 Linux 和 Mac（Docker Desktop）。如需运行 3 节点分布式集群，请为 Docker Desktop 分配至少 **12 GB** 内存（设置 → 资源 → 内存）。
 
-另外，如果我们希望能够在一个文件中管理 HugeGraph 相关的实例，可以使用 `docker compose` 完成部署。
+另外，如果我们希望能够一体化管理 HugeGraph 多模块实例，则可以使用 `docker compose` 方式。
 [`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了两个 compose 文件：
 
 - **单节点快速启动**（预构建镜像）：`docker/docker-compose.yml`
 - **单节点开发构建**（从源码构建）：`docker/docker-compose.dev.yml`
 
 ```bash
 cd hugegraph/docker
+# 注意版本号请随时保持更新 → 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose up -d
 ```
 
@@ -308,9 +309,9 @@ curl http://localhost:8081/graphs
 bin/stop-hugegraph.sh
 ```
 
-#### Docker 集群快速启动
+#### Docker 分布式集群
 
-通过 Docker 运行完整的分布式集群（3 PD + 3 Store + 3 Server）：
+通过 Docker-Compose 运行完整的分布式集群（3 PD + 3 Store + 3 Server）：
 
 
 ```bash

content/en/docs/guides/hugegraph-docker-cluster.md

@@ -6,32 +6,33 @@ weight: 5
 
 ## Overview
 
-HugeGraph supports running a full distributed cluster (PD + Store + Server) via Docker using bridge networking. This works on Linux and Mac (Docker Desktop).
-
-Previous versions used `network_mode: host` which only worked on Linux. The cluster now uses a Docker bridge network (`hg-net`) where services communicate via container hostnames instead of `127.0.0.1`.
+HugeGraph can quickly run a full distributed deployment (PD + Store + Server) with Docker Compose. This works on Linux and Mac.
 
 ## Prerequisites
 
 - Docker Engine 20.10+ or Docker Desktop 4.x+
 - Docker Compose v2
-- For the 3-node cluster on Mac (Docker Desktop): allocate at least **12 GB** memory (Settings → Resources → Memory)
+- For a 3-node cluster on Mac: allocate at least **12 GB** memory (Settings → Resources → Memory). Adjust this on other platforms as needed.
 
-> **Tested platforms**: Linux (native Docker) and macOS (Docker Desktop, tested on Apple M4). Windows Docker Desktop is untested.
+> **Tested environments**: Linux (native Docker) and macOS (Docker Desktop with ARM M4).
 
 ## Compose Files
 
-Three compose files are available in the [`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
+Three compose files are available in the [`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory of the HugeGraph main repository:
 
 | File | Description |
 |------|-------------|
-| `docker-compose.yml` | Single-node quickstart using pre-built images |
-| `docker-compose.dev.yml` | Single-node dev build from source |
-| `docker-compose-3pd-3store-3server.yml` | 3-node distributed cluster |
+| `docker-compose.yml` | Quickstart for a single-host deployment using pre-built images |
+| `docker-compose.dev.yml` | Development mode for a single-host deployment built from source |
+| `docker-compose-3pd-3store-3server.yml` | Distributed cluster with 3 PD, 3 Store, and 3 Server processes |
+
+> **Note**: The following steps assume you have already cloned or pulled the HugeGraph main repository locally, or at least have its `docker/` directory available.
 
 ## Single-Node Quickstart
 
 ```bash
 cd hugegraph/docker
+# Keep the version aligned with the latest release, for example 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose up -d
 ```
 
@@ -47,12 +48,12 @@ cd hugegraph/docker
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
-Startup ordering is enforced automatically:
-1. PD nodes start first and must pass `/v1/health`
-2. Store nodes start after all PD nodes are healthy
-3. Server nodes start after all Store nodes are healthy
+Built-in startup ordering:
+1. PD nodes start first and must pass the `/v1/health` check
+2. Store nodes start only after all PD nodes are healthy
+3. Server nodes start last, after all PD and Store nodes are healthy
 
-Verify the cluster:
+Verify that the cluster is healthy:
 ```bash
 curl http://localhost:8620/v1/health      # PD health
 curl http://localhost:8520/v1/health      # Store health
@@ -76,7 +77,7 @@ curl http://localhost:8620/v1/partitions   # Partition assignment
 | `HG_PD_DATA_PATH` | No | `/hugegraph-pd/pd_data` | `pd.data-path` |
 | `HG_PD_INITIAL_STORE_COUNT` | No | `1` | `pd.initial-store-count` |
 
-**Deprecated aliases**: `GRPC_HOST` → `HG_PD_GRPC_HOST`, `RAFT_ADDRESS` → `HG_PD_RAFT_ADDRESS`, `RAFT_PEERS` → `HG_PD_RAFT_PEERS_LIST`
+> **Deprecated aliases**: `GRPC_HOST` → `HG_PD_GRPC_HOST`, `RAFT_ADDRESS` → `HG_PD_RAFT_ADDRESS`, `RAFT_PEERS` → `HG_PD_RAFT_PEERS_LIST`
 
 ### Store Variables
 
@@ -89,7 +90,7 @@ curl http://localhost:8620/v1/partitions   # Partition assignment
 | `HG_STORE_REST_PORT` | No | `8520` | `server.port` |
 | `HG_STORE_DATA_PATH` | No | `/hugegraph-store/storage` | `app.data-path` |
 
-**Deprecated aliases**: `PD_ADDRESS` → `HG_STORE_PD_ADDRESS`, `GRPC_HOST` → `HG_STORE_GRPC_HOST`, `RAFT_ADDRESS` → `HG_STORE_RAFT_ADDRESS`
+> **Deprecated aliases**: `PD_ADDRESS` → `HG_STORE_PD_ADDRESS`, `GRPC_HOST` → `HG_STORE_GRPC_HOST`, `RAFT_ADDRESS` → `HG_STORE_RAFT_ADDRESS`
 
 ### Server Variables
 
@@ -100,7 +101,7 @@ curl http://localhost:8620/v1/partitions   # Partition assignment
 | `STORE_REST` | No | — | used by `wait-partition.sh` |
 | `PASSWORD` | No | — | enables auth mode |
 
-**Deprecated aliases**: `BACKEND` → `HG_SERVER_BACKEND`, `PD_PEERS` → `HG_SERVER_PD_PEERS`
+> **Deprecated aliases**: `BACKEND` → `HG_SERVER_BACKEND`, `PD_PEERS` → `HG_SERVER_PD_PEERS`
 
 ## Port Reference
 
@@ -124,12 +125,12 @@ curl http://localhost:8620/v1/partitions   # Partition assignment
 
 ## Troubleshooting
 
-**Containers OOM killed (exit code 137)**: Increase Docker Desktop memory to 12 GB+.
+1. **Containers exit due to OOM (`exit code 137`)**: Increase Docker Desktop memory to at least 12 GB, or reduce the JVM heap settings for the process that is being killed.
 
-**Raft leader election timeout**: Check `HG_PD_RAFT_PEERS_LIST` is identical on all PD nodes. Verify connectivity: `docker exec hg-pd0 ping pd1`
+2. **Raft leader election timeout**: Check that `HG_PD_RAFT_PEERS_LIST` is identical on all PD nodes. Verify connectivity with `docker exec hg-pd0 ping pd1`.
 
-**Partition assignment not completing**: Check `curl http://localhost:8620/v1/stores` — all 3 stores must show `"state":"Up"` before partitions are assigned.
+3. **Partition assignment does not complete**: Check `curl http://localhost:8620/v1/stores` and confirm that all 3 stores show `"state":"Up"` before partition assignment can finish.
 
-**Connection refused**: Ensure `HG_*` env vars use container hostnames (`pd0`, `store0`), not `127.0.0.1`.
+4. **Connection refused**: Ensure `HG_*` environment variables use container hostnames (`pd0`, `store0`) instead of `127.0.0.1`.
 
 **Viewing runtime logs**: Use `docker logs <container-name>` (e.g. `docker logs hg-pd0`) to view logs directly without exec-ing into the container.

content/en/docs/quickstart/hugegraph/hugegraph-hstore.md

@@ -52,12 +52,15 @@ mvn clean install -DskipTests=true
 
 #### 3.3 Docker Deployment
 
-The HugeGraph-Store Docker image is available on Docker Hub as `hugegraph/store:1.7.0`.
+The HugeGraph-Store Docker image is available on Docker Hub as `hugegraph/store`.
 
-For a complete 3-node cluster with PD, Store, and Server, use the compose file:
+> **Note**: The following steps assume you have already cloned or pulled the HugeGraph main repository locally, or at least have its `docker/` directory available.
+
+Use the compose file to deploy the complete 3-node cluster (PD + Store + Server):
 
 ```bash
 cd hugegraph/docker
+# Keep the version aligned with the latest release, for example 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
@@ -157,7 +160,7 @@ Ensure that the PD service is already started, then in the Store installation di
 After successful startup, you can see logs similar to the following in `logs/hugegraph-store-server.log`:
 
 ```
-2024-xx-xx xx:xx:xx [main] [INFO] o.a.h.s.n.StoreNodeApplication - Started StoreNodeApplication in x.xxx seconds (JVM running for x.xxx)
+2026-xx-xx xx:xx:xx [main] [INFO] o.a.h.s.n.StoreNodeApplication - Started StoreNodeApplication in x.xxx seconds (JVM running for x.xxx)
 ```
 
 #### 5.2 Stop Store
@@ -229,9 +232,9 @@ pdserver:
   address: 127.0.0.1:8686,127.0.0.1:8687,127.0.0.1:8688
 ```
 
-#### 6.3 Docker Cluster Quickstart
+#### 6.3 Docker Distributed Cluster Configuration
 
-The 3-node Store cluster is included in `docker/docker-compose-3pd-3store-3server.yml`. Each Store node gets its own hostname and env vars:
+The distributed Store cluster definition is included in `docker/docker-compose-3pd-3store-3server.yml`. Each Store node gets its own hostname and environment variables:
 
 ```yaml
 # store0

content/en/docs/quickstart/hugegraph/hugegraph-pd.md

@@ -51,12 +51,15 @@ mvn clean install -DskipTests=true
 
 #### 3.3 Docker Deployment
 
-The HugeGraph-PD Docker image is available on Docker Hub as `hugegraph/pd:1.7.0`.
+The HugeGraph-PD Docker image is available on Docker Hub as `hugegraph/pd`.
 
-For a complete 3-node cluster with PD, Store, and Server, use the compose file:
+> **Note**: The following steps assume you have already cloned or pulled the HugeGraph main repository locally, or at least have its `docker/` directory available.
+
+Use the `docker compose` setup to deploy the complete 3-node cluster (PD + Store + Server):
 
 ```bash
 cd hugegraph/docker
+# Keep the version aligned with the latest release, for example 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose -f docker-compose-3pd-3store-3server.yml up -d
 ```
 
@@ -164,7 +167,7 @@ In the PD installation directory, execute:
 After successful startup, you can see logs similar to the following in `logs/hugegraph-pd-stdout.log`:
 
 ```
-2024-xx-xx xx:xx:xx [main] [INFO] o.a.h.p.b.HugePDServer - Started HugePDServer in x.xxx seconds (JVM running for x.xxx)
+2026-xx-xx xx:xx:xx [main] [INFO] o.a.h.p.b.HugePDServer - Started HugePDServer in x.xxx seconds (JVM running for x.xxx)
 ```
 
 #### 5.2 Stop PD

content/en/docs/quickstart/hugegraph/hugegraph-server.md

@@ -58,14 +58,15 @@ If you use docker desktop, you can set the option like:
 
 > **Note**: The Docker compose files use bridge networking (`hg-net`) and work on Linux and Mac (Docker Desktop). For the 3-node distributed cluster on Mac (Docker Desktop), allocate at least **12 GB** memory (Settings → Resources → Memory). On Linux, Docker uses host memory directly.
 
-Also, if we want to manage HugeGraph-related instances in one file, we can use `docker compose` to deploy.
+If you want a single, unified setup for multiple HugeGraph services, you can use `docker compose`.
 Two compose files are available in the [`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
 
 - **Single-node quickstart** (pre-built images): `docker/docker-compose.yml`
 - **Single-node dev build** (build from source): `docker/docker-compose.dev.yml`
 
 ```bash
 cd hugegraph/docker
+# Keep the version aligned with the latest release, for example 1.x.0
 HUGEGRAPH_VERSION=1.7.0 docker compose up -d
 ```
 
@@ -325,9 +326,9 @@ The sequence to stop the services should be the reverse of the startup sequence:
 bin/stop-hugegraph.sh
 ```
 
-#### Docker Cluster Quickstart
+#### Docker Distributed Cluster
 
-For running the full distributed cluster (3 PD + 3 Store + 3 Server) via Docker:
+Run the full distributed cluster (3 PD + 3 Store + 3 Server) with Docker Compose:
 
 ```bash
 cd hugegraph/docker