You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by zh...@apache.org on 2020/07/18 03:22:17 UTC

[shardingsphere-elasticjob] branch master updated: Revise #1120 (#1123)

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

zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere-elasticjob.git


The following commit(s) were added to refs/heads/master by this push:
     new 35979cd  Revise #1120 (#1123)
35979cd is described below

commit 35979cd7d93626639637fef026a639f99910e51d
Author: Liang Zhang <te...@163.com>
AuthorDate: Sat Jul 18 11:22:09 2020 +0800

    Revise #1120 (#1123)
---
 docs/content/features/schedule-model.en.md                     |  2 +-
 .../elasticjob-lite/usage/job-api/spring-namespace.en.md       | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/content/features/schedule-model.en.md b/docs/content/features/schedule-model.en.md
index 63089f7..a3f5599 100644
--- a/docs/content/features/schedule-model.en.md
+++ b/docs/content/features/schedule-model.en.md
@@ -10,7 +10,7 @@ Unlike most job platforms, ElasticJob's scheduling model is divided into in-proc
 ## In-process scheduling
 
 ElasticJob Lite is a thread-level scheduling framework for in-process. Through it, Job can be transparently combined with business application systems.
-It can be easily used in conjunction with Java frameworks such as Spring and Dubbo. Spring DI Beans can be freely used in Job, such as data source connection pool and Dubbo remote service, etc., which is more convenient for business development.
+It can be easily used in conjunction with Java frameworks such as Spring and Dubbo. Spring DI (Dependency Injection) Beans can be freely used in Job, such as data source connection pool and Dubbo remote service, etc., which is more convenient for business development.
 
 ## Process-level scheduling
 
diff --git a/docs/content/user-manual/elasticjob-lite/usage/job-api/spring-namespace.en.md b/docs/content/user-manual/elasticjob-lite/usage/job-api/spring-namespace.en.md
index ac62305..6fdf337 100644
--- a/docs/content/user-manual/elasticjob-lite/usage/job-api/spring-namespace.en.md
+++ b/docs/content/user-manual/elasticjob-lite/usage/job-api/spring-namespace.en.md
@@ -5,7 +5,7 @@ chapter = true
 +++
 
 ElasticJob-Lite provides a custom Spring namespace, which can be used with the Spring.
-Through the way of DI, developers can easily use data sources and other objects that managed by the Spring container in their jobs, and use placeholders to get values ​​from property files.
+Through the way of DI (Dependency Injection), developers can easily use data sources and other objects that managed by the Spring container in their jobs, and use placeholders to get values ​​from property files.
 
 ## Config job for Spring namespace
 
@@ -19,18 +19,18 @@ Through the way of DI, developers can easily use data sources and other objects
                         http://shardingsphere.apache.org/schema/elasticjob
                         http://shardingsphere.apache.org/schema/elasticjob/elasticjob.xsd
                         ">
-    <!-- config registry center for job -->
+    <!-- Configure registry center for job -->
     <elasticjob:zookeeper id="regCenter" server-lists="yourhost:2181" namespace="dd-job" base-sleep-time-milliseconds="1000" max-sleep-time-milliseconds="3000" max-retries="3" />
     
-    <!-- config job java bean -->
+    <!-- Configure job java bean -->
     <bean id="myJob" class="xxx.MyJob">
         <property name="fooService" ref="xxx.FooService" />
     </bean>
     
-    <!-- config job scheduler base on java bean -->   
+    <!-- Configure job scheduler base on java bean -->   
     <elasticjob:job id="${myJob.id}" job-ref="myJob" registry-center-ref="regCenter" sharding-total-count="${myJob.shardingTotalCount}" cron="${myJob.cron}" />
     
-   <!-- config job scheduler base on type --> 
+   <!-- Configure job scheduler base on type --> 
     <elasticjob:job id="${myScriptJob.id}" job-type="SCRIPT" registry-center-ref="regCenter" sharding-total-count="${myScriptJob.shardingTotalCount}" cron="${myScriptJob.cron}">
         <props>
             <prop key="script.command.line">${myScriptJob.scriptCommandLine}</prop>