This is an automated email from the ASF dual-hosted git repository.
lidongdai 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 27c00ed377 [Document] Fix grammar and spelling (#12940)
27c00ed377 is described below
commit 27c00ed3772113e4eb7c53035360d3e3dbf55e66
Author: John Bampton <[email protected]>
AuthorDate: Mon Nov 21 22:58:03 2022 +1000
[Document] Fix grammar and spelling (#12940)
---
docs/docs/en/architecture/configuration.md | 4 ++--
docs/docs/en/contribute/frontend-development.md | 2 +-
docs/docs/en/contribute/join/unit-test.md | 2 +-
docs/docs/en/contribute/release/release.md | 4 ++--
docs/docs/en/guide/task/sqoop.md | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/docs/en/architecture/configuration.md
b/docs/docs/en/architecture/configuration.md
index be3cddc31b..051a7a6f15 100644
--- a/docs/docs/en/architecture/configuration.md
+++ b/docs/docs/en/architecture/configuration.md
@@ -277,7 +277,7 @@ Location: `master-server/conf/application.yaml`
|master.failover-interval|10|failover interval, the unit is minute|
|master.kill-yarn-job-when-task-failover|true|whether to kill yarn job when
failover taskInstance|
|master.registry-disconnect-strategy.strategy|stop|Used when the master
disconnect from registry, default value: stop. Optional values include stop,
waiting|
-|master.registry-disconnect-strategy.max-waiting-time|100s|Used when the
master disconnect from registry, and the disconnect strategy is waiting, this
config means the master will waiting to reconnect to registry in given times,
and after the waiting times, if the master still cannot connect to registry,
will stop itself, if the value is 0s, the Master will waitting infinitely|
+|master.registry-disconnect-strategy.max-waiting-time|100s|Used when the
master disconnect from registry, and the disconnect strategy is waiting, this
config means the master will waiting to reconnect to registry in given times,
and after the waiting times, if the master still cannot connect to registry,
will stop itself, if the value is 0s, the Master will wait infinitely|
|master.worker-group-refresh-interval|10s|The interval to refresh worker group
from db to memory|
### Worker Server related configuration
@@ -296,7 +296,7 @@ Location: `worker-server/conf/application.yaml`
|worker.alert-listen-host|localhost|the alert listen host of worker|
|worker.alert-listen-port|50052|the alert listen port of worker|
|worker.registry-disconnect-strategy.strategy|stop|Used when the worker
disconnect from registry, default value: stop. Optional values include stop,
waiting|
-|worker.registry-disconnect-strategy.max-waiting-time|100s|Used when the
worker disconnect from registry, and the disconnect strategy is waiting, this
config means the worker will waiting to reconnect to registry in given times,
and after the waiting times, if the worker still cannot connect to registry,
will stop itself, if the value is 0s, will waitting infinitely |
+|worker.registry-disconnect-strategy.max-waiting-time|100s|Used when the
worker disconnect from registry, and the disconnect strategy is waiting, this
config means the worker will waiting to reconnect to registry in given times,
and after the waiting times, if the worker still cannot connect to registry,
will stop itself, if the value is 0s, will wait infinitely |
|worker.task-execute-threads-full-policy|REJECT|If REJECT, when the task
waiting in the worker reaches exec-threads, it will reject the received task
and the Master will redispatch it; If CONTINUE, it will put the task into the
worker's execution queue and wait for a free thread to start execution|
### Alert Server related configuration
diff --git a/docs/docs/en/contribute/frontend-development.md
b/docs/docs/en/contribute/frontend-development.md
index 9ab23cc5be..0cc86811f8 100644
--- a/docs/docs/en/contribute/frontend-development.md
+++ b/docs/docs/en/contribute/frontend-development.md
@@ -125,7 +125,7 @@ Execute `pm2 start npm -- run dev` to start the project in
the project `dolphins
- The corresponding html file is in `src/view/${corresponding page filename =>
home}/index.html`
```
-Public module and utill `src/js/module`
+Public module and util `src/js/module`
`components` => internal project common components
diff --git a/docs/docs/en/contribute/join/unit-test.md
b/docs/docs/en/contribute/join/unit-test.md
index 7cc02c29b3..d562370d95 100644
--- a/docs/docs/en/contribute/join/unit-test.md
+++ b/docs/docs/en/contribute/join/unit-test.md
@@ -44,7 +44,7 @@ Multiple executions (any environment, any time) result in
unique and repeatable
That is, any environment can be implemented quickly.
-This requires that we don't rely on too many components, such as various
spring beans and the like. These are all mock in unit tests, nd adding them
would increase the speed of our single-test execution, as well as potentially
passing on contamination.
+This requires that we don't rely on too many components, such as various
spring beans and the like. These are all mock in unit tests, and adding them
would increase the speed of our single-test execution, as well as potentially
passing on contamination.
For some databases, other external components, etc. As far as possible, the
mock client is not dependent on the external environment (the presence of any
external dependencies greatly limits the portability and stability of test
cases and the correctness of results), which also makes it easy for developers
to test in any environment.
diff --git a/docs/docs/en/contribute/release/release.md
b/docs/docs/en/contribute/release/release.md
index cd602674bb..10e7fd1887 100644
--- a/docs/docs/en/contribute/release/release.md
+++ b/docs/docs/en/contribute/release/release.md
@@ -145,8 +145,8 @@ A_USERNAME=<YOUR-APACHE-USERNAME>
> Note: We can use the variable directly in you bash after we set environment,
> without changing anything. For example, we
> can use command `git clone -b "${VERSION}"-prepare
> https://github.com/apache/dolphinscheduler.git` to clone the release branch
-> and it can be success by covert the `"${VERSION}"` to
`<THE-VERSION-YOU-RELEASE>`. But you have to change `<VERSION>` manually in
-> some of not bash step like [vote mail](#vote-procedure), we using
`<VERSION>` instead of `"${VERSION}"` to notice release
+> and it can be successful by converting the `"${VERSION}"` to
`<THE-VERSION-YOU-RELEASE>`. But you have to change `<VERSION>` manually in
+> some of not bash step like [vote mail](#vote-procedure), we are using
`<VERSION>` instead of `"${VERSION}"` to notice release
> manager they have to change by hand.
### Create Release Branch
diff --git a/docs/docs/en/guide/task/sqoop.md b/docs/docs/en/guide/task/sqoop.md
index e2d65debbd..f62e0ab724 100644
--- a/docs/docs/en/guide/task/sqoop.md
+++ b/docs/docs/en/guide/task/sqoop.md
@@ -19,7 +19,7 @@ Sqoop task type for executing Sqoop application. The workers
run `sqoop` to exec
| **Parameter** |
**Description**
|
|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Job Name | map-reduce job name
|
-| Direct | (1) import:Imports an individual table
from an RDBMS to HDFS or Hve. (2) export:Exports a set of files from HDFS or
Hive back to an RDBMS. |
+| Direct | (1) import:Imports an individual table
from an RDBMS to HDFS or Hive. (2) export:Exports a set of files from HDFS or
Hive back to an RDBMS. |
| Hadoop Params | Hadoop custom param for sqoop job.
|
| Sqoop Advanced Parameters | Sqoop advanced param for sqoop job.
|
| Data Source - Type | Select the corresponding data source
type.
|
