mii/wasmer
1
0
Fork 0
mirror of https://github.com/mii443/wasmer.git synced 2025-12-03 03:08:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix spelling WASM -> Wasm

Browse Source
This commit is contained in:
Simon Warta
2021-01-03 21:59:11 +01:00
parent db41a5dfe8
commit 82e9c0c18f
9 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/migration_to_1.0.0.md
View File

@@ -20,7 +20,7 @@ to make migrating to the new API as simple as possible.
## Rationale for changes in 1.0.0
Wasmer 0.x was great but as the WASM community and standards evolve we felt the need to make Wasmer also follow these
Wasmer 0.x was great but as the Wasm community and standards evolve we felt the need to make Wasmer also follow these
changes.
Wasmer 1.x is what we think a necessary rewrite of a big part of the project to make it more future-proof.
@@ -70,9 +70,9 @@ The figure above shows the core Wasmer crates and their dependencies with transi
Wasmer 1.0.0 has two core architectural abstractions: engines and compilers.
An engine is a system that processes WASM with a compiler and prepares it to be executed.
An engine is a system that processes Wasm with a compiler and prepares it to be executed.
A compiler is a system that translates WASM into a format that can be understood
A compiler is a system that translates Wasm into a format that can be understood
more directly by a real computer: machine code.
For example, in the [examples] you'll see that we are using the JIT engine and the Cranelift compiler. The JIT engine