From 95b555cd4061f6a1318a569da3fd3402983f545a Mon Sep 17 00:00:00 2001 From: wgyt Date: Fri, 17 Jan 2025 05:33:54 +0800 Subject: [PATCH] Docs: fix typos (#12745) --- runtime/near-vm/test-api/README.md | 2 +- runtime/near-vm/tests/wast/wasmer/README.md | 6 +++--- tools/cold-store/README.md | 2 +- tools/speedy_sync/README.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/runtime/near-vm/test-api/README.md b/runtime/near-vm/test-api/README.md index 3948f5ce27b..4c99d55c534 100644 --- a/runtime/near-vm/test-api/README.md +++ b/runtime/near-vm/test-api/README.md @@ -57,7 +57,7 @@ Wasmer is not only fast, but also designed to be *highly customizable*: is possible to serialize it in a file for example, and later execute it with Wasmer with headless mode turned on. Headless Wasmer has no compiler, which makes it more portable and faster to load. It's - ideal for constrainted environments. + ideal for constrained environments. * **Cross-compilation** — Most compilers support cross-compilation. It means it possible to pre-compile a WebAssembly module targetting a diff --git a/runtime/near-vm/tests/wast/wasmer/README.md b/runtime/near-vm/tests/wast/wasmer/README.md index 976146c247b..e2aea8c21ac 100644 --- a/runtime/near-vm/tests/wast/wasmer/README.md +++ b/runtime/near-vm/tests/wast/wasmer/README.md @@ -7,11 +7,11 @@ by the standard WebAssembly spectests. ## NaN canonicalization: `nan-canonicalization.wast` This is an extra set of tests that assure that operations with NaNs -are deterministic regarless of the environment/chipset where it executes in. +are deterministic regardless of the environment/chipset where it executes in. -## Call Indirect Spilled Stack: `call-indirect-spilledd-stack.wast` +## Call Indirect Spilled Stack: `call-indirect-spilled-stack.wast` -We had an issue occuring that was making singlepass not working properly +We had an issue occurring that was making singlepass not working properly on the WebAssembly benchmark: https://00f.net/2019/10/22/updated-webassembly-benchmark/. This is a test case to ensure it doesn't reproduce again in the future. diff --git a/tools/cold-store/README.md b/tools/cold-store/README.md index 48fa251ef1b..133b77af282 100644 --- a/tools/cold-store/README.md +++ b/tools/cold-store/README.md @@ -3,7 +3,7 @@ ## Workflow Start by trying something on localnet, -then move on to test you code on a dedicated machine +then move on to test your code on a dedicated machine with real archival data. Ideally, on archival machine we only need to do every step before experimenting once. But accidents happen, and we should be mindful of the time it takes us diff --git a/tools/speedy_sync/README.md b/tools/speedy_sync/README.md index a33efc14235..d9997e1a2a6 100644 --- a/tools/speedy_sync/README.md +++ b/tools/speedy_sync/README.md @@ -1,6 +1,6 @@ # Speedy sync (a.k.a PoorMan's EpochSync) -The goal of the speedy sync is to allow people to cathup quickly with mainnet, before we have fully implemented the EpochSync feature. +The goal of the speedy sync is to allow people to catchup quickly with mainnet, before we have fully implemented the EpochSync feature. Currently, in order to catchup with mainnet there are two possible options: * download a DB backup that Pagoda provides (around 200GB)