', provider);
if (!isNickFactoryDeployed) {
diff --git a/docs/learn/overview.md b/docs/learn/overview.md
index 893d9df495..6c51971293 100644
--- a/docs/learn/overview.md
+++ b/docs/learn/overview.md
@@ -72,7 +72,7 @@ LUKSO is a Layer 1 EVM chain that uses an unmodified version of Ethereum. It can
-
+
diff --git a/docs/learn/universal-profile/advanced-guides/extend-profile-functionalities.md b/docs/learn/universal-profile/advanced-guides/extend-profile-functionalities.md
index 208f659b70..c797467744 100644
--- a/docs/learn/universal-profile/advanced-guides/extend-profile-functionalities.md
+++ b/docs/learn/universal-profile/advanced-guides/extend-profile-functionalities.md
@@ -204,7 +204,7 @@ const TipMeFactory = new ethers.ContractFactory(
const tipMeContract = await TipMeFactory.deploy();
await tipMeContract.deployTransaction.wait();
-const tipMeExtensionAddress = tipMeContract.addres;
+const tipMeExtensionAddress = tipMeContract.address;
console.log('Contract deployed at:', tipMeExtensionAddress);
```
@@ -371,7 +371,7 @@ main();
## Extending InterfaceIds
-Extending `interfaceIds` is crucial for Universal Profiles, as many protocols check for support of specific `interfaceIds` before executing calls to certain functions. Extending interfaceIds typically follows a similar approach to extending functions, with the main distinction being the existance of the `supportsInterface` function.
+Extending `interfaceIds` is crucial for Universal Profiles, as many protocols check for support of specific `interfaceIds` before executing calls to certain functions. Extending interfaceIds typically follows a similar approach to extending functions, with the main distinction being the existence of the `supportsInterface` function.
### Step 1: Create a Contract Supporting a Specific InterfaceId
@@ -443,7 +443,7 @@ const supportsInterfaceFactory = new ethers.ContractFactory(
const supportsInterfaceContract = await supportsInterfaceFactory.deploy();
await supportsInterfaceContract.deployTransaction.wait();
-const supportsInterfaceExtensionAddress = supportsInterfaceContract.addres;
+const supportsInterfaceExtensionAddress = supportsInterfaceContract.address;
console.log('Contract deployed at:', tipMeExtensionAddress);
```
@@ -535,7 +535,7 @@ async function main() {
const supportsInterfaceContract = await supportsInterfaceFactory.deploy();
await supportsInterfaceContract.deployTransaction.wait();
- const supportsInterfaceExtensionAddress = supportsInterfaceContract.addres;
+ const supportsInterfaceExtensionAddress = supportsInterfaceContract.address;
const supportsInterfaceInterface = new ethers.Interface(SupportsInterfaceABI);
const supportsInterfaceFunctionSelector =
diff --git a/docs/learn/universal-profile/connect-profile/connect-up.md b/docs/learn/universal-profile/connect-profile/connect-up.md
index 07b70854a0..3b0d437f46 100644
--- a/docs/learn/universal-profile/connect-profile/connect-up.md
+++ b/docs/learn/universal-profile/connect-profile/connect-up.md
@@ -131,7 +131,7 @@ Both libraries come with built-in UI elements and allow you to support multiple
| Customizable Connection Window
Remains connection on Page Refresh
Lists supported EIP-1193 Extensions
- Automatically detects EIP-6963 Extensions
+ Automatically detects EIP-6963 Extensions
Requires Wallet Connect Account ID |
diff --git a/docs/learn/universal-profile/interactions/transfer-lyx.md b/docs/learn/universal-profile/interactions/transfer-lyx.md
index 162d050c91..c0394d4f4e 100644
--- a/docs/learn/universal-profile/interactions/transfer-lyx.md
+++ b/docs/learn/universal-profile/interactions/transfer-lyx.md
@@ -12,11 +12,11 @@ import TabItem from '@theme/TabItem';
.default})
-
Transfering 0.5 LYXt between two Universal Profiles.
+
Transferring 0.5 LYXt between two Universal Profiles.
diff --git a/docs/learn/universal-profile/interactions/transfer-tokens-and-nfts.md b/docs/learn/universal-profile/interactions/transfer-tokens-and-nfts.md
index 02c44b9e70..c22900a73a 100644
--- a/docs/learn/universal-profile/interactions/transfer-tokens-and-nfts.md
+++ b/docs/learn/universal-profile/interactions/transfer-tokens-and-nfts.md
@@ -12,10 +12,10 @@ import TabItem from '@theme/TabItem';
.default})
-
Transfering 1,000 CHILL tokens between two Universal Profiles.
+
Transferring 1,000 CHILL tokens between two Universal Profiles.
@@ -66,7 +66,7 @@ Call the [LSP7 `transfer(address,address,uint256,bool,bytes)`](../../../contract
> Since most tokens have 18 [`decimals()`](../../../contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md#decimals), make sure to specify the `amount` with 18 decimals place. For instance, if you want to transfer 8 tokens the `amount` parameter will be: `8_000_000_000_000_000_000` ✅, not `8` ❌.
-> Otherwise, the transfer might have occured but you might not see the balance of the recipient updated, since you transferred only a tiny small amount (`8` for a token with 18 decimals is basically 1 / 1e18). To do so easily, use one of number utility function from _ethers.js_ or _web3.js_.
+> Otherwise, the transfer might have occurred but you might not see the balance of the recipient updated, since you transferred only a tiny small amount (`8` for a token with 18 decimals is basically 1 / 1e18). To do so easily, use one of number utility function from _ethers.js_ or _web3.js_.
diff --git a/docs/learn/universal-profile/key-manager/execute-relay-transactions.md b/docs/learn/universal-profile/key-manager/execute-relay-transactions.md
index b8024200ca..aad4d302cb 100644
--- a/docs/learn/universal-profile/key-manager/execute-relay-transactions.md
+++ b/docs/learn/universal-profile/key-manager/execute-relay-transactions.md
@@ -422,7 +422,7 @@ You can find more information about `executeRelayCall` within the [LSP6 Contract
:::
-To execute a previously signed transaction, the relayer will need all the following informations:
+To execute a previously signed transaction, the relayer will need all the following information:
- `signature` generated in **step 2.3**.
- `nonce` of the signing controller.
@@ -430,7 +430,7 @@ To execute a previously signed transaction, the relayer will need all the follow
- `abiPayload` as abi-encoded function call to execute on the 🆙.
- `keyManagerAddress` associated with the Universal Profile we want to execute on.
-The relayer can now call the [`executeRelayCall`](../../../contracts/contracts/LSP6KeyManager/LSP6KeyManager.md#executerelaycall) function on the Key Manager (`keyManagerAddress`) of the profile, passing all these informations as function arguments.
+The relayer can now call the [`executeRelayCall`](../../../contracts/contracts/LSP6KeyManager/LSP6KeyManager.md#executerelaycall) function on the Key Manager (`keyManagerAddress`) of the profile, passing all these information as function arguments.
diff --git a/docs/learn/universal-profile/key-manager/grant-permissions.md b/docs/learn/universal-profile/key-manager/grant-permissions.md
index 0a5a31fec7..76098203be 100644
--- a/docs/learn/universal-profile/key-manager/grant-permissions.md
+++ b/docs/learn/universal-profile/key-manager/grant-permissions.md
@@ -267,4 +267,4 @@ console.log(
Finally, to test the actual permissions, you can do this guide using a `beneficiaryAddress` that you have control over.
-You can try the [**Edit Universal Profile**](../metadata/edit-profile.md) guide, using this new 3rd party address that you have control over to test if it can successfull edit the profile details. This will give you guarantee that this `beneficiaryAddress` has the `SETDATA` permission working.
+You can try the [**Edit Universal Profile**](../metadata/edit-profile.md) guide, using this new 3rd party address that you have control over to test if it can successful edit the profile details. This will give you guarantee that this `beneficiaryAddress` has the `SETDATA` permission working.
diff --git a/docs/learn/universal-profile/metadata/read-profile-data.md b/docs/learn/universal-profile/metadata/read-profile-data.md
index 1005e7b8fc..0bda80e8e1 100644
--- a/docs/learn/universal-profile/metadata/read-profile-data.md
+++ b/docs/learn/universal-profile/metadata/read-profile-data.md
@@ -40,7 +40,7 @@ npm install @erc725/erc725.js
The parameters to provide to the erc725 instance are:
- [Schema](https://github.com/ERC725Alliance/erc725.js/tree/develop/schemas): specifies which data keys will be used to retrieve data from the Universal Profile.
-- Univeral Profile address: the address of the Universal Profile you want to retrieve data from.
+- Universal Profile address: the address of the Universal Profile you want to retrieve data from.
- Optional only for retrieving decoded data: RPC provider (web3, ethereum, ethers) or plain RPC url of [mainnet](../../../networks/mainnet/parameters.md) or [testnet](../../../networks/testnet/parameters.md) networks.
```js title="Creating an erc725 instance to read data from a Universal Profile"
@@ -59,7 +59,7 @@ const erc725js = new ERC725(
## Get all profile data
-Use the `await erc725js.getData()` functon from _erc725.js_ without passing any parameter.
+Use the `await erc725js.getData()` function from _erc725.js_ without passing any parameter.
```js title="Get all profile data"
import { ERC725 } from '@erc725/erc725.js';
diff --git a/docs/learn/universal-profile/universal-receiver/create-receiver-forwarder.md b/docs/learn/universal-profile/universal-receiver/create-receiver-forwarder.md
index 045af55904..8c6b9878ba 100644
--- a/docs/learn/universal-profile/universal-receiver/create-receiver-forwarder.md
+++ b/docs/learn/universal-profile/universal-receiver/create-receiver-forwarder.md
@@ -31,7 +31,7 @@ This guide is working with version above 0.14.0 of the [`@lukso/lsp-smart-contra
:::
-In order to follow this guide, you will need the followings:
+In order to follow this guide, you will need the following:
1. Download and install the [UP Browser extension](/install-up-browser-extension).
2. Fund the main EOA controller of your 🆙 (See **[Step 1](#step-1---enable-your-controller-to-add-a-universal-receiver) bullet point 3** to retrieve its address) using the [Testnet Faucet](https://faucet.testnet.lukso.network/).
@@ -210,7 +210,7 @@ contract LSP1Forwarder is ERC165, ILSP1Delegate {
return "Token not in allowlist";
}
- // extract data (we only need the amount that was transfered / minted)
+ // extract data (we only need the amount that was transferred / minted)
(, , , uint256 amount, ) = abi.decode(
data,
(address, address, address, uint256, bytes)
@@ -395,7 +395,7 @@ contract LSP1Forwarder is ERC165, ILSP1Delegate {
return "Token not in allowlist";
}
- // extract data (we only need the amount that was transfered / minted)
+ // extract data (we only need the amount that was transferred / minted)
(, , , uint256 amount, ) = abi.decode(
data,
(address, address, address, uint256, bytes)
@@ -691,7 +691,7 @@ console.log('✅ LSP1 Forwarder contract authorized on My USDC Token for UP 🫡
Now that all the pieces are connected, we can try it out!
-The expected behaviour is that **everytime the UP on which the custom LSP1 Forwarder contract has been set receives an allowed token (either through `transfer` or `mint`), it will automatically send a percentage to the specified recipient.**
+The expected behaviour is that **every time the UP on which the custom LSP1 Forwarder contract has been set receives an allowed token (either through `transfer` or `mint`), it will automatically send a percentage to the specified recipient.**
Here are the test data:
diff --git a/docs/learn/vault/edit-vault-data.md b/docs/learn/vault/edit-vault-data.md
index 6faf91226d..3b206ab89b 100644
--- a/docs/learn/vault/edit-vault-data.md
+++ b/docs/learn/vault/edit-vault-data.md
@@ -363,7 +363,7 @@ const updateVaultURD = async (vaultURDAddress) => {
});
};
-// update the curent Vault's URD
+// update the current Vault's URD
await updateVaultURD(vaultURDAddress);
```
@@ -395,7 +395,7 @@ const updateVaultURD = async (vaultURDAddress) => {
);
};
-// update the curent Vault's URD
+// update the current Vault's URD
await updateVaultURD(vaultURDAddress);
```
@@ -477,7 +477,7 @@ const updateVaultURD = async (vaultURDAddress) => {
// deploy a new Vault URD and retrieve its address
const vaultURDAddress = await deployVaultURD();
-// update the curent Vault's URD
+// update the current Vault's URD
await updateVaultURD(vaultURDAddress);
```
@@ -543,7 +543,7 @@ const updateVaultURD = async (vaultURDAddress) => {
// deploy a new Vault URD and retrieve its address
const vaultURDAddress = await deployVaultURD();
-// update the curent Vault's URD
+// update the current Vault's URD
await updateVaultURD(vaultURDAddress);
```
diff --git a/docs/networks/mainnet/running-a-node.md b/docs/networks/mainnet/running-a-node.md
index e22c2b69e1..f3be589849 100644
--- a/docs/networks/mainnet/running-a-node.md
+++ b/docs/networks/mainnet/running-a-node.md
@@ -25,7 +25,7 @@ Anyone is welcome to participate in the LUKSO network by running her/his own nod
Map of the LUKSO genesis validators from the execution stats website - 19.09.23.
diff --git a/docs/networks/testnet/running-a-node.md b/docs/networks/testnet/running-a-node.md
index becbf88296..eb2b7b7947 100644
--- a/docs/networks/testnet/running-a-node.md
+++ b/docs/networks/testnet/running-a-node.md
@@ -8,7 +8,7 @@ description: 'Run a Testnet LUKSO node with one of the three options: Dappnode,
:::info
-Running a testnet node is very similar to running a mainnet node. Therefore, we recommand you to read the [mainnet version](../mainnet/running-a-node.md) first and to adjust the commands with the instructions provided here.
+Running a testnet node is very similar to running a mainnet node. Therefore, we recommend you to read the [mainnet version](../mainnet/running-a-node.md) first and to adjust the commands with the instructions provided here.
:::
diff --git a/docs/standards/access-control/lsp14-ownable-2-step.md b/docs/standards/access-control/lsp14-ownable-2-step.md
index 8f972d4860..b9cdab3a2f 100644
--- a/docs/standards/access-control/lsp14-ownable-2-step.md
+++ b/docs/standards/access-control/lsp14-ownable-2-step.md
@@ -66,7 +66,7 @@ The hook is executed whenever the owner _initiates the process of transferring o
#### Accept Ownership Hooks
These hooks are designed to _notify the previous and new owner_ when ownership of the contract has been fully transferred. One hook notifies the previous owner and the second one notifies the new owner.
-Each hook is executed whenever the _new owner confirms the process of tranferring ownership_.
+Each hook is executed whenever the _new owner confirms the process of transferring ownership_.
- The hook that notifies the previous owner is only executed if the previous owner is a contract that **implements LSP1**.
- The hook that notifies the new owner is only executed if the new owner is a contract that **implements LSP1**.
@@ -77,8 +77,8 @@ Each hook is executed whenever the _new owner confirms the process of tranferrin
The control of the contract is refully renounced _once the owner of the contract confirmes the ownership renouncement_. The 2 steps of ownership renouncement are described below:
-1. The owner initiates the process of ownerhsip renouncement via the ['renounceOwnership()'](../../contracts/contracts/LSP14Ownable2Step/LSP14Ownable2Step.md#renounceownership) function.
+1. The owner initiates the process of ownership renouncement via the ['renounceOwnership()'](../../contracts/contracts/LSP14Ownable2Step/LSP14Ownable2Step.md#renounceownership) function.
-2. After waiting for 200 blocks to pass from the intiation of the ownership renouncement process the owner has a window of 200 block for confirming the renouncement via ['renounceOwnership()'](../../contracts/contracts/LSP14Ownable2Step/LSP14Ownable2Step.md#renounceownership). If the owner doesn't confirm in that window of time, the process cannot be confirmed and the owner must start again if it was intended to renounce ownership.
+2. After waiting for 200 blocks to pass from the initiation of the ownership renouncement process the owner has a window of 200 block for confirming the renouncement via ['renounceOwnership()'](../../contracts/contracts/LSP14Ownable2Step/LSP14Ownable2Step.md#renounceownership). If the owner doesn't confirm in that window of time, the process cannot be confirmed and the owner must start again if it was intended to renounce ownership.
diff --git a/docs/standards/access-control/lsp6-key-manager.md b/docs/standards/access-control/lsp6-key-manager.md
index d3a30546ec..50ed3e4c58 100644
--- a/docs/standards/access-control/lsp6-key-manager.md
+++ b/docs/standards/access-control/lsp6-key-manager.md
@@ -63,7 +63,7 @@ While the Key Manager allows for a very fine-grained control over the Universal
**Good practices:**
-1. Split the permissions over the Universal Profile accross different devices, hardware wallets or a combination of both.
+1. Split the permissions over the Universal Profile across different devices, hardware wallets or a combination of both.
2. Make sure to double or triple check when granting permissions to 3rd parties (other Universal Profiles, DApps, etc.).
:::
@@ -93,7 +93,7 @@ The `ADDCONTROLLER` permission enables to grant permissions to new addresses tha
The `ADDCONTROLLER` permission is needed to:
-- Give a new address some permission(s) by setting its permissions under `AddressPermissions:Permissions:` (this is also refered to _"adding a new controller"_)
+- Give a new address some permission(s) by setting its permissions under `AddressPermissions:Permissions:` (this is also referred to _"adding a new controller"_)
- Add a new controller address in the list of `AddressPermissions[index]` at a specific `index`.
- Increase the length of the `AddressPermissions[]` Array length (to describe that a new controller has been added).
@@ -775,7 +775,7 @@ A CompactBytesArray for these 3 different ERC725Y Data Keys would look like this
}
```
-Below is an example use case. An ERC725Account can allow some applications to add/edit informations on its storage via `setData(...)`. The account can restrict such Dapps and protocols to edit the data keys that are only relevant to the logic of their applications.
+Below is an example use case. An ERC725Account can allow some applications to add/edit information on its storage via `setData(...)`. The account can restrict such Dapps and protocols to edit the data keys that are only relevant to the logic of their applications.
diff --git a/docs/standards/accounts/lsp0-erc725account.md b/docs/standards/accounts/lsp0-erc725account.md
index 1e6eb76749..e9113e2d77 100644
--- a/docs/standards/accounts/lsp0-erc725account.md
+++ b/docs/standards/accounts/lsp0-erc725account.md
@@ -1,7 +1,7 @@
---
sidebar_label: 'LSP0 - ERC725 Account'
sidebar_position: 2
-descriotion: LUKSO's LSP0 - ERC725 Account.
+description: LUKSO's LSP0 - ERC725 Account.
---
# LSP0 - ERC725 Account
diff --git a/docs/standards/accounts/lsp17-contract-extension.md b/docs/standards/accounts/lsp17-contract-extension.md
index 474f36e0f7..dcd0ddb5d0 100644
--- a/docs/standards/accounts/lsp17-contract-extension.md
+++ b/docs/standards/accounts/lsp17-contract-extension.md
@@ -70,7 +70,7 @@ The 52 bytes of additional calldata appended to the call to the extension contra
While contracts can deploy and customize their own extensions, many smart contracts **share almost the same logic** for certain functions. In this case, the same extensions can be re-used by different contracts supporting LSP17.
-For example, **_smart contract A & B_** are two independant contracts that implement different functions but share the same logic for verifying signatures. Therefore, they can use the same extension for signature validation for the `isValidSignature(..)` function.
+For example, **_smart contract A & B_** are two independent contracts that implement different functions but share the same logic for verifying signatures. Therefore, they can use the same extension for signature validation for the `isValidSignature(..)` function.
diff --git a/docs/standards/accounts/lsp25-execute-relay-call.md b/docs/standards/accounts/lsp25-execute-relay-call.md
index 86931d5ed3..dad1d1b464 100644
--- a/docs/standards/accounts/lsp25-execute-relay-call.md
+++ b/docs/standards/accounts/lsp25-execute-relay-call.md
@@ -1,7 +1,7 @@
---
title: LSP25 - Execute Relay Call
sidebar_position: 9
-description: Learn about meta transactions using the LSP25 Execute Relay Call standards and how to use multi-channel nonces to dispatch transactions that are order independant or not.
+description: Learn about meta transactions using the LSP25 Execute Relay Call standards and how to use multi-channel nonces to dispatch transactions that are order independent or not.
---
# LSP25 - Execute Relay Call
diff --git a/docs/standards/factories/lsp16-universal-factory.md b/docs/standards/factories/lsp16-universal-factory.md
index 31d01ebeab..3e7555039c 100644
--- a/docs/standards/factories/lsp16-universal-factory.md
+++ b/docs/standards/factories/lsp16-universal-factory.md
@@ -21,7 +21,7 @@ LSP16 introduces a universal factory for deploying smart contracts using the CRE
## Introduction
-The use of different blockchain networks has brought with it a unique challenge: ensuring that an entity or user controlling an address on one chain can have the same control on another chain. For Externally Owned Accounts, this is known, as possesing the private key of the address means control over it regardless of the chain.
+The use of different blockchain networks has brought with it a unique challenge: ensuring that an entity or user controlling an address on one chain can have the same control on another chain. For Externally Owned Accounts, this is known, as possessing the private key of the address means control over it regardless of the chain.
@@ -35,7 +35,7 @@ Therefore, it's preferable to opt for a situation that can allow for the creatio
## What does this standard represent?
-This standard defines a contract called **Universal Factory** which provide a way to deploy the same contracts at the same addresses accross different chains given few requirements.
+This standard defines a contract called **Universal Factory** which provide a way to deploy the same contracts at the same addresses across different chains given few requirements.
@@ -57,7 +57,7 @@ For initializable contracts, the initialization data is included into the salt t
Additionally, it ensures that the same bytecode and salt will create the same contract address on different chains, given that the UniversalFactory contract was deployed on the same address on each chain.
-For a contract to be replicated at the same address accross different chain, it should be deployed using the same:
+For a contract to be replicated at the same address across different chain, it should be deployed using the same:
- Bytecode
- Salt
diff --git a/docs/standards/factories/lsp23-linked-contracts-factory.md b/docs/standards/factories/lsp23-linked-contracts-factory.md
index d2e7251fe8..bab9a2cb7b 100644
--- a/docs/standards/factories/lsp23-linked-contracts-factory.md
+++ b/docs/standards/factories/lsp23-linked-contracts-factory.md
@@ -18,7 +18,7 @@ LSP 23 simplifies the deployment of interdependent smart contracts by providing
Deploying smart contracts that are interdependent can be a complex process. Often, two or more contracts need each other's addresses at deployment, creating a circular dependency that can be challenging to resolve.
-
+
The LSP23 Linked Contracts Factory addresses this issue by providing a unified interface for deploying linked contracts with an optional post-deployment execution. This standard simplifies the deployment of complex contract systems, making it easier for developers to deploy interdependent contracts without the need for manual intervention.
diff --git a/docs/standards/introduction.md b/docs/standards/introduction.md
index 052cceedea..03356eeaca 100644
--- a/docs/standards/introduction.md
+++ b/docs/standards/introduction.md
@@ -1,6 +1,6 @@
---
title: 'Introduction'
-description: Introduction to LSPs (LUKSO Standars Proposals).
+description: Introduction to LSPs (LUKSO Standard Proposals).
---
import StandardsGallery from '@site/src/components/StandardsGallery';
diff --git a/docs/standards/metadata/lsp2-json-schema.md b/docs/standards/metadata/lsp2-json-schema.md
index 4b7257bf6a..1a095a171f 100644
--- a/docs/standards/metadata/lsp2-json-schema.md
+++ b/docs/standards/metadata/lsp2-json-schema.md
@@ -58,7 +58,7 @@ By introducing a schema, we can represent contract storage in the same way acros
LSP2 introduces new ways to encode data, depending on its type. From a single entry to multiple entries (like arrays or maps).
-A data key in the contract storage can be defined as a JSON object with properties that describe the key. The schema includes informations about the data key itself, as well as its value to explain what this data represents.
+A data key in the contract storage can be defined as a JSON object with properties that describe the key. The schema includes information about the data key itself, as well as its value to explain what this data represents.
- the data `key` itself: the `bytes32` hex value used when calling [`setData`](../../contracts/contracts/ERC725/ERC725.md#setdata) or [`setDataBatch`](../../contracts/contracts/ERC725/ERC725.md#setdatabatch) on the smart contract.
- the data key `name`: human readable version
diff --git a/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md b/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md
index eed696a810..a5728da5e4 100644
--- a/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md
+++ b/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md
@@ -162,7 +162,7 @@ LSP4 defines 3 default token types (see [table above](./LSP4-Digital-Asset-Metad
}
```
-The value attached to this data key repesents the type of token of the digital asset. The defaults values are:
+The value attached to this data key represents the type of token of the digital asset. The defaults values are:
- 0 (Token)
- 1 (NFT)
diff --git a/docs/standards/tokens/LSP7-Digital-Asset.md b/docs/standards/tokens/LSP7-Digital-Asset.md
index 8a3a7dafb1..1f0a6ffc33 100644
--- a/docs/standards/tokens/LSP7-Digital-Asset.md
+++ b/docs/standards/tokens/LSP7-Digital-Asset.md
@@ -61,7 +61,7 @@ To ensure a flexible and generic asset representation, the token contract should
:::caution
-When LSP7 assets are transfered, the LSP7 contract will notify the token sender and recipient using [`_notifyTokenSender(...)`](../../contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md#_notifytokensender) and [`_notifyTokenReceiver(...)`](../../contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md#_notifytokenreceiver).
+When LSP7 assets are transferred, the LSP7 contract will notify the token sender and recipient using [`_notifyTokenSender(...)`](../../contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md#_notifytokensender) and [`_notifyTokenReceiver(...)`](../../contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md#_notifytokenreceiver).
**These methods will make external calls** to the [`universalReceiver(...)`](../../contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md#universalreceiver) functions of both the sender and recipient.
diff --git a/docs/tools/libraries/erc725js/methods.md b/docs/tools/libraries/erc725js/methods.md
index 1b3b3a0fa7..2a2d561e58 100644
--- a/docs/tools/libraries/erc725js/methods.md
+++ b/docs/tools/libraries/erc725js/methods.md
@@ -2730,7 +2730,7 @@ The encoded permission (32bytes hex).
| Name | Type | Description |
| :------------------- | :----- | :------------------------------------------------------------------------------------------------- |
-| `decodedPermissions` | Object | An object specifying whether default LSP6 permissions are included in provided hexademical string. |
+| `decodedPermissions` | Object | An object specifying whether default LSP6 permissions are included in provided hexadecimal string. |
#### Example
diff --git a/docs/tools/libraries/lsp-utils/LSP23LinkedContractsFactory.md b/docs/tools/libraries/lsp-utils/LSP23LinkedContractsFactory.md
index 2781cf5230..4f72a5ac9b 100644
--- a/docs/tools/libraries/lsp-utils/LSP23LinkedContractsFactory.md
+++ b/docs/tools/libraries/lsp-utils/LSP23LinkedContractsFactory.md
@@ -13,7 +13,7 @@ Deploy Universal Profile with Key Manager using LSP23 Linked Contracts Factory.
| Name | Type | Description |
| :---------------------- | :------------------- | :-------------------------------------------------------------------------------- |
| `signer` | `Signer` \| `Wallet` | The signer used to deploy the contracts, needs to have native token for gas fees. |
-| `mainController` | `BytesLike` | The main controller for the Unviersal Profile. |
+| `mainController` | `BytesLike` | The main controller for the Universal Profile. |
| `additionalDataKeys` | `BytesLike`[] | Data keys that you want to set on deployment. |
| `additionalDataValues` | `BytesLike`[] | Data values that you want to set on deployment. |
| `additionalControllers` | `LSP6Controller`[] | Additional controllers for the deployed Universal Profile. |
diff --git a/docs/tools/libraries/lsp-utils/LSP5ReceivedAssets.md b/docs/tools/libraries/lsp-utils/LSP5ReceivedAssets.md
index f0e09e9494..fc296746be 100644
--- a/docs/tools/libraries/lsp-utils/LSP5ReceivedAssets.md
+++ b/docs/tools/libraries/lsp-utils/LSP5ReceivedAssets.md
@@ -12,7 +12,7 @@ Generate an array of Data Key/Value pairs to be set on the receiver address afte
| Name | Type | Description |
| :----------------- | :----------------- | :---------------------------------------------------------------------- |
-| `erc725YContract` | `UniversalProfile` | The contract instance of the asset reciever. |
+| `erc725YContract` | `UniversalProfile` | The contract instance of the asset receiver. |
| `assetAddress` | `BytesLike` | The address of the asset being received (_e.g: an LSP7 or LSP8 token_). |
| `assetInterfaceId` | `BytesLike` | The interfaceID of the asset being received. |
diff --git a/docs/tools/libraries/lsp-utils/LSP6KeyManager.md b/docs/tools/libraries/lsp-utils/LSP6KeyManager.md
index e117d47956..9c73ef08fa 100644
--- a/docs/tools/libraries/lsp-utils/LSP6KeyManager.md
+++ b/docs/tools/libraries/lsp-utils/LSP6KeyManager.md
@@ -27,7 +27,7 @@ v0.0.1
**`Throws`**
-When teh bytes value of either `startingTimestamp` or `endingTimestamp` exceeds 16 bytes.
+When the bytes value of either `startingTimestamp` or `endingTimestamp` exceeds 16 bytes.
**`See`**
@@ -169,7 +169,7 @@ Decode a hex value, containing a `BitArray` of permissions. The `AddressPermissi
| Name | Type | Description |
| :------------------------ | :------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `permissions` | `BytesLike` | A hex value, containing a BitArray of permissions. |
-| `decodedPermissionsType?` | `"bigint"` \| `"boolean"` \| `"BytesLike"` \| `"LSP6PermissionName"` | Optional param, defaults to `LSP6PermissionName`. Can be used to specfiy the type of the return array. Options: - `BytesLike` - `bigint` - `boolean` - `LSP6PermissionName` |
+| `decodedPermissionsType?` | `"bigint"` \| `"boolean"` \| `"BytesLike"` \| `"LSP6PermissionName"` | Optional param, defaults to `LSP6PermissionName`. Can be used to specify the type of the return array. Options: - `BytesLike` - `bigint` - `boolean` - `LSP6PermissionName` |
#### Returns
@@ -287,7 +287,7 @@ encodeAllowedCalls(
▸ **encodeAllowedERC725YDataKeys**(`dataKeys`): `string`
-Enocde a list of data keys as `{ "valueType": "bytes[CompactBytesArray]" }`. The result can be user for `AddressPermissions:AllowedERC725YDataKeys:`
+Encode a list of data keys as `{ "valueType": "bytes[CompactBytesArray]" }`. The result can be user for `AddressPermissions:AllowedERC725YDataKeys:`
#### Parameters
diff --git a/docs/tools/services/rpc-api.md b/docs/tools/services/rpc-api.md
index 3c9fe8e997..ced5287f88 100644
--- a/docs/tools/services/rpc-api.md
+++ b/docs/tools/services/rpc-api.md
@@ -69,7 +69,7 @@ It requests that the user provides an Ethereum address that should sign the tran
#### Returns
-`string` - on a successful call the method returns a signature, a string representing hex encoded bytes or an error with code `4001` - if the user rejects the requets
+`string` - on a successful call the method returns a signature, a string representing hex encoded bytes or an error with code `4001` - if the user rejects the requests
### personal_sign
diff --git a/spellcheck.log b/spellcheck.log
new file mode 100644
index 0000000000..f47dcd27d1
--- /dev/null
+++ b/spellcheck.log
@@ -0,0 +1,19 @@
+
+
+Error: ./docs/contracts/contracts/UniversalProfile.md:336: datas ==> data
+Error: ./docs/contracts/contracts/UniversalProfile.md:340: datas ==> data
+Error: ./docs/contracts/contracts/UniversalProfile.md:373: datas ==> data
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/src/components/ContractCardsGallery/index.tsx b/src/components/ContractCardsGallery/index.tsx
index f65f9c45b3..9ffc26c295 100644
--- a/src/components/ContractCardsGallery/index.tsx
+++ b/src/components/ContractCardsGallery/index.tsx
@@ -14,7 +14,7 @@ const Contracts_AccountsInteraction = [
url: '/contracts/overview/LSP1Delegate',
urlABI: '/contracts/contracts/LSP6KeyManager',
description:
- 'Allows to react on transfers and informations received (token transfers, notifications, etc...)',
+ 'Allows to react on transfers and information received (token transfers, notifications, etc...)',
},
{
diff --git a/src/components/StandardsGallery/index.tsx b/src/components/StandardsGallery/index.tsx
index 1f3c3a1269..2bc534a789 100644
--- a/src/components/StandardsGallery/index.tsx
+++ b/src/components/StandardsGallery/index.tsx
@@ -109,7 +109,7 @@ const STANDARDS = [
title: '💸 LSP18',
name: 'Royalties',
link: 'https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-18-Royalties.md',
- text: 'Set of data keys to store informations about royalty recipient addresses and their claimable percentage.',
+ text: 'Set of data keys to store information about royalty recipient addresses and their claimable percentage.',
},
{
title: '🔄 LSP20',