Add UI startup.sh description.

docs/en/Deploy-collector-in-cluster-mode.md

@@ -77,3 +77,5 @@ storage:
 
 
 3. Run `bin/startup.sh`
+
+- NOTICE: **In 5.0.0-alpha, startup.sh will start two processes, collector and UI, and UI uses 127.0.0.1:10800 as default.**

docs/en/Deploy-collector-in-standalone-mode.md

@@ -3,7 +3,7 @@ Default standalong mode collector means don't support cluster. It uses H2 as sto
 
 If you are using skywalking in a low throughputs monitoring scenario, and don't want to deploy cluster, at least, switch the storage implementation from H2 to  Elasticsearch.
 
-**H2 storage implementation is not provided in 5.0.0-alpha**
+**H2 storage implementation is not provided in 5.0.0-alpha, so you must deploy ElasticSearch before try to start backend**
 
 ## Requirements
 * JDK 8+
@@ -19,6 +19,8 @@ You can simplely tar/unzip and startup if ports 10800, 11800, 12800 are free.
 
 You should keep the `config/application.yml` as default.
 
+- NOTICE: **In 5.0.0-alpha, startup.sh will start two processes, collector and UI, and UI uses 127.0.0.1:10800 as default.**
+
 ## Use Elastic Search instead of H2 as storage layer implementation
 Even in standalone mode, collector can run with Elastic Search as storage. If so, uncomment the `storage` section in `application.yml`, set the config right. The default configs fit for collector and Elasticsearch both running in same machine, and not cluster.
 

docs/en/Quick-start.md

@@ -1,8 +1,7 @@
 # Quick start
 1. Download `org.apache.skywalking.apm-dist` in maven central. Or find `skywalking-dist.tar.gz/.zip` in `dist` folder after `mvn clean package`.
-1. Deploy Collector
-   1. [Standalone Mode](Deploy-collector-in-standalone-mode.md)
-   1. [Cluster Mode](Deploy-collector-in-cluster-mode.md)
-1. Deploy webui server [WIP]
+1. Deploy Backend
+   - [Standalone Mode](Deploy-collector-in-standalone-mode.md)
+   - [Cluster Mode](Deploy-collector-in-cluster-mode.md)
 1. Deploy Java Agent，[doc](Deploy-skywalking-agent.md)
 1. Reboot your applications, and open UI.