Skip to content

fix typos #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xwang98 merged 1 commit into from
May 10, 2019
Merged

fix typos #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,11 @@ Features

Architecture
=========================
The application manager component handles the packets that the platform recieved from external through any communication buses such as socket, serial port, PSI. A packet type can be either request, response or event. It will service the request with URI "/applet" and call the runtime glue layer interfaces for installing/uninstalling the application. For other URIs, it will filter the resource registeration table and router the request to internal queue of responsible application.
The application manager component handles the packets that the platform received from external through any communication buses such as socket, serial port, PSI. A packet type can be either request, response or event. It will service the request with URI "/applet" and call the runtime glue layer interfaces for installing/uninstalling the application. For other URIs, it will filter the resource registration table and router the request to internal queue of responsible application.

The WebAssembly runtime is the execution environment for WASM applications.

The messaging layer can suppor the API for WASM applications communicate to each other and also the host environment.
The messaging layer can support the API for WASM applications communicate to each other and also the host environment.

When Ahead of Time compilation is enabled, the WASM application can be either bytecode or compiled native binary.

Expand Down Expand Up @@ -62,7 +62,7 @@ make
```
Zephyr
-------------------------
You need download Zephyr source code first and embeded WAMR into it.
You need download Zephyr source code first and embedded WAMR into it.
``` Bash
git clone https://github.com/zephyrproject-rtos/zephyr.git
cd zephyr/samples/
Expand Down Expand Up @@ -301,7 +301,7 @@ The pre-defined MACRO `EXPORT_WASM_API` should be used to declare a function exp
#define EXPORT_WASM_API(symbol) {#symbol, symbol}
```

Below code example shows how to extend the library to support `customeized()`:
Below code example shows how to extend the library to support `customized()`:
``` C
//lib-export-impl.c
void customized()
Expand Down