minor changes (bytecodealliance#43)

content/en/blog/move_the_embedded_world_to_webassembly_practice_in_chre/index.md

@@ -1,5 +1,5 @@
 ---
-title: "Move the embedded world to WebAssembly : practice in CHRE"
+title: "Moving the embedded world to WebAssembly : Practice in CHRE"
 description: ""
 excerpt: ""
 date: 2023-05-16T15:18:38+08:00
@@ -14,17 +14,13 @@ pinned: false
 homepage: false
 ---
 
-This blog will introduce our practice in integrating WASM with CHRE(Context Hub Runtime Environment), which solves some challenges that may also be encountered in other projects.
+I have recently finished my project of moving CHRE NanoApps from native to WebAssembly without changing the application source code. The source code is available in my GitHub repo [cher-wasm](https://github.com/FromLiQg/chre-wasm/tree/wasm).
 
-These challenges mainly focus on data sharing and callback functions.
-
-We will introduce the architecture used in this projects and solutions to specific challenges.
+The major challenges are from Wasm-Host data sharing and function callbacks. This blog will introduce the practice in integrating WASM with CHRE(Context Hub Runtime Environment), and how to some challenges. It should be useful for moving other existing project to Wasm based user applications.
 
 ### 1. The overview of CHRE-WASM
 
-`CHRE` is the software environment where small native applications, called `nanoapp`, execute on a low-power processor and interact with the underlying system through the common `CHRE API`.
-And CHRE is a event-driven model system, maintaining an event queue and distribute events to nanoapps.
-We compile nanoapps into WASM and embed WAMR into CHRE to enable CHRE to run these new WASM nanoapps. 
+`CHRE` is the Android sensor framework where small native applications, called `nanoapp`, execute on a low-power processor and interact with the underlying system through the common `CHRE API`. And CHRE is a event-driven model system, maintaining an event queue and distribute events to nanoapps. We compile nanoapps into WASM and embed WAMR into CHRE to enable CHRE to run these new WASM nanoapps. 
 
 The CHRE framework interacts with a given nanoapp through one of the three nanoapp entry points (`nanoappStart()`, `nanoappHandleEvent()`, and `nanoappEnd()`) or through a callback provided in a prior CHRE API call, and nanoapps interact with the CHRE framework and the underlying system through the CHRE API. 
 

content/en/blog/the_wasm-host_data_transfer_challenges/index.md

@@ -16,7 +16,7 @@ homepage: false
 
 ### Background
 
-I have tried to integrate WASM with CHRE (Context Hub Runtime Environment) at my GitHub repo [cher-wasm](https://github.com/FromLiQg/chre-wasm/tree/wasm), and before that I learned the LVGL (Light and Versatile Graphics Library) samples provided by WAMR. 
+I have tried to integrate WASM with CHRE (Context Hub Runtime Environment) at my GitHub repo [(cher-wasm)](https://github.com/FromLiQg/chre-wasm/tree/wasm), and before that I learned the LVGL (Light and Versatile Graphics Library) samples provided by WAMR. 
 
 CHRE is the Android sensor hub framework where small native applications, called nanoapps, which are executed on a low-power processor and interact with the underlying system through the common CHRE API. My goal was compiling the nanoapps source code into WASM and run them on the WAMR embedded into CHRE.  
 

content/en/blog/wamr_memory_model/index.md

@@ -5,7 +5,7 @@ excerpt: ""
 date: 2023-03-21T9:20:07+08:00
 lastmod: 2023-03-21T9:20:07+08:00
 draft: false
-weight: 100
+weight: 20
 images: []
 categories: ['introduction']
 tags: []