chore: fix spelling errors caught by CI

lukso-network · Nov 25, 2024 · 9a09a49 · 9a09a49
1 parent 0f73ade
commit 9a09a49
Show file tree

Hide file tree

Showing 66 changed files with 120 additions and 100 deletions.
diff --git a/.github/workflows/spellcheck.yml b/.github/workflows/spellcheck.yml
@@ -23,6 +23,7 @@ jobs:
           check_filenames: true
           check_hidden: true
           skip: yarn.lock,./node_modules/**/*,./node_modules/.*,./yarn/**/*,./.yarn/**/*
+          ignore_words_list: datas
 
       - name: Output Spellcheck Results 📝
         uses: actions/upload-artifact@v3

diff --git a/docs/contracts/_interface_ids_table.mdx b/docs/contracts/_interface_ids_table.mdx
@@ -7,7 +7,7 @@
 | **LSP0ERC725Account**             | `0x24871b3d` | Interface of the [LSP-0-ERC725Account] standard, an account based smart contract that represents an identity on-chain.                                   |
 | **LSP1UniversalReceiver**         | `0x6bb56a14` | Interface of the LSP1 - Universal Receiver standard, an entry function for a contract to receive arbitrary information.                                  |
 | **LSP1UniversalReceiverDelegate** | `0xa245bbda` | Interface of the LSP1 - Universal Receiver Delegate standard.                                                                                            |
-| **LSP6KeyManager**                | `0x23f34c62` | Interface of the LSP6 - Key Manager standard, a contract acting as a controller of an ERC725 Account using predfined permissions.                        |
+| **LSP6KeyManager**                | `0x23f34c62` | Interface of the LSP6 - Key Manager standard, a contract acting as a controller of an ERC725 Account using predefined permissions.                       |
 | **LSP7DigitalAsset**              | `0xb3c4928f` | Interface of the LSP7 - Digital Asset standard, a fungible digital asset.                                                                                |
 | **LSP8IdentifiableDigitalAsset**  | `0x3a271706` | Interface of the LSP8 - Identifiable Digital Asset standard, a non-fungible digital asset.                                                               |
 | **LSP9Vault**                     | `0x28af17e6` | Interface of LSP9 - Vault standard, a blockchain vault that can hold assets and interact with other smart contracts.                                     |

diff --git a/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md b/docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md
@@ -847,7 +847,7 @@ function universalReceiver(
 ) external payable returns (bytes returnedValues);
 ```
 
-_Notifying the contract by calling its `universalReceiver` function with the following informations: typeId: `typeId`; data: `data`._
+_Notifying the contract by calling its `universalReceiver` function with the following information: typeId: `typeId`; data: `data`._
 
 Achieves the goal of [LSP-1-UniversalReceiver] by allowing the account to be notified about incoming/outgoing transactions and enabling reactions to these actions. The reaction is achieved by having two external contracts ([LSP1UniversalReceiverDelegate]) that react on the whole transaction and on the specific typeId, respectively. The function performs the following steps:
 

diff --git a/docs/contracts/contracts/LSP11BasicSocialRecovery/LSP11BasicSocialRecovery.md b/docs/contracts/contracts/LSP11BasicSocialRecovery/LSP11BasicSocialRecovery.md
@@ -559,7 +559,7 @@ function _cleanStorage(
 ) internal nonpayable;
 ```
 
-Remove the guardians choice after a successfull recovery process
+Remove the guardians choice after a successful recovery process
 To avoid keeping unnecessary state
 
 <br/>

diff --git a/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md b/docs/contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateUP.md
@@ -96,8 +96,8 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface).
 
 :::info
 
-- If some issues occured with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
-- If an error occured when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
+- If some issues occurred with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
+- If an error occurred when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
 
 :::
 

diff --git a/...rsalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md b/...rsalReceiver/LSP1UniversalReceiverDelegateUP/LSP1UniversalReceiverDelegateUP.md
@@ -96,8 +96,8 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface).
 
 :::info
 
