You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by li...@apache.org on 2021/02/27 14:16:11 UTC
[incubator-dolphinscheduler-website] branch master updated: chore:
fix spelling (#300)
This is an automated email from the ASF dual-hosted git repository.
lidongdai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new 464dbea chore: fix spelling (#300)
464dbea is described below
commit 464dbeab8236c8d2c2cf1d43373363e34d5288dd
Author: John Bampton <jb...@users.noreply.github.com>
AuthorDate: Sun Feb 28 00:15:52 2021 +1000
chore: fix spelling (#300)
---
docs/en-us/1.2.0/user_doc/metadata-1.2.md | 2 +-
docs/en-us/1.2.1/user_doc/metadata-1.2.md | 2 +-
docs/en-us/1.3.2/user_doc/metadata-1.3.md | 2 +-
docs/en-us/1.3.2/user_doc/upgrade.md | 2 +-
docs/en-us/1.3.3/user_doc/metadata-1.3.md | 2 +-
docs/en-us/1.3.3/user_doc/upgrade.md | 2 +-
docs/en-us/1.3.4/user_doc/metadata-1.3.md | 2 +-
docs/en-us/1.3.4/user_doc/system-manual.md | 2 +-
docs/en-us/1.3.4/user_doc/task-structure.md | 2 +-
docs/en-us/1.3.4/user_doc/upgrade.md | 2 +-
docs/en-us/1.3.5/user_doc/metadata-1.3.md | 2 +-
docs/en-us/1.3.5/user_doc/system-manual.md | 2 +-
docs/en-us/1.3.5/user_doc/task-structure.md | 2 +-
docs/en-us/1.3.5/user_doc/upgrade.md | 2 +-
docs/en-us/release/faq.md | 4 ++--
15 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/docs/en-us/1.2.0/user_doc/metadata-1.2.md b/docs/en-us/1.2.0/user_doc/metadata-1.2.md
index 2d706f9..19616ef 100644
--- a/docs/en-us/1.2.0/user_doc/metadata-1.2.md
+++ b/docs/en-us/1.2.0/user_doc/metadata-1.2.md
@@ -40,7 +40,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.2.1/user_doc/metadata-1.2.md b/docs/en-us/1.2.1/user_doc/metadata-1.2.md
index 2d706f9..19616ef 100644
--- a/docs/en-us/1.2.1/user_doc/metadata-1.2.md
+++ b/docs/en-us/1.2.1/user_doc/metadata-1.2.md
@@ -40,7 +40,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.3.2/user_doc/metadata-1.3.md b/docs/en-us/1.3.2/user_doc/metadata-1.3.md
index 223867a..5de8b3d 100644
--- a/docs/en-us/1.3.2/user_doc/metadata-1.3.md
+++ b/docs/en-us/1.3.2/user_doc/metadata-1.3.md
@@ -39,7 +39,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.3.2/user_doc/upgrade.md b/docs/en-us/1.3.2/user_doc/upgrade.md
index ca37b3b..f11a901 100644
--- a/docs/en-us/1.3.2/user_doc/upgrade.md
+++ b/docs/en-us/1.3.2/user_doc/upgrade.md
@@ -62,7 +62,7 @@ Imaging bellow are the machine worker service to be deployed:
| ds2 | 192.168.xx.11 |
| ds3 | 192.168.xx.12 |
-To keep worker group config consistant with previous version, we need to modify workers config item as below:
+To keep worker group config consistent with previous version, we need to modify workers config item as below:
```shell
#worker service is deployed on which machine, and also specify which worker group this worker belong to.
diff --git a/docs/en-us/1.3.3/user_doc/metadata-1.3.md b/docs/en-us/1.3.3/user_doc/metadata-1.3.md
index 223867a..5de8b3d 100644
--- a/docs/en-us/1.3.3/user_doc/metadata-1.3.md
+++ b/docs/en-us/1.3.3/user_doc/metadata-1.3.md
@@ -39,7 +39,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.3.3/user_doc/upgrade.md b/docs/en-us/1.3.3/user_doc/upgrade.md
index 58947ed..d9136d4 100644
--- a/docs/en-us/1.3.3/user_doc/upgrade.md
+++ b/docs/en-us/1.3.3/user_doc/upgrade.md
@@ -62,7 +62,7 @@ Imaging bellow are the machine worker service to be deployed:
| ds2 | 192.168.xx.11 |
| ds3 | 192.168.xx.12 |
-To keep worker group config consistant with previous version, we need to modify workers config item as below:
+To keep worker group config consistent with previous version, we need to modify workers config item as below:
```shell
#worker service is deployed on which machine, and also specify which worker group this worker belong to.
diff --git a/docs/en-us/1.3.4/user_doc/metadata-1.3.md b/docs/en-us/1.3.4/user_doc/metadata-1.3.md
index 223867a..5de8b3d 100644
--- a/docs/en-us/1.3.4/user_doc/metadata-1.3.md
+++ b/docs/en-us/1.3.4/user_doc/metadata-1.3.md
@@ -39,7 +39,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.3.4/user_doc/system-manual.md b/docs/en-us/1.3.4/user_doc/system-manual.md
index 6a388db..2916b39 100644
--- a/docs/en-us/1.3.4/user_doc/system-manual.md
+++ b/docs/en-us/1.3.4/user_doc/system-manual.md
@@ -116,7 +116,7 @@ The operation functions of the workflow definition list are as follows:
* Notification group: select notification strategy||timeout alarm||when fault tolerance occurs, process information or email will be sent to all members in the notification group.
* Recipient: Select notification policy||Timeout alarm||When fault tolerance occurs, process information or alarm email will be sent to the recipient list.
* Cc: Select the notification strategy||Timeout alarm||When fault tolerance occurs, the process information or warning email will be copied to the CC list.
- * Startup paramter: Set or overwrite global paramter values when starting a new process instance.
+ * Startup parameter: Set or overwrite global parameter values when starting a new process instance.
* Complement: Two modes including serial complement and parallel complement. Serial complement: within the specified time range, the complement is executed sequentially from the start date to the end date, and only one process instance is generated; parallel complement: within the specified time range, multiple days are complemented at the same time to generate N process instances.
* For example, you need to fill in the data from May 1 to May 10.
diff --git a/docs/en-us/1.3.4/user_doc/task-structure.md b/docs/en-us/1.3.4/user_doc/task-structure.md
index 378f14c..2c380fd 100644
--- a/docs/en-us/1.3.4/user_doc/task-structure.md
+++ b/docs/en-us/1.3.4/user_doc/task-structure.md
@@ -17,7 +17,7 @@ No. | field | type | description
8|description|text|process definition description
9|global_params|text|global parameters
10|flag|tinyint(4)|specify whether the process is available: 0 is not available, 1 is available
-11|locations|text|node location infomation
+11|locations|text|node location information
12|connects|text|node connectivity info
13|receivers|text|receivers
14|receivers_cc|text|CC receivers
diff --git a/docs/en-us/1.3.4/user_doc/upgrade.md b/docs/en-us/1.3.4/user_doc/upgrade.md
index 9fca4fe..eb1f13f 100644
--- a/docs/en-us/1.3.4/user_doc/upgrade.md
+++ b/docs/en-us/1.3.4/user_doc/upgrade.md
@@ -62,7 +62,7 @@ Imaging bellow are the machine worker service to be deployed:
| ds2 | 192.168.xx.11 |
| ds3 | 192.168.xx.12 |
-To keep worker group config consistant with previous version, we need to modify workers config item as below:
+To keep worker group config consistent with previous version, we need to modify workers config item as below:
```shell
#worker service is deployed on which machine, and also specify which worker group this worker belong to.
diff --git a/docs/en-us/1.3.5/user_doc/metadata-1.3.md b/docs/en-us/1.3.5/user_doc/metadata-1.3.md
index 223867a..5de8b3d 100644
--- a/docs/en-us/1.3.5/user_doc/metadata-1.3.md
+++ b/docs/en-us/1.3.5/user_doc/metadata-1.3.md
@@ -39,7 +39,7 @@
- Multiple users can belong to one tenant
-- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue infomation using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
+- The queue field in t_ds_user table stores the queue_name information in t_ds_queue table, but t_ds_tenant stores queue information using queue_id. During the execution of the process definition, the user queue has the highest priority. If the user queue is empty, the tenant queue is used.
- The user_id field in the t_ds_datasource table indicates the user who created the data source. The user_id in t_ds_relation_datasource_user indicates the user who has permission to the data source.
<a name="7euSN"></a>
#### Project Resource Alert
diff --git a/docs/en-us/1.3.5/user_doc/system-manual.md b/docs/en-us/1.3.5/user_doc/system-manual.md
index 6a388db..2916b39 100644
--- a/docs/en-us/1.3.5/user_doc/system-manual.md
+++ b/docs/en-us/1.3.5/user_doc/system-manual.md
@@ -116,7 +116,7 @@ The operation functions of the workflow definition list are as follows:
* Notification group: select notification strategy||timeout alarm||when fault tolerance occurs, process information or email will be sent to all members in the notification group.
* Recipient: Select notification policy||Timeout alarm||When fault tolerance occurs, process information or alarm email will be sent to the recipient list.
* Cc: Select the notification strategy||Timeout alarm||When fault tolerance occurs, the process information or warning email will be copied to the CC list.
- * Startup paramter: Set or overwrite global paramter values when starting a new process instance.
+ * Startup parameter: Set or overwrite global parameter values when starting a new process instance.
* Complement: Two modes including serial complement and parallel complement. Serial complement: within the specified time range, the complement is executed sequentially from the start date to the end date, and only one process instance is generated; parallel complement: within the specified time range, multiple days are complemented at the same time to generate N process instances.
* For example, you need to fill in the data from May 1 to May 10.
diff --git a/docs/en-us/1.3.5/user_doc/task-structure.md b/docs/en-us/1.3.5/user_doc/task-structure.md
index 378f14c..2c380fd 100644
--- a/docs/en-us/1.3.5/user_doc/task-structure.md
+++ b/docs/en-us/1.3.5/user_doc/task-structure.md
@@ -17,7 +17,7 @@ No. | field | type | description
8|description|text|process definition description
9|global_params|text|global parameters
10|flag|tinyint(4)|specify whether the process is available: 0 is not available, 1 is available
-11|locations|text|node location infomation
+11|locations|text|node location information
12|connects|text|node connectivity info
13|receivers|text|receivers
14|receivers_cc|text|CC receivers
diff --git a/docs/en-us/1.3.5/user_doc/upgrade.md b/docs/en-us/1.3.5/user_doc/upgrade.md
index 2ea0764..a6598dc 100644
--- a/docs/en-us/1.3.5/user_doc/upgrade.md
+++ b/docs/en-us/1.3.5/user_doc/upgrade.md
@@ -62,7 +62,7 @@ Imaging bellow are the machine worker service to be deployed:
| ds2 | 192.168.xx.11 |
| ds3 | 192.168.xx.12 |
-To keep worker group config consistant with previous version, we need to modify workers config item as below:
+To keep worker group config consistent with previous version, we need to modify workers config item as below:
```shell
#worker service is deployed on which machine, and also specify which worker group this worker belong to.
diff --git a/docs/en-us/release/faq.md b/docs/en-us/release/faq.md
index 6dbf20b..9eb1c1b 100644
--- a/docs/en-us/release/faq.md
+++ b/docs/en-us/release/faq.md
@@ -324,7 +324,7 @@ A: 1, The release process of Apache Project happens in the mailing list. You can
---
## Q : Subsequent tasks can execute even front task failed
-A: When start the workflow, you can set the task failure strategy: contine or failure.
+A: When start the workflow, you can set the task failure strategy: continue or failure.
---
@@ -357,7 +357,7 @@ A: For version 1.3.0, we want to support k8s, while the ip always will be change
---
## Q : Why not add mysql jdbc connector to docker image
-A: The license of mysql jdbc connector is not compitable with apache v2 license, so it can't be included by docker image.
+A: The license of mysql jdbc connector is not compatible with apache v2 license, so it can't be included by docker image.
---