docs: fix typos with spell checker

aptos/README.md

@@ -124,8 +124,8 @@ run the deploy script again. However, a better way is to run one of the followin
 
 ``` sh
 scripts $ ./upgrade devnet Core # for upgrading the wormhole contract
-scripts $ ./upgrade devnet TokenBridge # for upgarding the token bridge contract
-scripts $ ./upgrade devnet NFTBridge # for upgarding the NFT bridge contract
+scripts $ ./upgrade devnet TokenBridge # for upgrading the token bridge contract
+scripts $ ./upgrade devnet NFTBridge # for upgrading the NFT bridge contract
 ```
 
 Behind the scenes, these scripts exercise the whole contract upgrade code path

near/test/p3.ts

@@ -322,7 +322,7 @@ async function testNearSDK() {
   console.log("wallet addr: " + algoWallet.addr);
   console.log("usdcAssetId: " + usdcAssetId);
 
-  console.log("transfering USDC from Algo To Near... getting the vaa");
+  console.log("transferring USDC from Algo To Near... getting the vaa");
   console.log("myAddress: " + myAddress);
 
   let testAddress = nearAPI.providers.getTransactionLastResult(
@@ -379,7 +379,7 @@ async function testNearSDK() {
     )
   );
 
-  console.log("transfering USDC from Algo To Near... getting the vaa");
+  console.log("transferring USDC from Algo To Near... getting the vaa");
   let transferAlgoToNearRandoP3;
   {
     const AmountToTransfer: number = 100;

near/test/sdk.ts

@@ -886,7 +886,7 @@ async function testNearSDK() {
   console.log("wallet addr: " + algoWallet.addr);
   console.log("usdcAssetId: " + usdcAssetId);
 
-  console.log("transfering USDC from Algo To Near... getting the vaa");
+  console.log("transferring USDC from Algo To Near... getting the vaa");
   console.log("myAddress: " + myAddress);
 
   let transferAlgoToNearUSDC;
@@ -921,7 +921,7 @@ async function testNearSDK() {
     ).vaaBytes;
   }
 
-  console.log("YYY transfering rando from Algo To Near... getting the vaa");
+  console.log("YYY transferring rando from Algo To Near... getting the vaa");
   let transferAlgoToNearRando;
   {
     const Fee: number = 0;
@@ -953,7 +953,7 @@ async function testNearSDK() {
     ).vaaBytes;
   }
 
-  console.log("transfering NEAR from Algo To Near... getting the vaa");
+  console.log("transferring NEAR from Algo To Near... getting the vaa");
   let transferAlgoToNearNEAR;
   {
     const AmountToTransfer: number = 100;
@@ -1119,7 +1119,7 @@ async function testNearSDK() {
     );
 
     console.log(
-      "YYY P3 transfering rando from Algo To Near... getting the vaa"
+      "YYY P3 transferring rando from Algo To Near... getting the vaa"
     );
     let transferAlgoToNearRandoP3;
     {

node/pkg/node/node.go

@@ -37,7 +37,7 @@ const (
 	observationRequestInboundBufferSize = 500
 
 	// observationRequestOutboundBufferSize configures the size of obsvReqSendC
-	// and thereby somewhat limits the amout of observation requests that can be sent in bursts to the network.
+	// and thereby somewhat limits the amount of observation requests that can be sent in bursts to the network.
 	observationRequestOutboundBufferSize = 100
 
 	// observationRequestPerChainBufferSize is the buffer size of the per-network reobservation channel

sdk/js/src/token_bridge/__tests__/sui-integration.ts

@@ -272,7 +272,7 @@ describe("Sui SDK tests", () => {
       console.log(JSON.stringify(updateWrappedTxRes.effects, null, 2));
     expect(updateWrappedTxRes.effects?.status.status).toBe("success");
 
-    // Check if update was propogated to coin metadata
+    // Check if update was propagated to coin metadata
     const newCoinMetadata = await suiProvider.getCoinMetadata({
       coinType: getWrappedCoinType(coinPackageId),
     });

sui/README.md

@@ -117,8 +117,8 @@ run the deploy script again.
 
 ``` sh
 scripts $ ./upgrade devnet Core # for upgrading the wormhole contract
-scripts $ ./upgrade devnet TokenBridge # for upgarding the token bridge contract
-scripts $ ./upgrade devnet NFTBridge # for upgarding the NFT bridge contract
+scripts $ ./upgrade devnet TokenBridge # for upgrading the token bridge contract
+scripts $ ./upgrade devnet NFTBridge # for upgrading the NFT bridge contract
 ```
 
 Behind the scenes, these scripts exercise the whole contract upgrade code path

whitepapers/0007_governor.md

@@ -44,7 +44,7 @@ If a Guardian decides to enable this feature:
 
 Governor divides token-based transactions into two categories: small transactions, and large transactions.
 
-- **Small Transactions:** Transactions smaller than the single-transaction threshold of the chain where the transfer is originating from are considered small transactions.  During any 24h sliding window, the Guardian will sign token bridge transfers in aggregate value up to the 24h threshold with no finality delay.  When small transactions exceed this limit, they will be delayed until sufficient headroom is present in the 24h sliding window. A transaction either fits or is delayed, they are not artifically split into multiple transactions. If a small transaction has been delayed for more than 24h, it will be released immediately and it will not count towards the 24h threshold.
+- **Small Transactions:** Transactions smaller than the single-transaction threshold of the chain where the transfer is originating from are considered small transactions.  During any 24h sliding window, the Guardian will sign token bridge transfers in aggregate value up to the 24h threshold with no finality delay.  When small transactions exceed this limit, they will be delayed until sufficient headroom is present in the 24h sliding window. A transaction either fits or is delayed, they are not artificially split into multiple transactions. If a small transaction has been delayed for more than 24h, it will be released immediately and it will not count towards the 24h threshold.
 - **Large Transactions:** Transactions larger than the single-transaction threshold of the chain where the transfer is originating from are considered large transactions.  All large transactions have an imposed 24h finality delay before Wormhole Guardians sign them. These transactions do not affect the 24h threshold counter.
 
 ### Asset pricing

whitepapers/0011_accountant.md

@@ -123,7 +123,7 @@ It will have the following accounts:
 
 Transferring a native token across the tokenbridge (locking) increases the balance on both the custody account and wrapped account on the destination chain.  Transferring a wrapped token back across the tokenbridge (burning) and subsequently unlocking its native asset decreases the balance on both the wrapped and custody accounts.  Any transfer causing the balance of an account to become negative is invalid and gets rejected.
 
-Each account is identified via a `(chain_id, token_chain, token_address)` tuple.  Custody accounts are those where `chain_id == token_chain`, while the rest are wrapped accounts. See the [governance](#governance) section below for futher clarification.
+Each account is identified via a `(chain_id, token_chain, token_address)` tuple.  Custody accounts are those where `chain_id == token_chain`, while the rest are wrapped accounts. See the [governance](#governance) section below for further clarification.
 
 #### Governance
 

wormchain/development.md

@@ -1,6 +1,6 @@
 # Develop
 
-## prerequsites
+## prerequisites
 
 - Go >= 1.16
 - nodejs >= 16

wormchain/x/ibc-hooks/README.md

@@ -55,7 +55,7 @@ msg := MsgExecuteContract{
 
 ### ICS20 packet structure
 
-So given the details above, we propogate the implied ICS20 packet data structure.
+So given the details above, we propagate the implied ICS20 packet data structure.
 ICS20 is JSON native, so we use JSON for the memo format.
 
 ```json 

wormchain/x/tokenfactory/README.md

@@ -81,7 +81,7 @@ message MsgBurn {
 
 **State Modifications:**
 
-- Saftey check the following
+- Safety check the following
   - Check that the denom minting is created via `tokenfactory` module
   - Check that the sender of the message is the admin of the denom
 - Burn designated amount of tokens for the denom via `bank` module