Fix typos (#3438)

* fix typo * fix typo * fix typos * fix typos * fix typo * fix typos * fix typos * fix typos
trustwallet · Sep 22, 2023 · a752fb6 · a752fb6
1 parent c86ab9d
commit a752fb6
Show file tree

Hide file tree

Showing 8 changed files with 17 additions and 17 deletions.
diff --git a/docs/registry-fields.md b/docs/registry-fields.md
@@ -31,7 +31,7 @@ Ex.: `10000118` for Osmosis, `118` for Cosmos; `20000714` for BNB Smart Chain.
 See also: `slip44` and `chainId`.
 
 **`slip44`**
-Optionally, SLIP-44 (BIP-44) coin ID can be specified here, in case it differs from `coinId`.  Most of the case the two are the same, so this can be omitted.
+Optionally, SLIP-44 (BIP-44) coin ID can be specified here, in case it differs from `coinId`.  In most cases the two are the same, so this can be omitted.
 Ex.: `60` for Optimism (coinID is `10000070`).
 
 **`symbol`**
@@ -67,7 +67,7 @@ Note that the second number, the BIP-44 ID, usually matches the coinId.
 Some blockchains may support additional alternative derivations.  These have:
 
 - a name
-- a alternative derivation path (optional)
+- an alternative derivation path (optional)
 
 Derivation may differ in the derivation path, or by address generation method (based on the derivation name).
 The first derivation is considered the default.

diff --git a/samples/cpp/README.md b/samples/cpp/README.md
@@ -23,7 +23,7 @@ and [Build Instructions](https://developer.trustwallet.com/wallet-core/building)
 
 You need to download and build WalletCore yourself
 (there is no official binary distribution).
-The dependencies TrezorCrypto and protobuf are also needed, these are also come with WalletCore.
+The dependencies TrezorCrypto and protobuf are also needed, these also come with WalletCore.
 You need to [build](https://developer.trustwallet.com/wallet-core/building) the library.
 
 
@@ -49,7 +49,7 @@ Run it:
 ./sample
 ```
 
-The relavant sample code is in the file `cpp/sample.cpp`.
+The relevant sample code is in the file `cpp/sample.cpp`.
 
 # What it Does
 

diff --git a/samples/go/README.md b/samples/go/README.md
@@ -50,7 +50,7 @@ cd wallet-core
 
 ### 🐳 Docker
 1. Run `docker run -it trustwallet/wallet-core`
-The librabry is already built in this image  (Build instructions [here](building.md))  Note: may not be the most recent version.
+The library is already built in this image  (Build instructions [here](building.md))  Note: may not be the most recent version.
 
 2. Install go: `apt-get update && apt-get install golang` 
 (or download from here [go1.16.12](https://go.dev/dl/go1.16.12.linux-amd64.tar.gz), configure `GOROOT` and append `GOROOT/bin` to `PATH`).
@@ -62,7 +62,7 @@ The librabry is already built in this image  (Build instructions [here](building
 cd wallet-core/samples/go
 ```
 
-2. Compile it by `go build -o main`.  Relavant source file is `main.go`.
+2. Compile it by `go build -o main`.  Relevant source file is `main.go`.
 
 3. Run `./main` and you will see the output below: 
 
@@ -73,4 +73,4 @@ cd wallet-core/samples/go
 ```
 4. *(optional)* You might want to copy and run `main` outside of the docker container, make sure you have `libc++1` and `libc++abi1` installed in your host Ubuntu.
 
-5. *(optional)* If you want to make transaction on other networks you need to compile `src/proto` proto files and to do that, just run the `./compile.sh` . you can also modify it based on your project.
+5. *(optional)* If you want to make transaction on other networks you need to compile `src/proto` proto files and to do that, just run the `./compile.sh` . you can also modify it based on your project.
diff --git a/samples/go/main.go b/samples/go/main.go
@@ -45,7 +45,7 @@ func main() {
 	fmt.Println("Ethereum signed tx:")
 	fmt.Println("\t", ethTxn)
 
-	// Bitcion transaction
+	// Bitcoin transaction
 	btcTxn := createBtcTransaction(bw)
 	fmt.Println("\nBitcoin signed tx:")
 	fmt.Println("\t", btcTxn)

diff --git a/samples/osx/README.md b/samples/osx/README.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-This folder contains a simple but complete **iOS/macOS** sample application, for demostrating usage of the
+This folder contains a simple but complete **iOS/macOS** sample application, for demonstrating usage of the
 [Wallet Core](https://github.com/trustwallet/wallet-core) library (part of [Trust Wallet](https://trustwallet.com)).
 
 ## DISCLAIMER

diff --git a/samples/rust/README.md b/samples/rust/README.md
@@ -20,11 +20,11 @@ cargo run
 
 - The app links with the wallet-core library (C/C++).
 - The `walletcore_iface.rs` file contains the interface definitions in Rust.
-- Links with `TrustWalletCore`, `TrezorCrypto`, `protobuf`, and the platform libc (`c++` or `stdc++`). Build/link paramaters are in `build.rs`.
+- Links with `TrustWalletCore`, `TrezorCrypto`, `protobuf`, and the platform libc (`c++` or `stdc++`). Build/link parameters are in `build.rs`.
 - Rust proto files are created during the build process, from the `.proto` files in wallet-core,
 into subfolder `src/wc_proto`
 (see `build.rs`).
-- Notable dependecies:
+- Notable dependencies:
   -- `protobuf`
   -- `lib` for C linking
   -- `hex`

diff --git a/trezor-crypto/crypto/README.md b/trezor-crypto/crypto/README.md
@@ -27,9 +27,9 @@ These include:
 - unit tests (using Check - check.sf.net; in test_check.c)
 - tests against OpenSSL (in test_openssl.c)
 - integrated Wycheproof tests
-- public key convertion between Curve25519 to Ed25519 and vice versa
+- public key conversion between Curve25519 to Ed25519 and vice versa
 
-Distibuted under MIT License.
+Distributed under MIT License.
 
 ## Some parts of the library come from external sources:
 

diff --git a/trezor-crypto/crypto/ed25519-donna/README.md b/trezor-crypto/crypto/ed25519-donna/README.md
@@ -1,5 +1,5 @@
 [ed25519](https://ed25519.cr.yp.to) is an
-[Elliptic Curve Digital Signature Algortithm](https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm),
+[Elliptic Curve Digital Signature Algorithm](https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm),
 developed by [Dan Bernstein](https://cr.yp.to/djb.html),
 [Niels Duif](https://www.nielsduif.nl),
 [Tanja Lange](https://hyperelliptic.org/tanja),
@@ -56,7 +56,7 @@ No configuration is needed **if you are compiling against OpenSSL**.
 
 ##### Hash Options
 
-If you are not compiling aginst OpenSSL, you will need a hash function.
+If you are not compiling against OpenSSL, you will need a hash function.
 
 To use a simple/**slow** implementation of SHA-512, use `-DED25519_REFHASH` when compiling `ed25519.c`.
 This should never be used except to verify the code works when OpenSSL is not available.
@@ -73,7 +73,7 @@ custom hash implementation in ed25519-hash-custom.h. The hash must have a 512bit
 
 ##### Random Options
 
-If you are not compiling aginst OpenSSL, you will need a random function for batch verification.
+If you are not compiling against OpenSSL, you will need a random function for batch verification.
 
 To use a custom random function, use `-DED25519_CUSTOMRANDOM` when compiling `ed25519.c` and put your
 custom hash implementation in ed25519-randombytes-custom.h. The random function must implement:
@@ -170,7 +170,7 @@ signing due to both using the same code for the scalar multiply.
 
 #### Testing
 
-Fuzzing against reference implemenations is now available. See [fuzz/README](fuzz/README.md).
+Fuzzing against reference implementations is now available. See [fuzz/README](fuzz/README.md).
 
 Building `ed25519.c` with `-DED25519_TEST` and linking with `test.c` will run basic sanity tests
 and benchmark each function. `test-batch.c` has been incorporated in to `test.c`.