This is an automated email from the ASF dual-hosted git repository.

zihaoxiang pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git


The following commit(s) were added to refs/heads/dev by this push:
     new ec01df1305 docs: fix several issues in installation md (#16079)
ec01df1305 is described below

commit ec01df130530568f20f2ec5eab0e44e24119d066
Author: lwyang <[email protected]>
AuthorDate: Tue May 28 14:14:48 2024 +0800

    docs: fix several issues in installation md (#16079)
    
    Co-authored-by: Eric Gao <[email protected]>
---
 docs/docs/en/guide/installation/cluster.md        | 2 +-
 docs/docs/en/guide/installation/pseudo-cluster.md | 2 +-
 docs/docs/en/guide/installation/standalone.md     | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/docs/en/guide/installation/cluster.md 
b/docs/docs/en/guide/installation/cluster.md
index 14ae58a479..0014a9c7f1 100644
--- a/docs/docs/en/guide/installation/cluster.md
+++ b/docs/docs/en/guide/installation/cluster.md
@@ -14,7 +14,7 @@ Configure all the configurations refer to [pseudo-cluster 
deployment](pseudo-clu
 
 ### Modify Configuration
 
-This step differs quite a lot from [pseudo-cluster 
deployment](pseudo-cluster.md), because the deployment script transfers the 
required resources for installation to each deployment machine by using `scp`. 
So we only need to modify the configuration of the machine that runs 
`install.sh` script and configurations will dispatch to cluster by `scp`. The 
configuration file is under the path `bin/env/install_env.sh`, here we only 
need to modify section **INSTALL MACHINE**, **DolphinScheduler  [...]
+This step differs quite a lot from [pseudo-cluster 
deployment](pseudo-cluster.md), because the deployment script transfers the 
required resources for installation to each deployment machine by using `scp`. 
So we only need to modify the configuration of the machine that runs 
`install.sh` script and configurations will dispatch to cluster by `scp`. The 
configuration file is under the path `bin/env/install_env.sh`, here we only 
need to modify section **INSTALL MACHINE**, **DolphinScheduler  [...]
 
 ```shell
 # ---------------------------------------------------------
diff --git a/docs/docs/en/guide/installation/pseudo-cluster.md 
b/docs/docs/en/guide/installation/pseudo-cluster.md
index 7a3b43b00e..64f28022e4 100644
--- a/docs/docs/en/guide/installation/pseudo-cluster.md
+++ b/docs/docs/en/guide/installation/pseudo-cluster.md
@@ -2,7 +2,7 @@
 
 The purpose of the pseudo-cluster deployment is to deploy the DolphinScheduler 
service on a single machine. In this mode, DolphinScheduler's master, worker, 
API server, are all on the same machine.
 
-If you are a new hand and want to experience DolphinScheduler functions, we 
recommend you install follow [Standalone deployment](standalone.md). If you 
want to experience more complete functions and schedule massive tasks, we 
recommend you install follow[pseudo-cluster deployment. If you want to deploy 
DolphinScheduler in production, we recommend you follow [cluster 
deployment](cluster.md) or [Kubernetes deployment](kubernetes.md).
+If you are a new hand and want to experience DolphinScheduler functions, we 
recommend you install follow [Standalone deployment](standalone.md). If you 
want to experience more complete functions and schedule massive tasks, we 
recommend you install follow [pseudo-cluster deployment](pseudo-cluster.md). If 
you want to deploy DolphinScheduler in production, we recommend you follow 
[cluster deployment](cluster.md) or [Kubernetes deployment](kubernetes.md).
 
 ## Preparation
 
diff --git a/docs/docs/en/guide/installation/standalone.md 
b/docs/docs/en/guide/installation/standalone.md
index bd2d73f1ce..ac78e7817f 100644
--- a/docs/docs/en/guide/installation/standalone.md
+++ b/docs/docs/en/guide/installation/standalone.md
@@ -36,7 +36,7 @@ Access address `http://localhost:12345/dolphinscheduler/ui` 
and login DolphinSch
 
 ### Start or Stop Server
 
-The script `./bin/dolphinscheduler-daemon.sh`can be used not only quickly 
start standalone, but also to stop the service operation. The following are all 
the commands:
+The script `./bin/dolphinscheduler-daemon.sh` can be used not only quickly 
start standalone, but also to stop the service operation. The following are all 
the commands:
 
 ```shell
 # Start Standalone Server

Reply via email to