Revise what-is-kubevela (#315)

* Revise what-is-kubevela

* Apply suggestions from code review

Co-authored-by: Hongchao Deng <hongchaodeng1@gmail.com>

Co-authored-by: Jianbo Sun <wonderflow.sun@gmail.com>
Co-authored-by: Hongchao Deng <hongchaodeng1@gmail.com>

docs/getting-started/introduction.md

@@ -17,7 +17,7 @@ Today the application teams are eager to find a platform that can simplify the a
 
 KubeVela is a modern application platform that makes it easier and faster to deliver and manage applications across hybrid, multi-cloud environments. At the mean time, it is highly extensible and programmable, which can adapt to your needs as they grow. 
 
-![](../resources/system-arch.png)
+![](../resources/what-is-kubevela.png)
 
 
 ## Who should use KubeVela?
@@ -37,7 +37,7 @@ The typical examples are Heroku and Cloud Foundry. They provide full application
 
 Though the biggest difference lies in **flexibility**.
 
-KubeVela does not introduce any restriction. As a plus, even its deployment workflow and full feature set are implemented as LEGO-sytle CUE modules and can be extended at any time when your needs grow. Comparing to this mechanism, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the type of supported applications and capabilities, and as application needs grows, you always outgrow the capabilities of the PaaS system - this will never happen in KubeVela platform.
+KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities -- That means as the platform grows, you always outgrow the capabilities of the PaaS system. Growing and extending is so much easier to do in the KubeVela platform.
 
 ### KubeVela vs. Serverless  
 

i18n/zh/docusaurus-plugin-content-docs/version-v1.1/getting-started/introduction.md

@@ -17,13 +17,13 @@ slug: /
 
 KubeVela 是一个开箱即用的、现代化的应用交付与管理平台。
 
-![](../resources/system-arch.png)
+![](../resources/what-is-kubevela.png)
 
 KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变得非常简单高效：
 
-- **完全以应用为中心** - KubeVela 创新性的提出了[开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。
-- **可编程式交付工作流** - KubeVela 的交付模型是利用 [CUE](https://cuelang.org/) 来实现的。CUE 是一种诞生自 Google Borg 系统的数据配置语言，它可以将应用交付的所有步骤、所需资源、关联的运维动作以可编程的方式粘合成一个 DAG（有向无环图）来作为最终的声明式交付计划。相比于其他系统的复杂性和不可扩展性，KubeVela 基于 CUE 的实现不仅使用简单、扩展性极强，也更符合现代 GitOps 应用交付的趋势与要求。
-- **运行时无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略，面向任何环境交付和管理任何应用组件，比如：容器、云函数、数据库，甚至 AWS EC2 实例等等。
+- **完全以应用为中心** - KubeVela 提出了[开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获和渲染面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。
+- **可编程式交付工作流** - KubeVela 的交付模型是利用 [CUE](https://cuelang.org/) 来实现的。CUE 是一种诞生自 Google Borg 系统的数据配置语言，它可以将应用交付的所有步骤、所需资源、关联的运维动作以可编程的方式编排成一个 DAG（有向无环图）来作为最终的声明式交付计划。相比于其他系统的复杂性和不可扩展性，KubeVela 基于 CUE 的实现不仅使用简单、扩展性极强，也更符合现代 GitOps 应用交付的趋势与要求。
+- **基础设施无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略交付任何工作负载，比如：容器、云函数、数据库、甚至虚拟机实例到任何云或者 Kubernetes 集群当中。
 
 ## 谁应该使用 KubeVela？
 
@@ -43,7 +43,7 @@ KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变
 
 不过，KubeVela 和它们最大的区别在于其**可扩展性**。
 
-KubeVela 对待交付应用没有任何限制，它的整个应用交付与管理能力集也是由独立的可插拔模块（CUE 模块）构成的，这些模块可以随时通过编写 CUE 模板的方式进行增加或者定制。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
+KubeVela 是可编程的。它的交付工作流乃至整个应用交付与管理能力集都是完全由独立的可插拔模块构成的，这些模块可以随时通过编写 CUE 模板的方式进行增/删/重定义且变更会即时生效。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
 
 ### KubeVela vs. Serverless
 

src/data/features.js

@@ -10,7 +10,7 @@ const features = [
         <p>
           <Translate>
             KubeVela introduces Open Application Model (OAM) as the consistent 
-            yet higher level API to capture a full deployment of microservices 
+            yet higher level API to capture and render a full deployment of microservices 
             on top of hybrid environments. Placement strategy, traffic shifting 
             and rolling update are declared at application level. 
             No infrastructure level concern, simply deploy. 
@@ -29,9 +29,9 @@ const features = [
            KubeVela models application delivery as DAG (Directed Acyclic Graph) 
            and expresses it with</Translate> 
             <a href="https://github.com/cuelang/cue"> CUE</a>, <Translate>
-            a modern data configuration language. This allows you to declare 
-            application deployment workflow with all steps and delivery needs 
-            assembled together in programmable approach. No restrictions, 
+            a modern data configuration language. This allows you to design 
+            application deployment steps per needs and
+            orchestrate them in programmable approach. No restrictions, 
             natively extensible.</Translate>
         </p>
       </>
@@ -47,10 +47,10 @@ const features = [
           <Translate>
             KubeVela works as an application 
             delivery control plane that is fully decoupled from runtime 
-            infrastructure. It can deploy and manage any 
-            application types including containers, cloud services, databases, 
-            or even EC2 instances across hybrid environments, following the 
-            workflow you designed.</Translate>
+            infrastructure. It can deploy any 
+            workload types including containers, cloud services, databases, 
+            or even VM instances to any cloud or Kubernetes cluster, following the 
+            workflow designed by you.</Translate>
         </p>
       </>
     ),

src/pages/index.js

@@ -108,7 +108,7 @@ const WhatIs = () => (
               <br />
               <br />
               <Translate>
-                KubeVela is runtime agnostic, natively extensible, yet most importantly, 
+                KubeVela is infrastructure agnostic, programmable, yet most importantly, 
               </Translate><i> <Translate>application-centric.</Translate></i>
             </small>
           </p>

versioned_docs/version-v1.1/getting-started/introduction.md

@@ -17,7 +17,7 @@ Today the application teams are eager to find a platform that can simplify the a
 
 KubeVela is a modern application platform that makes it easier and faster to deliver and manage applications across hybrid, multi-cloud environments. At the mean time, it is highly extensible and programmable, which can adapt to your needs as they grow. 
 
-![](../resources/system-arch.png)
+![](../resources/what-is-kubevela.png)
 
 ## Who should use KubeVela?
 
@@ -36,7 +36,7 @@ The typical examples are Heroku and Cloud Foundry. They provide full application
 
 Though the biggest difference lies in **flexibility**.
 
-KubeVela does not introduce any restriction. As a plus, even its deployment workflow and full feature set are implemented as LEGO-sytle CUE modules and can be extended at any time when your needs grow. Comparing to this mechanism, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the type of supported applications and capabilities, and as application needs grows, you always outgrow the capabilities of the PaaS system - this will never happen in KubeVela platform.
+KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities -- That means as the platform grows, you always outgrow the capabilities of the PaaS system. Growing and extending is so much easier to do in the KubeVela platform.
 
 ### KubeVela vs. Serverless