[dolphinscheduler-website] branch asf-site updated: Automated deployment: e0a0c7de119e7c51cb4294c9a7d353b06c96da8a

[github-bot]

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

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 169ab55  Automated deployment: e0a0c7de119e7c51cb4294c9a7d353b06c96da8a
169ab55 is described below

commit 169ab559210117513bc32646732397f28e982676
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Dec 20 10:46:27 2021 +0000

    Automated deployment: e0a0c7de119e7c51cb4294c9a7d353b06c96da8a
---
 en-us/docs/dev/user_doc/architecture/design.html | 4 ++--
 en-us/docs/dev/user_doc/architecture/design.json | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/en-us/docs/dev/user_doc/architecture/design.html 
b/en-us/docs/dev/user_doc/architecture/design.html
index 953b31d..9749ef9 100644
--- a/en-us/docs/dev/user_doc/architecture/design.html
+++ b/en-us/docs/dev/user_doc/architecture/design.html
@@ -223,13 +223,13 @@ After the fault tolerance of ZooKeeper Master is 
completed, it is re-scheduled b
 <li>
 <p>The priority of the process definition is to consider that some processes 
need to be processed before other processes. This can be configured when the 
process is started or scheduled to start. There are 5 levels in total, which 
are HIGHEST, HIGH, MEDIUM, LOW, and LOWEST. As shown below</p>
   <p align="center">
-     <img 
src="https://analysys.github.io/easyscheduler_docs_cn/images/process_priority.png";
 alt="Process priority configuration"  width="40%" />
+     <img 
src="https://user-images.githubusercontent.com/10797147/146744784-eb351b14-c94a-4ed6-8ba4-5132c2a3d116.png";
 alt="Process priority configuration"  width="40%" />
    </p>
 </li>
 <li>
 <p>The priority of the task is also divided into 5 levels, followed by 
HIGHEST, HIGH, MEDIUM, LOW, LOWEST. As shown below</p>
   <p align="center">
-     <img 
src="https://analysys.github.io/easyscheduler_docs_cn/images/task_priority.png"; 
alt="Task priority configuration"  width="35%" />
+     <img 
src="https://user-images.githubusercontent.com/10797147/146744830-5eac611f-5933-4f53-a0c6-31613c283708.png";
 alt="Task priority configuration"  width="35%" />
    </p>
 </li>
 </ul>
diff --git a/en-us/docs/dev/user_doc/architecture/design.json 
b/en-us/docs/dev/user_doc/architecture/design.json
index be61315..5e7b231 100644
--- a/en-us/docs/dev/user_doc/architecture/design.json
+++ b/en-us/docs/dev/user_doc/architecture/design.json
@@ -1,6 +1,6 @@
 {
   "filename": "design.md",
-  "__html": "<h2>System Architecture Design</h2>\n<p>Before explaining the 
architecture of the scheduling system, let's first understand the commonly used 
terms of the scheduling 
system</p>\n<h3>1.Glossary</h3>\n<p><strong>DAG：</strong> The full name is 
Directed Acyclic Graph, referred to as DAG. Task tasks in the workflow are 
assembled in the form of a directed acyclic graph, and topological traversal is 
performed from nodes with zero degrees of entry until there are no subsequent 
nodes [...]
+  "__html": "<h2>System Architecture Design</h2>\n<p>Before explaining the 
architecture of the scheduling system, let's first understand the commonly used 
terms of the scheduling 
system</p>\n<h3>1.Glossary</h3>\n<p><strong>DAG：</strong> The full name is 
Directed Acyclic Graph, referred to as DAG. Task tasks in the workflow are 
assembled in the form of a directed acyclic graph, and topological traversal is 
performed from nodes with zero degrees of entry until there are no subsequent 
nodes [...]
   "link": "/dist/en-us/docs/dev/user_doc/architecture/design.html",
   "meta": {}
 }
\ No newline at end of file