-- If some issues occured with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
-- If an error occured when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
+- If some issues occurred with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
+- If an error occurred when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
 
 :::
 

diff --git a/...contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateVault.md b/...contracts/contracts/LSP1UniversalReceiver/LSP1UniversalReceiverDelegateVault.md
@@ -94,8 +94,8 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface).
 
 :::info
 
-- If some issues occured with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
-- If an error occured when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
+- If some issues occurred with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
+- If an error occurred when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
 
 :::
 

diff --git a/...ceiver/LSP1UniversalReceiverDelegateVault/LSP1UniversalReceiverDelegateVault.md b/...ceiver/LSP1UniversalReceiverDelegateVault/LSP1UniversalReceiverDelegateVault.md
@@ -94,8 +94,8 @@ See [`IERC165-supportsInterface`](#ierc165-supportsinterface).
 
 :::info
 
-- If some issues occured with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
-- If an error occured when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
+- If some issues occurred with generating the `dataKeys` or `dataValues` the `returnedMessage` will be an error message, otherwise it will be empty.
+- If an error occurred when trying to use `setDataBatch(dataKeys,dataValues)`, it will return the raw error data back to the caller.
 
 :::
 

diff --git a/docs/contracts/contracts/LSP25ExecuteRelayCall/LSP25MultiChannelNonce.md b/docs/contracts/contracts/LSP25ExecuteRelayCall/LSP25MultiChannelNonce.md
@@ -16,7 +16,7 @@
 
 > Implementation of the multi channel nonce and the signature verification defined in the LSP25 standard.
 
-This contract can be used as a backbone for other smart contracts to implement meta-transactions via the LSP25 Execute Relay Call interface. It contains a storage of nonces for signer addresses across various channel IDs, enabling these signers to submit signed transactions that order-independant. (transactions that do not need to be submitted one after the other in a specific order). Finally, it contains internal functions to verify signatures for specific calldata according the signature format specified in the LSP25 standard.
+This contract can be used as a backbone for other smart contracts to implement meta-transactions via the LSP25 Execute Relay Call interface. It contains a storage of nonces for signer addresses across various channel IDs, enabling these signers to submit signed transactions that order-independent. (transactions that do not need to be submitted one after the other in a specific order). Finally, it contains internal functions to verify signatures for specific calldata according the signature format specified in the LSP25 standard.
 
 ## Internal Methods
 

diff --git a/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md b/docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md
@@ -286,7 +286,7 @@ Same as [`executeRelayCall`](#executerelaycall) but execute a batch of signed ca
 A signer can choose its channel number arbitrarily. The recommended practice is to:
 
 - use `channelId == 0` for transactions for which the ordering of execution matters.abi _Example: you have two transactions A and B, and transaction A must be executed first and complete successfully before transaction B should be executed)._
-- use any other `channelId` number for transactions that you want to be order independant (out-of-order execution, execution _"in parallel"_). \_Example: you have two transactions A and B. You want transaction B to be executed a) without having to wait for transaction A to complete, or b) regardless if transaction A completed successfully or not.
+- use any other `channelId` number for transactions that you want to be order independent (out-of-order execution, execution _"in parallel"_). \_Example: you have two transactions A and B. You want transaction B to be executed a) without having to wait for transaction A to complete, or b) regardless if transaction A completed successfully or not.
 
 :::
 

