Skip to content

Commit c2cf77b

Browse files
authored
Update features.md
Signed-off-by: alabulei1 <[email protected]>
1 parent bb20170 commit c2cf77b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/start/wasmedge/features.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -41,15 +41,15 @@ Through the [WasmEdge-Quickjs](https://github.com/second-state/wasmedge-quickjs)
4141

4242
WasmEdge could be seamlessly integrated with the existing cloud-native infra.
4343

44-
To integrate WasmEdge with your existing cloud-native infrastructure, there are several options available for managing WASM applications as "containers" under Kubernetes. These options enables you to run Linux containers and WASM containers side by side within a Kubernetes cluster.
44+
To integrate WasmEdge with your existing cloud-native infrastructure, there are several options available for managing WASM applications as "containers" under Kubernetes. These options enable you to run Linux containers and WASM containers side by side within a Kubernetes cluster.
4545

4646
**Option #1:** is to [use an OCI runtime crun](../../develop/deploy/oci-runtime/crun.md) (the C version of runc — mainly supported by Red Hat). crun decides whether an OCI image is WASM or Linux based on image annotations. If the image is annotated as wasm32, crun will bypass the Linux container setup and just use WasmEdge to run the image. By using crun, you can get the entire Kubernetes stack - including CRI-O, containerd, Podman, kind, micro k8s, and k8s - to work with WASM images.
4747

4848
Option #2 is to [use a containerd-shim to start WASM "containers" via runwasi](../../develop/deploy/cri-runtime/containerd.md). Basically, containerd could look at the image's target platform. It uses runwasi if the image is wasm32 and runc if it is x86 / arm. This is the approach used by Docker + Wasm.
4949

5050
## Cross Platform
5151

52-
WASM is Portable. The compiled wasm file could run on different hardware and platforms without any changes.
52+
WASM is Portable. The compiled WASM file could run on different hardware and platforms without any changes.
5353

5454
WasmEdge supports a wide range of operating systems and hardware platforms. It allows WebAssembly applications to be truly portable across platforms. It runs on Linux-like systems and microkernels such as the `seL4` real-time system.
5555

@@ -69,12 +69,12 @@ WasmEdge now supports:
6969

7070
It is easy to build customized WasmEdge runtime with native host functions in C, Go, and Rust.
7171

72-
Or you could build your own plug-ins for WasmEdge in,
72+
Or you could build your own plug-ins for WasmEdge in
7373

7474
- [Rust](../../contribute/plugin/develop_plugin_rustsdk)
7575
- [C](../../contribute/plugin/develop_plugin_c)
7676
- [C++](../../contribute/plugin/develop_plugin_cpp)
7777

7878
## Easy to Embed into a Host Application
7979

80-
Embedded runtime is the classical use case for WasmEdge. You could embed WasmEdge functions in C, Go, Rust, Node.js, Java (WIP), and Python (WIP) host applications.
80+
[Embedded runtime](https://wasmedge.org/docs/embed/overview) is the classical use case for WasmEdge. You could embed WasmEdge functions in C, Go, Rust, Node.js, Java (WIP), and Python (WIP) host applications.

0 commit comments

Comments
 (0)