Fix spellcheck

Author: rkalis

.cspell.json

@@ -46,6 +46,7 @@
         "chipnet",
         "cleanstack",
         "cryptocurrency",
+        "collateralized",
         "datasig",
         "deserialisation",
         "docblock",
@@ -94,6 +95,7 @@
         "linebreak",
         "listunspent",
         "locktime",
+        "locktimes",
         "lokad",
         "lshift",
         "mecenas",
@@ -159,6 +161,7 @@
         "signable",
         "sigs",
         "spedn",
+        "stablecoins",
         "startup",
         "standardness",
         "tagline",
@@ -203,6 +206,7 @@
         "bchn",
         "cashcompiler",
         "cashninjas",
+        "chaingraph",
         "cherian",
         "CSCriptNum",
         "docu",
@@ -216,6 +220,7 @@
         "lichos",
         "mainnetjs",
         "maxdepth",
+        "moria",
         "networkprovider",
         "outputnulldata",
         "outputp",

packages/cashscript/test/e2e/network/FullStack.test.ts

@@ -35,7 +35,7 @@ if (!process.env.TESTS_USE_MOCKNET) {
 
     describe('send using FullStackNetworkProvider', () => {
       // Note: We instantiate the contract with bobPkh to avoid mempool conflicts with other tests
-      // Using p2sh20 address becuase it is funded on mainnet
+      // Using p2sh20 address because it is funded on mainnet
       const p2pkhInstance = new Contract(artifact, [bobPkh], { provider, addressType: 'p2sh20' });
       console.log(p2pkhInstance.address);
 
@@ -74,5 +74,5 @@ if (!process.env.TESTS_USE_MOCKNET) {
     });
   });
 } else {
-  test.skip('skip', () => {});
+  test.skip('skip', () => { });
 }

packages/cashscript/test/types/Contract.types.test.ts

@@ -34,7 +34,7 @@ interface ManualArtifactType extends Artifact {
 
 // describe('P2PKH contract | single constructor input | single function (2 args)')
 {
-  // describe('Contructor arguments')
+  // describe('Constructor arguments')
   {
     // it('should not give type errors when using correct constructor inputs')
     new Contract(p2pkhArtifact, [alicePkh]);

website/docs/guides/infrastructure.md

@@ -3,7 +3,7 @@ title: Contract Infrastructure
 ---
 
 When creating a smart contract application on Bitcoin Cash you'll need to investigate whether you need surrounding contract infrastructure.
-Below we'll discuss the 2 main types of contract infrastructure you might run into: the need to store contract details and the need for a transaction server. 
+Below we'll discuss the 2 main types of contract infrastructure you might run into: the need to store contract details and the need for a transaction server.
 
 ## Storing Contract Details
 
@@ -13,7 +13,7 @@ Because of the `pay-to-scripthash` (`P2SH`) standard for smart contracts on BCH,
 It is the responsibility of smart contract services/apps to keep track of the contract details making up the `P2SH` contract, as user-wallets are currently not smart enough to do this automatically.
 :::
 
-When users are allowed to provide their own `constructor` arguments when creating a BCH smart contract, each contract creation will have a unique smart contract address. Only the constructor arguments in the contract bytecode are variable, the rest of the bytecode for a contract is static. This static part is derived from the CashScript source file, so storing the contract source file or artifact both has the same effect. 
+When users are allowed to provide their own `constructor` arguments when creating a BCH smart contract, each contract creation will have a unique smart contract address. Only the constructor arguments in the contract bytecode are variable, the rest of the bytecode for a contract is static. This static part is derived from the CashScript source file, so storing the contract source file or artifact both has the same effect.
 
 :::note
 To construct the full contract script you need both the `constructor` arguments and static contract bytecode (either the contract source file or the `Artifact`) to be available.
@@ -40,10 +40,10 @@ There are 2 main types of events which might need a transaction server to trigge
 
 ### Time-related events
 
-Time-related events are when your smart contract uses absolute or relative locktimes, which require a waiting period before certain transactions can happen. However, if you want those transactions to 'automatically' happen when this locktime is reached, then you will need to create a transaction server to monitor the blockheight on an ongoing basis.
+Time-related events are when your smart contract uses absolute or relative locktimes, which require a waiting period before certain transactions can happen. However, if you want those transactions to 'automatically' happen when this locktime is reached, then you will need to create a transaction server to monitor the block height on an ongoing basis.
 
 :::tip
-Both the `Electrum` and `Chaingraph` indexers allow you to create websocket subscriptions to listen for blockheight updates.
+Both the `Electrum` and `Chaingraph` indexers allow you to create websocket subscriptions to listen for block height updates.
 :::
 
 ### Oracle-related events

website/docs/guides/syntax-highlighting.md

@@ -43,7 +43,7 @@ GitHub has highlighting for Solidity built in. To associate `.cash` files with S
 *.cash linguist-language=Solidity # GitHub
 ```
 
-Unfortunately Gitlab does not have properly working Soldidity highlighting through the `gitattributes` for now...
+Unfortunately Gitlab does not have properly working Solidity highlighting through the `gitattributes` for now...
 
 ## Others
 If your editor is not mentioned above, the steps are likely very similar. Try to find a Solidity syntax highlighting plugin for your editor of choice and find a method to associate `.cash` files with this Solidity highlighting.

website/docs/showcase.md

@@ -26,7 +26,7 @@ Tapswap is the first non-custodial marketplace to trade CashTokens, both fungibl
     <a href="https://moria.money/" target="_blank"><img src="/img/moria.png" /></a>
 </div>
 
-Moria is a decentralized stablecoin and borrowing protocol on Bitcoin Cash using CashTokens. The Moria protocol works with collateralized-debt-positions (CDPs) where stablecoins are issued by creating over-collateralized loans. The Moria protocol uses multiple smart contracts, all written in CashScript.
+Moria is a decentralized stablecoin and borrowing protocol on Bitcoin Cash using CashTokens. The Moria protocol works with collateralized debt positions (CDPs) where stablecoins are issued by creating over-collateralized loans. The Moria protocol uses multiple smart contracts, all written in CashScript.
 
 ## Bitcats Heroes