@@ -1546,8 +1546,8 @@ impl Config {
1546
1546
///
1547
1547
/// Memory in the `initial` range is accessible to the instance and can be
1548
1548
/// read/written by wasm code. Memory in the `guard` regions is never
1549
- /// accesible to wasm code and memory in `capacity` is initially
1550
- /// inaccessible but may become accesible through `memory.grow` instructions
1549
+ /// accessible to wasm code and memory in `capacity` is initially
1550
+ /// inaccessible but may become accessible through `memory.grow` instructions
1551
1551
/// for example.
1552
1552
///
1553
1553
/// This means that this setting is the size of the initial chunk of virtual
@@ -1559,7 +1559,7 @@ impl Config {
1559
1559
/// during the compilation process of a WebAssembly module. For example if a
1560
1560
/// 32-bit WebAssembly linear memory has a `memory_reservation` size of 4GiB
1561
1561
/// then bounds checks can be elided because `capacity` will be guaranteed
1562
- /// to be unmapped for all addressible bytes that wasm can access (modulo a
1562
+ /// to be unmapped for all addressable bytes that wasm can access (modulo a
1563
1563
/// few details).
1564
1564
///
1565
1565
/// If `memory_reservation` was something smaller like 256KiB then that
@@ -1571,7 +1571,7 @@ impl Config {
1571
1571
/// modules by default. Some situations which require explicit bounds checks
1572
1572
/// though are:
1573
1573
///
1574
- /// * When `memory_reservation` is smaller than the addressible size of the
1574
+ /// * When `memory_reservation` is smaller than the addressable size of the
1575
1575
/// linear memory. For example if 64-bit linear memories always need
1576
1576
/// bounds checks as they can address the entire virtual address spacce.
1577
1577
/// For 32-bit linear memories a `memory_reservation` minimum size of 4GiB
0 commit comments