diff --git a/...ontracts/contracts/LSP8IdentifiableDigitalAsset/LSP8IdentifiableDigitalAsset.md b/...ontracts/contracts/LSP8IdentifiableDigitalAsset/LSP8IdentifiableDigitalAsset.md
@@ -769,7 +769,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Burnable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Burnable.md
@@ -795,7 +795,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/...contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md b/...contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md
@@ -794,7 +794,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/...racts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CompatibleERC721.md b/...racts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CompatibleERC721.md
@@ -1112,7 +1112,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Enumerable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Enumerable.md
@@ -800,7 +800,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/.../contracts/LSP8IdentifiableDigitalAsset/presets/LSP8CompatibleERC721Mintable.md b/.../contracts/LSP8IdentifiableDigitalAsset/presets/LSP8CompatibleERC721Mintable.md
@@ -1156,7 +1156,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md
@@ -835,7 +835,7 @@ Transfer a given `tokenId` token from the `from` address to the `to` address. If
 | `from`    | `address` | The address that owns the given `tokenId`.                                                                                                                          |
 | `to`      | `address` | The address that will receive the `tokenId`.                                                                                                                        |
 | `tokenId` | `bytes32` | The token ID to transfer.                                                                                                                                           |
-| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any addres. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
+| `force`   |  `bool`   | When set to `true`, the `to` address CAN be any address. When set to `false`, the `to` address MUST be a contract that supports the LSP1 UniversalReceiver standard. |
 | `data`    |  `bytes`  | Any additional data the caller wants included in the emitted event, and sent in the hooks of the `from` and `to` addresses.                                         |
 
 <br/>

diff --git a/docs/contracts/contracts/LSP9Vault/LSP9Vault.md b/docs/contracts/contracts/LSP9Vault/LSP9Vault.md
@@ -764,7 +764,7 @@ function universalReceiver(
 ) external payable returns (bytes returnedValues);
 ```
 
-_Notifying the contract by calling its `universalReceiver` function with the following informations: typeId: `typeId`; data: `data`._
+_Notifying the contract by calling its `universalReceiver` function with the following information: typeId: `typeId`; data: `data`._
 
 Achieves the goal of [LSP-1-UniversalReceiver] by allowing the account to be notified about incoming/outgoing transactions and enabling reactions to these actions. The reaction is achieved by having two external contracts ([LSP1UniversalReceiverDelegate]) that react on the whole transaction and on the specific typeId, respectively. The function performs the following steps:
 

diff --git a/docs/contracts/contracts/UniversalProfile/UniversalProfile.md b/docs/contracts/contracts/UniversalProfile/UniversalProfile.md
@@ -776,7 +776,7 @@ function universalReceiver(
 ) external payable returns (bytes returnedValues);
 ```
 
-_Notifying the contract by calling its `universalReceiver` function with the following informations: typeId: `typeId`; data: `data`._
+_Notifying the contract by calling its `universalReceiver` function with the following information: typeId: `typeId`; data: `data`._
 
 Achieves the goal of [LSP-1-UniversalReceiver] by allowing the account to be notified about incoming/outgoing transactions and enabling reactions to these actions. The reaction is achieved by having two external contracts ([LSP1UniversalReceiverDelegate]) that react on the whole transaction and on the specific typeId, respectively. The function performs the following steps:
 

diff --git a/docs/contracts/deployed-contracts.md b/docs/contracts/deployed-contracts.md
@@ -13,7 +13,7 @@ Check our guide [**_🏭 Deploy Universal Profile + its Key Manager with LSP23 F
 
 :::
 
-Below is a list of contracts deployed on the LUKSO Mainnet for production usage. These contracts are deployed with `CREATE2` using the Nick Factory, so that they can be re-deployed at different addresses accross multiple chains.
+Below is a list of contracts deployed on the LUKSO Mainnet for production usage. These contracts are deployed with `CREATE2` using the Nick Factory, so that they can be re-deployed at different addresses across multiple chains.
 
 ## 🏭 Factory contracts
-Original file line number
+Diff line change
@@ Expand Up @@
     :::
-    Below is a list of contracts deployed on the LUKSO Mainnet for production usage. These contracts are deployed with `CREATE2` using the Nick Factory, so that they can be re-deployed at different addresses accross multiple chains.
+    Below is a list of contracts deployed on the LUKSO Mainnet for production usage. These contracts are deployed with `CREATE2` using the Nick Factory, so that they can be re-deployed at different addresses across multiple chains.
     ## 🏭 Factory contracts
@@ Expand Down @@