Readme refactoring (#2038)

Author: xwang98

README.md

@@ -1,28 +1,27 @@
-Application framework
-=======
-
-## Directory structure
+# Application framework
 
+By using the WAMR VM core, we are flexible to build different application frameworks for the specific domains, although it would take quite some effort.
 
+The WAMR has offered a comprehensive framework for programming WASM applications for device and IoT usages. The framework supports running multiple applications, that are based on the event driven programming model. Here are the supporting API sets by the [WAMR application framework library](../doc/wamr_api.md) :
 
-This folder "app-native-shared" is for the source files shared by both WASM APP and native runtime
+- Timer,  Inter-app communication (request/response and pub/sub), Sensor, Connectivity and data transmission, 2D graphic UI
 
-- The c files in this directory are compiled into both the WASM APP and runtime.
-- The header files for distributing to SDK are placed in the "bi-inc" folder.
+Browse the folder  [core/app-framework](./app-framework) for how to extend the application framework.
 
 
+## Directory structure
+This folder "app-native-shared" is for the source files shared by both WASM APP and native runtime  
 
-This folder "template" contains a pre-defined directory structure for a framework component. The developers can copy the template folder to create new components to the application framework.
-
+- The c files in this directory are compiled into both the WASM APP and runtime.
+- The header files for distributing to SDK are placed in the "bi-inc" folder.
 
+This folder "template" contains a pre-defined directory structure for a framework component. The developers can copy the template folder to create new components to the application framework.  
 
-Every other subfolder is framework component. Each component contains two library parts: **app and native**.
+Every other subfolder is framework component. Each component contains two library parts: **app and native**.  
 
 - The "base" component provide timer API and inter-app communication support. It must be enabled if other components are selected.
 - Under the "app" folder of a component, the subfolder "wa_inc" holds all header files that should be included by the WASM applications
 
-
-
 ## Application framework basic model
 
 The app framework is built on top of two fundamental operations:
@@ -116,10 +115,6 @@ Generally you should follow following steps to create a new component:
   ```
 
 
-
 ## Sensor component working flow
-
-
-
 ![](../../doc/pics/sensor_callflow.PNG)
 

core/app-framework/README.md

@@ -1,10 +1,8 @@
-WASM application management
-=======
-
-## structure
-
+# Remote application management
 
+The WAMR application manager supports [remote application management](../core/app-mgr) from the host environment or the cloud through any physical communications such as TCP, UPD, UART, BLE, etc. Its modular design makes it able to support application management for different managed runtimes.
 
+The tool [host_tool](../test-tools/host-tool) communicates to the WAMR app manager for installing/uninstalling the WASM applications on companion chip from the host system. And the [IoT App Store Demo](../test-tools/IoT-APP-Store-Demo/) shows the conception of remotely managing the device applications from the cloud.
 
 
 <img src="../../doc/pics/wamr-arch.JPG" width="80%">