Some initial edits
diff --git a/source/guide/index.md b/source/guide/index.md
index de4d3b9..fe24706 100644
--- a/source/guide/index.md
+++ b/source/guide/index.md
@@ -10,25 +10,25 @@
## What is Weex?
-> **Weex is a framework for building high-performance mobile applications with modern web development experience.**
+> **Weex is a framework for building high-performance mobile applications with a modern web development experience.**
-Weex dedicates to enable developers to use modern web development experience to build both Android, iOS and web apps with a single codebase. In practice, you can use javascript and modern front-end frameworks to develop mobile apps after integrating the WeexSDK.
+Weex enables developers to use modern web development experience to build Android, iOS, and web apps with a single codebase. In practice, you can use JavaScript and modern front-end frameworks to develop mobile apps after integrating the WeexSDK.
-The structure of Weex is decoupled, the render engines are separated from the syntax layer. Weex doesn't rely on any specific front-end framework, it mainly supports [Vue.js](https://vuejs.org/) and [Rax](https://alibaba.github.io/rax/).
+The structure of Weex is decoupled: the render engines are separated from the syntax layer. Weex does not rely on any specific front-end framework; however, Weex mainly supports [Vue.js](https://vuejs.org/) and [Rax](https://alibaba.github.io/rax/).
-Another primary goal of Weex is to keep up with modern development technologies and platform capabilities both for web and native. Productivity and performance can coexist in Weex. Writing Weex pages feels the same like writing web pages. Rendering Weex pages is just the same as rendering native pages.
+Another primary goal of Weex is to keep up with modern development technologies and platform capabilities both for web and native. Productivity and performance can coexist in Weex. Writing Weex pages feels the same as writing web pages. In fact, rendering Weex pages is the same as rendering native pages.
## Overview
-If you just want to try Weex, You don't need to install anything. There is an [online playground](http://dotwe.org/vue/) of Weex, you can write single page examples on it without any configurations. The source code should be written in Vue.js [single file component](https://vuejs.org/v2/guide/single-file-components.html) syntax (also known as the `*.vue` files), and the render result of the web platform will be displayed in a mocked phone shell.
+If you just want to try Weex, you do not need to install anything. There is an [online playground](http://dotwe.org/vue/) for Weex wherein you can write single page examples without any installation or configuration. The source code should be written in Vue.js [single file component](https://vuejs.org/v2/guide/single-file-components.html) syntax (also known as the `*.vue` files), and the rendered result from editor pane will be displayed in a mock phone shell.
Here is an [example](http://dotwe.org/vue/8da01827631b21150a12dd54d7114380) written in Weex and Vue.js:
-This example renders a word "Yo" in the center of the screen. If you want to preview the rendered result on mobile devices, you need to install the [Weex playground app](/tools/playground.html) or integrate Weex SDK into your own app. Then scan your page's QR code with your playground app or your own app (with the QR scan feature to load scanned URL with Weex SDK), and you will see the rendered result on your device.
+This example renders a word "Yo" in the center of the screen. If you want to preview the rendered result on mobile devices, you need to install the [Weex playground app](/tools/playground.html), or integrate Weex SDK into your own app and scan your page's QR code with your playground app or your own app (with the QR scan feature to load scanned URL with Weex SDK). Thereafter, you will see the rendered result on your device.
-Within the `<template>` of the source code, You must be familiar with the `<div>` which is widely used on the web, and it's also the generic container on Weex. But the `<text>` component is provided by Weex, it's a block-level text container.
+Within the `<template>` of the source code, you will notice the `<div>` element, which is widely used on the web, and is also the generic container in Weex. The `<text>` component, however, is provided by Weex and is a block-level text container.
> The raw text node can only be placed in the `<text>` component, otherwise, it will be ignored.
@@ -36,7 +36,7 @@
### Native Components
-In the example above, the `<div>` and the `<text>` is rendered into corresponding native views on the mobile device, which is not `HTMLElement`.
+In the example above, the `<div>` and the `<text>` elements are rendered into corresponding native views on the mobile device. As such, they do not implement the `HTMLElement` interface.
@@ -44,33 +44,33 @@
Although the components in Weex look like HTML tags, you are not able to use all of them, instead, you can only use the built-in components and your custom components.
-Under the scene, Weex uses the native widgets. Although Weex emphasize the consistency on each mobile platform, we still embrace the platform's own behavior and UI differences. For example, [the `<switch>` component](http://dotwe.org/vue/d96943452b6708422197c47920903823) may look different on Android and iOS (the appearance on the web simulates iOS).
+Behind the scenes, Weex uses native widgets. Although Weex emphasizes consistency on each mobile platform, we still embrace the platform's own behavior and UI differences. For example, [the `<switch>` component](http://dotwe.org/vue/d96943452b6708422197c47920903823) may look different on Android and iOS (the appearance on the web simulates iOS).
-If you want to use more native component other than the built-in components, you need to implement them on each platform and keep their behaviors to be consistent. The most practical way is to integrate the existing native components to Weex platform.
+If you want to use additional native components, other than the built-in components Weex provides, you need to implement them on each platform and keep their behaviors consistent. The most practical way is to integrate the existing native components to Weex platform. /_ need explanation _/
### Native Modules
-For those features which does not rely on the UI, Weex wraps them into **modules**. You can use `weex.requireModule('xxx')` to require them. It is a way to access native capabilities in javascript, such as network, storage, clipboard, and navigator. For example, you can [use `stream` module to fetch the star count of Vue.js](http://dotwe.org/vue/2ae062b6a04124a35bbe2da3b1e5c07b).
+For those features that do not rely on the UI, Weex wraps them into **modules**. You can use `weex.requireModule('xxx')` to require them. Weex modules provide easy access to native capabilities in JavaScript, such as network, storage, clipboard, and navigator. For example, you can [use `stream` module to fetch the star count of Vue.js](http://dotwe.org/vue/2ae062b6a04124a35bbe2da3b1e5c07b).
-Similarly, Weex also provides a group of [built-in modules](../references/modules/) for basic usage, and supports the integration of the existing native modules to Weex platform.
+Similarly, Weex provides a group of [built-in modules](../references/modules/) for basic usage, and supports the integration of the existing native modules into the Weex platform.
Here are some documents about how to extend native components and native modules for Weex:
-+ [Extend Web Render](./extend-web-render.html)
-+ [Extend Android](./extend-android.html)
-+ [Extend iOS](./extend-ios.html)
+- [Extend Web Render](./extend-web-render.html)
+- [Extend Android](./extend-android.html)
+- [Extend iOS](./extend-ios.html)
### Write Once, Run Everywhere
-Yes, Weex can build for Android, iOS and Web from a single codebase.
+Yes, Weex can build for Android, iOS, and Web from a single codebase.
Using the same source code across different platforms can dramatically increase development productivity and simplify the testing, building, and publishing processes. On this basis, Weex can combine the front-end's packaging and testing process with the mobile's publishing and monitoring system to improve development efficiency.
-> You can read *[How it works](../wiki/index.html)* and *[Design Principles](../wiki/design-principles.html)* to know more about the technologies and ideas behind Weex.
+> You can read _[How it works](../wiki/index.html)_ and _[Design Principles](../wiki/design-principles.html)_ to know more about the technologies and ideas behind Weex.
-Although Weex uses a single codebase, you can still write platform specific codes. Weex provides `weex.config.env` and `WXEnvironment` (they are strictly equal) to get the current runtime environment. You can use `WXEnvironment.platform` to determine which platform the code is running on. Except for the *platform*, `WXEnvironment` also contains other environmental informations, such as *osVersion* and *deviceModel*, refer to *[Weex variable](../references/weex-variable.html)* for the complete list.
+Although Weex uses a single codebase, you can still write platform specific code. Weex provides `weex.config.env` and `WXEnvironment` (they are strictly equal) to get the current runtime environment. You can use `WXEnvironment.platform` to determine which platform the code is running on. Except for the _platform_, `WXEnvironment` contains other information pertaining to environment, such as _osVersion_ and _deviceModel_. Refer to _[Weex variable](../references/weex-variable.html)_ for the complete list.
## Support Multiple Front-End Frameworks
@@ -80,14 +80,14 @@
-+ **Vue.js** is a progressive front-end framework for building user interfaces.
-+ **Rax** is a front-end framework with React-compatible APIs.
+- **Vue.js** is a progressive front-end framework for building user interfaces.
+- **Rax** is a front-end framework with React-compatible APIs.
> Vue.js and Rax are already integrated into Weex SDK, you don't need to require them manually.
-However, Vue and Rax are not the only options, it's possible to integrate other your favorite front-end framework into Weex. There is a document *[Extend JS Framework](./extend-js-framework.html)* that describes how to implement it, but the process is still very complicated and tricky. To achieve it, you need to understand many underlying details about the js-native bridge and native render engines.
+However, Vue and Rax are not the only options, it's possible to integrate other your favorite front-end framework into Weex. There is a document _[Extend JS Framework](./extend-js-framework.html)_ that describes how to implement it, but the process is still very complicated and tricky. To achieve it, you need to understand many underlying details about the js-native bridge and native render engines.
-You can read *[Front-End Frameworks](./front-end-frameworks.html)* to learn more details.
+You can read _[Front-End Frameworks](./front-end-frameworks.html)_ to learn more details.
## Create Your Own App
@@ -164,19 +164,19 @@
If you want to use weex right now:
-+ [Integrate Weex to Your Existing App](./integrate-to-your-app.html)
-+ [Set up Development Environment](./set-up-env.html)
-+ [References](../references/)
+- [Integrate Weex to Your Existing App](./integrate-to-your-app.html)
+- [Set up Development Environment](./set-up-env.html)
+- [References](../references/)
If you want to know the technologies and ideas behind Weex:
-+ [How it Works](../wiki/index.html)
-+ [Design Principles](../wiki/design-principles.html)
-+ [Platform Differences between Weex and Web](../wiki/platform-difference.html)
+- [How it Works](../wiki/index.html)
+- [Design Principles](../wiki/design-principles.html)
+- [Platform Differences between Weex and Web](../wiki/platform-difference.html)
After getting acquainted with Weex, if you want to contribute to make it even better:
-+ [Development Process](../development-process.html)
-+ [How to Contribute](../contributing.html)
+- [Development Process](../development-process.html)
+- [How to Contribute](../contributing.html)
In addition, Weex is a cross-stack technology, developers are also diverse, learn some fundamental knowledge of front-end development, Vue.js, iOS and Android would be especially helpful.
