diff --git a/docs/contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md b/docs/contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md index 4fabf13e16..fd98e976ee 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/LSP7DigitalAsset.md @@ -234,7 +234,7 @@ Allows a caller to batch different function calls in one call. Perform a `delega function decimals() external view returns (uint8); ``` -Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned wiil be `0`. Otherwise `18` is the common value. +Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned will be `0`. Otherwise `18` is the common value. #### Returns @@ -937,7 +937,7 @@ Spend `amountToSpend` from the `operator`'s authorized on behalf of the `tokenOw | --------------- | :-------: | ------------------------------------------------------------------- | | `operator` | `address` | The address of the operator to decrease the allowance of. | | `tokenOwner` | `address` | The address that granted an allowance on its balance to `operator`. | -| `amountToSpend` | `uint256` | The amount of tokens to substract in allowance of `operator`. | +| `amountToSpend` | `uint256` | The amount of tokens to subtract in allowance of `operator`. |
@@ -1001,7 +1001,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1026,7 +1026,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7Burnable.md b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7Burnable.md index d5ecec050c..ed32191330 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7Burnable.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7Burnable.md @@ -1026,7 +1026,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1051,7 +1051,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md index 5c0d299173..db297ea27c 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CappedSupply.md @@ -232,7 +232,7 @@ Allows a caller to batch different function calls in one call. Perform a `delega function decimals() external view returns (uint8); ``` -Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned wiil be `0`. Otherwise `18` is the common value. +Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned will be `0`. Otherwise `18` is the common value. #### Returns @@ -634,7 +634,7 @@ function tokenSupplyCap() external view returns (uint256); _The maximum supply amount of tokens allowed to exist is `_TOKEN_SUPPLY_CAP`._ -Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSuuplyCap`](#totalsuuplycap), it is not possible to mint more tokens. +Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSupplyCap`](#totalsuuplycap), it is not possible to mint more tokens. #### Returns @@ -936,7 +936,7 @@ Spend `amountToSpend` from the `operator`'s authorized on behalf of the `tokenOw | --------------- | :-------: | ------------------------------------------------------------------- | | `operator` | `address` | The address of the operator to decrease the allowance of. | | `tokenOwner` | `address` | The address that granted an allowance on its balance to `operator`. | -| `amountToSpend` | `uint256` | The amount of tokens to substract in allowance of `operator`. | +| `amountToSpend` | `uint256` | The amount of tokens to subtract in allowance of `operator`. |
@@ -1000,7 +1000,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1025,7 +1025,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CompatibleERC20.md b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CompatibleERC20.md index 7917357227..d378bc992a 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CompatibleERC20.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/extensions/LSP7CompatibleERC20.md @@ -308,7 +308,7 @@ Allows a caller to batch different function calls in one call. Perform a `delega function decimals() external view returns (uint8); ``` -Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned wiil be `0`. Otherwise `18` is the common value. +Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned will be `0`. Otherwise `18` is the common value. #### Returns @@ -1061,7 +1061,7 @@ Spend `amountToSpend` from the `operator`'s authorized on behalf of the `tokenOw | --------------- | :-------: | ------------------------------------------------------------------- | | `operator` | `address` | The address of the operator to decrease the allowance of. | | `tokenOwner` | `address` | The address that granted an allowance on its balance to `operator`. | -| `amountToSpend` | `uint256` | The amount of tokens to substract in allowance of `operator`. | +| `amountToSpend` | `uint256` | The amount of tokens to subtract in allowance of `operator`. |
@@ -1091,7 +1091,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1116,7 +1116,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7CompatibleERC20Mintable.md b/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7CompatibleERC20Mintable.md index 0161d72f22..1f0e5b8d75 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7CompatibleERC20Mintable.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7CompatibleERC20Mintable.md @@ -315,7 +315,7 @@ Allows a caller to batch different function calls in one call. Perform a `delega function decimals() external view returns (uint8); ``` -Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned wiil be `0`. Otherwise `18` is the common value. +Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned will be `0`. Otherwise `18` is the common value. #### Returns @@ -1101,7 +1101,7 @@ Spend `amountToSpend` from the `operator`'s authorized on behalf of the `tokenOw | --------------- | :-------: | ------------------------------------------------------------------- | | `operator` | `address` | The address of the operator to decrease the allowance of. | | `tokenOwner` | `address` | The address that granted an allowance on its balance to `operator`. | -| `amountToSpend` | `uint256` | The amount of tokens to substract in allowance of `operator`. | +| `amountToSpend` | `uint256` | The amount of tokens to subtract in allowance of `operator`. |
@@ -1131,7 +1131,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1156,7 +1156,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7Mintable.md b/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7Mintable.md index 99fde2ae22..9e8388e4b1 100644 --- a/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7Mintable.md +++ b/docs/contracts/contracts/LSP7DigitalAsset/presets/LSP7Mintable.md @@ -265,7 +265,7 @@ Allows a caller to batch different function calls in one call. Perform a `delega function decimals() external view returns (uint8); ``` -Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned wiil be `0`. Otherwise `18` is the common value. +Returns the number of decimals used to get its user representation. If the asset contract has been set to be non-divisible via the `isNonDivisible_` parameter in the `constructor`, the decimals returned will be `0`. Otherwise `18` is the common value. #### Returns @@ -1001,7 +1001,7 @@ Spend `amountToSpend` from the `operator`'s authorized on behalf of the `tokenOw | --------------- | :-------: | ------------------------------------------------------------------- | | `operator` | `address` | The address of the operator to decrease the allowance of. | | `tokenOwner` | `address` | The address that granted an allowance on its balance to `operator`. | -| `amountToSpend` | `uint256` | The amount of tokens to substract in allowance of `operator`. | +| `amountToSpend` | `uint256` | The amount of tokens to subtract in allowance of `operator`. |
@@ -1065,7 +1065,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1090,7 +1090,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/LSP8IdentifiableDigitalAsset.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/LSP8IdentifiableDigitalAsset.md index 45152088eb..fc2b0ea465 100644 --- a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/LSP8IdentifiableDigitalAsset.md +++ b/docs/contracts/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. |
@@ -1185,7 +1185,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1210,7 +1210,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Burnable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Burnable.md index 3d623117a9..9f703d2e4b 100644 --- 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. |
@@ -1211,7 +1211,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1236,7 +1236,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md index 9841715d8b..4de60b91d4 100644 --- a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md +++ b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CappedSupply.md @@ -729,7 +729,7 @@ function tokenSupplyCap() external view returns (uint256); _The maximum supply amount of tokens allowed to exist is `_TOKEN_SUPPLY_CAP`._ -Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSuuplyCap`](#totalsuuplycap), it is not possible to mint more tokens. +Get the maximum number of tokens that can exist to circulate. Once [`totalSupply`](#totalsupply) reaches reaches [`totalSupplyCap`](#totalsuuplycap), it is not possible to mint more tokens. #### Returns @@ -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. |
@@ -1185,7 +1185,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1210,7 +1210,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CompatibleERC721.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CompatibleERC721.md index 7357fc5c76..8fcc8c1a74 100644 --- a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8CompatibleERC721.md +++ b/docs/contracts/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. |
@@ -1462,7 +1462,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1487,7 +1487,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Enumerable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/extensions/LSP8Enumerable.md index 37095361cf..db685e7a88 100644 --- 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. |
@@ -1238,7 +1238,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8CompatibleERC721Mintable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8CompatibleERC721Mintable.md index 7571dd9830..4caa1d5224 100644 --- a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8CompatibleERC721Mintable.md +++ b/docs/contracts/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. |
@@ -1506,7 +1506,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1531,7 +1531,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md b/docs/contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md index bdaaa1fce3..e665e656af 100644 --- 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. |
@@ -1251,7 +1251,7 @@ function _beforeTokenTransfer( ``` Hook that is called before any token transfer, including minting and burning. -Allows to run custom logic before updating balances and notifiying sender/recipient by overriding this function. +Allows to run custom logic before updating balances and notifying sender/recipient by overriding this function. #### Parameters @@ -1276,7 +1276,7 @@ function _afterTokenTransfer( ``` Hook that is called after any token transfer, including minting and burning. -Allows to run custom logic after updating balances, but **before notifiying sender/recipient via LSP1** by overriding this function. +Allows to run custom logic after updating balances, but **before notifying sender/recipient via LSP1** by overriding this function. #### Parameters diff --git a/docs/contracts/contracts/LSP9Vault/LSP9Vault.md b/docs/contracts/contracts/LSP9Vault/LSP9Vault.md index ded563c24c..7b74a92fb3 100644 --- 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.md b/docs/contracts/contracts/UniversalProfile.md index 0af3ab61c4..1af69dc7ab 100644 --- a/docs/contracts/contracts/UniversalProfile.md +++ b/docs/contracts/contracts/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/contracts/UniversalProfile/UniversalProfile.md b/docs/contracts/contracts/UniversalProfile/UniversalProfile.md index 289bba5c56..4257ec4e56 100644 --- 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 index a595db9ac2..5ae0aa66ce 100644 --- 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 diff --git a/docs/contracts/introduction.md b/docs/contracts/introduction.md index 2016aa8e5f..fbdbf13701 100644 --- a/docs/contracts/introduction.md +++ b/docs/contracts/introduction.md @@ -160,7 +160,7 @@ The `@lukso/lsp-smart-contracts` repository contains two types of contracts: | Type | Description | Example | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------- | | **Standard contracts** | One contract deployed per user. Deployed and initialized via a `constructor`. | `LSP0ERC725Account.sol` | -| **Base contracts** | Deploy one contract for all users. To be used as base contract behind proxies. Initialized via a `initalize(...)` function. | `LSP0ERC725AccountInit.sol` | +| **Base contracts** | Deploy one contract for all users. To be used as base contract behind proxies. Initialized via a `initialize(...)` function. | `LSP0ERC725AccountInit.sol` | ## LSP Recipes diff --git a/docs/contracts/libraries/LSP1Utils.md b/docs/contracts/libraries/LSP1Utils.md index b57da1178d..d0302372ea 100644 --- a/docs/contracts/libraries/LSP1Utils.md +++ b/docs/contracts/libraries/LSP1Utils.md @@ -16,7 +16,7 @@ > LSP1 Utility library. -LSP1Utils is a library of utility functions that can be used to notify the `universalReceiver` function of a contract that implements LSP1 and retrieve informations related to LSP1 `typeId`. Based on LSP1 Universal Receiver standard. +LSP1Utils is a library of utility functions that can be used to notify the `universalReceiver` function of a contract that implements LSP1 and retrieve information related to LSP1 `typeId`. Based on LSP1 Universal Receiver standard. ## Internal Methods diff --git a/docs/contracts/overview/KeyManager.md b/docs/contracts/overview/KeyManager.md index ef182255fe..5ac17be1df 100644 --- a/docs/contracts/overview/KeyManager.md +++ b/docs/contracts/overview/KeyManager.md @@ -23,7 +23,7 @@ You can then grant partial access to any address so that they can use your Unive | Example | Description | Permissions | | :-------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------- | | Treasury & Funds Manager | Allow certain addresses to transfer your native tokens (or any LSP7 tokens) to certain specific addresses (_e.g: allow a crypto accountant or treasury manager to manage your funds on your behalf, allow a video game dApp to transfer the game tokens, etc..._) | `SUPER_TRANSFERVALUE`
or `TRANSFERVALUE` + Allowed Calls on specific addresses
or `CALL` + Allowed Calls on certain token addresses. | -| Brand Manager | Allow certain addresses representating Marketing managers to either manage the metadata (and branding) of your Universal Profile, or the metadata of any NFT collections created by your Universal Profile. | `SETDATA` + Allowed ERC725Y Data Keys to manage the UP
`CALL` + Allowed Calls on specific NFT collection contract addresses. | +| Brand Manager | Allow certain addresses representing Marketing managers to either manage the metadata (and branding) of your Universal Profile, or the metadata of any NFT collections created by your Universal Profile. | `SETDATA` + Allowed ERC725Y Data Keys to manage the UP
`CALL` + Allowed Calls on specific NFT collection contract addresses. | | Metadata Manager | Allow certain dApps to store some user settings related to the dApp under the Universal Profile's storage, and allow each specific dApp to update these specific data only. | `SETDATA` + Allowed ERC725Y Data Keys | | Universal Receiver Delegate | Allow your Universal Receiver Delegate to operate automatically when receiving tokens or NFTs (_e.g: add / remove them in your received assets, automatically transfer a certain percentage of tokens received into a saving vault, save certain valuable NFTs into a vault, etc..._) | | | Social Recovery | Plug a service to gain you back access to your 🆙 if you have a lost access to your main controller private key / address. | `ADDCONTROLLER` | @@ -72,7 +72,7 @@ If controller has `CALL` permission but has no `AllowedCalls`, controller will n ::: -Key Manager allows for restricting controller addresses to be able to call specific functions on specific addresses which should be of a specific standard. In order to achieve such functionallity one could encode a set of type calls, addresses, standards and functions to [`bytes[CompactBytesArray]`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-2-ERC725YJSONSchema.md#bytesncompactbytesarray), and store them under the [Allowed Calls](../../standards/access-control/lsp6-key-manager.md#allowed-calls) data key. +Key Manager allows for restricting controller addresses to be able to call specific functions on specific addresses which should be of a specific standard. In order to achieve such functionality one could encode a set of type calls, addresses, standards and functions to [`bytes[CompactBytesArray]`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-2-ERC725YJSONSchema.md#bytesncompactbytesarray), and store them under the [Allowed Calls](../../standards/access-control/lsp6-key-manager.md#allowed-calls) data key. _E.g._ diff --git a/docs/contracts/overview/LSP1Delegate.md b/docs/contracts/overview/LSP1Delegate.md index 9dac7ebef0..9e61b9738f 100644 --- a/docs/contracts/overview/LSP1Delegate.md +++ b/docs/contracts/overview/LSP1Delegate.md @@ -14,7 +14,7 @@ There are two default implementations of the LSP1 Delegate contracts available, ## Routing -The Universal Profile implementation allows for attaching multiple instances of Universal Receiver Delegate to it. This is due to LSP1 Routing. You could have a single General Purpose Unviersal Receiver Delegate and multiple instances of Specific Unviersal Receiver Delegate. +The Universal Profile implementation allows for attaching multiple instances of Universal Receiver Delegate to it. This is due to LSP1 Routing. You could have a single General Purpose Universal Receiver Delegate and multiple instances of Specific Universal Receiver Delegate. A General Purpose Universal Receiver Delegate has its address stored under the [LSP1UniversalReceiverDelegate Singleton](/standards/accounts/lsp1-universal-receiver-delegate.md#lsp1universalreceiverdelegate-singleton) data key. This contract will be called on any LSP1 hook, meaning that it can potentially react on any [TypeID](../type-ids.md#universal-receiver-type-ids). diff --git a/docs/faq/lukso/feature-requests.md b/docs/faq/lukso/feature-requests.md index abeb28ed42..af6c419bce 100644 --- a/docs/faq/lukso/feature-requests.md +++ b/docs/faq/lukso/feature-requests.md @@ -16,7 +16,7 @@ Yes, developers have several options for financial support when building on LUKS ## Will LUKSO be listed on additional exchanges? -At the moment, LUKSO is available on [KuCoin](https://www.kucoin.com/de), [Crypto.com](https://crypto.com/), and [Gate.io](https://www.gate.io/). As the network continues to expand, additionl exchanges may consider joining. It is important to note that this decision is entirely at the discretion of the exchanges. +At the moment, LUKSO is available on [KuCoin](https://www.kucoin.com/de), [Crypto.com](https://crypto.com/), and [Gate.io](https://www.gate.io/). As the network continues to expand, additional exchanges may consider joining. It is important to note that this decision is entirely at the discretion of the exchanges. ## Will there be a Mobile Application for Universal Profiles? diff --git a/docs/faq/lukso/project-differentiation.md b/docs/faq/lukso/project-differentiation.md index 0fb708bef7..f24750ad1f 100644 --- a/docs/faq/lukso/project-differentiation.md +++ b/docs/faq/lukso/project-differentiation.md @@ -12,7 +12,7 @@ The [Ethereum Name Service](https://docs.ens.domains/) (ENS) and Universal Profi ENS is a **naming system** for accounts on the Ethereum blockchain. It functions similarly to the internet's domain name system (DNS), enabling users to replace long, complex blockchain addresses with verifiable human-friendly names. Name services make it easier for users to send transactions and interact with smart contracts without remembering their account addresses. Users can even add additional information, such as social media links, email addresses, keywords, or profile pictures. -Universal Profiles, on the other hand, are **accounts acting as the center for your user profile, persona and blockchain interactions**. They can have extensive and editable informations directly embedded on them (on the smart contract that represents the Universal Profile) while also being able to interact with on-chain applications, just as regular wallets. In comparison, information associated to an ENS name is stored and maintained within a global ENS registry service. +Universal Profiles, on the other hand, are **accounts acting as the center for your user profile, persona and blockchain interactions**. They can have extensive and editable information directly embedded on them (on the smart contract that represents the Universal Profile) while also being able to interact with on-chain applications, just as regular wallets. In comparison, information associated to an ENS name is stored and maintained within a global ENS registry service. While name services are convenient for transferring assets, they are **not as fitting to maintain an on-chain persona**. The domains can not be secured with multiple keys, have limited attachable information, and require payments to keep your domain names. If the subscription expires, all historical transactions no longer bear this name, meaning **users would lose their** verifiable information and **reputation** connected to the name. Anyone else could rebuy the domain and assume the identity associated with it. Universal Profiles can tackle such concerns, as they have convenience features such as **permission management and rotatable keys**. However, Universal Profiles are accounts and have regular blockchain addresses. diff --git a/docs/faq/lukso/project-origins.md b/docs/faq/lukso/project-origins.md index 3ce259e77c..cf441a523c 100644 --- a/docs/faq/lukso/project-origins.md +++ b/docs/faq/lukso/project-origins.md @@ -42,7 +42,7 @@ The official address of the Genesis Deposit Contract is [`0x42000421dd80d1e90e56 The deposit contract called the external LYXe [ERC777](https://ethereum.org/de/developers/docs/standards/tokens/erc-777/) token contract to lock the deposit amounts. To prepare the genesis files of the mainnet launch featured a freeze. Therefore, the deposit contract featured checks if a public key has been registered, preventing duplicate deposits. Only static deposit amounts of 32 LYX were allowed. -The freeze also came with a delay function to allow people to have time still after the LUKSO team triggered it. Each validator that went through the Genesis Launchpad stored not only the LYXe token but also a vote for the initial coin supply of the mainnet. The additional data was stored on-chain to have a publically verifiable source of the initial LYX supply and distribution. +The freeze also came with a delay function to allow people to have time still after the LUKSO team triggered it. Each validator that went through the Genesis Launchpad stored not only the LYXe token but also a vote for the initial coin supply of the mainnet. The additional data was stored on-chain to have a publicly verifiable source of the initial LYX supply and distribution. ## How was the token supply of LUKSO determined? diff --git a/docs/faq/network/blockchain-architecture.md b/docs/faq/network/blockchain-architecture.md index f7de66a626..aa9ed9f8f2 100644 --- a/docs/faq/network/blockchain-architecture.md +++ b/docs/faq/network/blockchain-architecture.md @@ -87,7 +87,7 @@ An epoch in PoS is a fixed period during which slots occur. It is a larger time Epochs provide several vital functions: - **Validator Shuffling**: At the start of each epoch, a random selection process determines the active validators and assigns them to slots. This is done to ensure that the system remains decentralized and that no single validator can predict far in advance when they will be selected. -- **Rewards and Penaltie**s: At the end of each epoch, rewards and penalties are calculated for validators. Validators that correctly proposed and attested to blocks receive rewards, while those who behaved maliciously or were offline are penalized. +- **Rewards and Penalties**: At the end of each epoch, rewards and penalties are calculated for validators. Validators that correctly proposed and attested to blocks receive rewards, while those who behaved maliciously or were offline are penalized. - **Finality**: An epoch also plays a role in achieving finality. Finality refers to the point at which a block cannot be changed or removed from the blockchain. The finality is achieved in every epoch. ## What are slots? diff --git a/docs/faq/network/node-setup.md b/docs/faq/network/node-setup.md index 338e2903f3..a9dbb6032f 100644 --- a/docs/faq/network/node-setup.md +++ b/docs/faq/network/node-setup.md @@ -30,7 +30,7 @@ Currently, LUKSO officially supports Geth, Erigon, Lighthouse, and Prysm. All cl ## Should I run an archive or a full node? -A full node downloads the entire blockchain and validates all blocks and transactions against the network's consensus rules. It stores the **current state of the network, including account balances, contracts, storage, and other informatio**n. However, it does not keep all historical states. If you need to check the balance of an account at a specific block height in the past, a full node cannot provide this information directly. +A full node downloads the entire blockchain and validates all blocks and transactions against the network's consensus rules. It stores the **current state of the network, including account balances, contracts, storage, and other information**. However, it does not keep all historical states. If you need to check the balance of an account at a specific block height in the past, a full node cannot provide this information directly. An archive node is a particular type of full node. It also downloads the entire blockchain and validates all blocks and transactions like a full node. In addition to the current state of the network, it **also stores all historical states since the genesis block**. Keeping the entire historical state makes an archive node much more storage extensive than a full node, but it allows you to query any historical state directly on the node. diff --git a/docs/faq/network/staking.md b/docs/faq/network/staking.md index 6afee81fc9..8f04af5406 100644 --- a/docs/faq/network/staking.md +++ b/docs/faq/network/staking.md @@ -40,7 +40,7 @@ No. Rewards are given out for each validator key separately and do not increase ## Are LYX/LYXt locked after they have been deposited? -No, validators are not locked after depositing their stake. The locking **only occurred for genesis deposits** before the Shappella fork went live on the LUKSO mainnet. Please remember that the deposited LYX can only be exited from the network after they have been activated, which may take up to 24h. In addition, the exit process may also **take up to multiple hours** until it is picked up from the consensus. Please also note that it requires setting withdrawal credentials to withdraw your funds to an account. +No, validators are not locked after depositing their stake. The locking **only occurred for genesis deposits** before the Shapella fork went live on the LUKSO mainnet. Please remember that the deposited LYX can only be exited from the network after they have been activated, which may take up to 24h. In addition, the exit process may also **take up to multiple hours** until it is picked up from the consensus. Please also note that it requires setting withdrawal credentials to withdraw your funds to an account. ## Are there different types of withdrawals for validators? @@ -102,6 +102,6 @@ In case you have multiple wallets to make deposits from but you don't want to se ## How much stake will I lose for being offline? -The exact calculation of penalties can be complex due to these variables, but there are rough estimates based on the [EVM Panelty Research](https://alonmuroch-65570.medium.com/how-long-will-it-take-an-inactive-eth2-validator-to-get-ejected-a6ce8f98fd1c). You will roughly lose 0.01 LYX/LYXt per validatory for being offline for an hour. After being offline for a whole day, it will increase to about 0.1 LYX/LYXt. After an entire offline week, it will be approximately 1 LYX/LYXt per validator. +The exact calculation of penalties can be complex due to these variables, but there are rough estimates based on the [EVM Penalty Research](https://alonmuroch-65570.medium.com/how-long-will-it-take-an-inactive-eth2-validator-to-get-ejected-a6ce8f98fd1c). You will roughly lose 0.01 LYX/LYXt per validatory for being offline for an hour. After being offline for a whole day, it will increase to about 0.1 LYX/LYXt. After an entire offline week, it will be approximately 1 LYX/LYXt per validator. A validator will lose roughly 60% of their staked LYX after 18 days of inactivity. It takes around three weeks for the effective balance to fall to around 16 LYX/LYXt, which will cause the validator to be ejected from the PoS protocol. Remember, these are **rough estimates, and the penalties could differ** based on the network conditions. If the network is not finalizing, e.g., over one-third of the network is offline, penalties can ramp up significantly. diff --git a/docs/faq/network/validators.md b/docs/faq/network/validators.md index 503bf2db25..3478953b0f 100644 --- a/docs/faq/network/validators.md +++ b/docs/faq/network/validators.md @@ -56,7 +56,7 @@ If you plan to become a validator for testnet, please contact `testnet-validator ## What happens when my validator is offline? -In Proof of Stake, validators can be penalized for being offline. The **penalties for an offline validator are dynamically adjusted** based on the total amount of offline validators and their offline duration. You can find rough estemates within the [staking section](./staking.md) of the FAQ. +In Proof of Stake, validators can be penalized for being offline. The **penalties for an offline validator are dynamically adjusted** based on the total amount of offline validators and their offline duration. You can find rough estimates within the [staking section](./staking.md) of the FAQ. This mechanism **incentivizes validators to stay online** and actively participate in the network's consensus process. Validators are expected to be online to propose and attest to blocks. If a validator is offline, they're not fulfilling their role, so their balance slowly leaks over time. The inactivity penalty is proportional to the square of the time the validator has been offline, meaning the penalty accelerates the longer the validator is offline. diff --git a/docs/faq/onboarding/lukso-standards.md b/docs/faq/onboarding/lukso-standards.md index 841508c480..686357fa44 100644 --- a/docs/faq/onboarding/lukso-standards.md +++ b/docs/faq/onboarding/lukso-standards.md @@ -23,14 +23,14 @@ With LSPs, the mission is to have standards that facilitate using tools that abs - Assets can be **anchored** directly to the blockchain **account's storage** using [LSP1](/standards/accounts/lsp1-universal-receiver), abandoning complex data fetching. - Token IDs have an increased size and can map any serial number (for digital or physical products) on-chain, which also allows NFC integration. - Developers and users can safely utilize **events from asset contracts**, regulate allowlists and blocklists, customize UI and app workflows, or create consensus for asset transfers using LSP1 Delegate. -- Assets have **built-in security for sending assets** to accounts without recovery, utiliszing account abstraction with their force parameter in [LSP7](/standards/tokens/LSP7-Digital-Asset) and [LSP8](/standards/tokens/LSP8-Identifiable-Digital-Asset). +- Assets have **built-in security for sending assets** to accounts without recovery, utilizing account abstraction with their force parameter in [LSP7](/standards/tokens/LSP7-Digital-Asset) and [LSP8](/standards/tokens/LSP8-Identifiable-Digital-Asset). - Attached data can always be verified through hash integration in the [LSP2](/standards/metadata/lsp2-json-schema) schema. - Assets can be **organized and managed in vaults** using [LSP9](/standards/accounts/lsp9-vault). Here, multiple services and games can have permissioned access for updating the asset data of user accounts. - For NFTs, individual token IDs from a collection can have **separate metadata**, upgrades, creators, and behaviors, instead of just being limited to the logic of the mint contract. ## What's the recommended language for LSP development? -If you want to build on the LUKSO blockchain, the recommended programming language is Solidity. It is the implementation language of LSPs, the most commonly used language for the EVM, and the default implementation langauge for LSPs. +If you want to build on the LUKSO blockchain, the recommended programming language is Solidity. It is the implementation language of LSPs, the most commonly used language for the EVM, and the default implementation language for LSPs. ## Why are LSPs not proposed as ERCs? diff --git a/docs/learn/concepts.md b/docs/learn/concepts.md index 022be0400c..e2cc6013c4 100644 --- a/docs/learn/concepts.md +++ b/docs/learn/concepts.md @@ -23,5 +23,5 @@ Highlight any word and click `Ask Cookbook` in the Navbar for its definition. | [ERC725Y](/standards/erc725#erc725x) | ERC725Y is the basic tool that lets you store information, while LSP2 is the set of rules that makes sure everyone stores and retrieves this information in an organized and understandable way. | | [LYXt](../../docs/faq/lukso/general-information.md#whats-the-difference-between-lyxt-lyxe-and-lyx) | LYXt is the token for developers to use on our testnet. It can always be acquired by anyone for free. | | [LYXe](../../docs/faq/lukso/general-information.md#whats-the-difference-between-lyxt-lyxe-and-lyx) | LYXe is the token that was deployed on Ethereum before LUKSO Mainnet was launched. It allowed people to invest in LUKSO pre-launch. | -| [Metadata](/standards/metadata/lsp3-profile-metadata.md) | This typically refers to the additional data that is stored against a token or NFT. The difference on LUKSO is it can be extended.
For example, imagine you've bought a house and have the deed as an NFT on LUKSO. Well now, as rennovations are carried out, they can be continually added to the NFT for history. | +| [Metadata](/standards/metadata/lsp3-profile-metadata.md) | This typically refers to the additional data that is stored against a token or NFT. The difference on LUKSO is it can be extended.
For example, imagine you've bought a house and have the deed as an NFT on LUKSO. Well now, as renovations are carried out, they can be continually added to the NFT for history. | | Account Abstraction | Account abstraction is abstracting away smart contract execution from storing funds. With a smart contract account, you can program it to do all sorts of things. You can set up automatic payments, create multi-signature wallets that require multiple people to approve transactions, or even add security features like daily spending limits. It's like having a customizable, programmable bank account on the blockchain. | diff --git a/docs/learn/digital-assets/metadata-management/cascade-and-sense-support.md b/docs/learn/digital-assets/metadata-management/cascade-and-sense-support.md index e9acc41d68..991d9be523 100644 --- a/docs/learn/digital-assets/metadata-management/cascade-and-sense-support.md +++ b/docs/learn/digital-assets/metadata-management/cascade-and-sense-support.md @@ -72,7 +72,7 @@ if (result) { ### Retrieve activation ticket transaction id -To get activation ticket transaction status and id, you can use `retrieveTxId` funciton of provider. +To get activation ticket transaction status and id, you can use `retrieveTxId` function of provider. ``` const { result_id } = await provider.uploadToCascade(file); diff --git a/docs/learn/digital-assets/metadata-management/read-asset-data.md b/docs/learn/digital-assets/metadata-management/read-asset-data.md index 53cfa1308b..acb3dfa6c1 100644 --- a/docs/learn/digital-assets/metadata-management/read-asset-data.md +++ b/docs/learn/digital-assets/metadata-management/read-asset-data.md @@ -235,7 +235,7 @@ console.log(tokenSymbol); To fetch the whole JSON file of the asset's metadata, you can use the following 2 functions of the [`erc725js`](../../../tools/dapps/erc725js/getting-started.md) library: - [`fetchData('LSP4Metadata')`](../../../tools/dapps/erc725js/methods.md#fetchdata): This will download and decode the content of `VerifiableURI` as JSON. -- [`getData(LSP4Metadata)`](../../../tools/dapps/erc725js/methods#getdata): This will retrieve the raw data value from the smart contract. You will then need to decode the `VerifiableURI` maunually using [`decodeData(...)`](../../../tools/dapps/erc725js/methods.md#decodedata). +- [`getData(LSP4Metadata)`](../../../tools/dapps/erc725js/methods#getdata): This will retrieve the raw data value from the smart contract. You will then need to decode the `VerifiableURI` manually using [`decodeData(...)`](../../../tools/dapps/erc725js/methods.md#decodedata). ```ts // Download and verify the asset metadata JSON file @@ -386,4 +386,4 @@ Based on the [token type](#detect-the-token-type), the information of the [LSP4 - If your asset is a Token (`tokenType = 0`), individual metadata **cant be set**, due to the lack of token IDs. - If your asset is an NFT (`tokenType = 1`), individual metadata **may be set in addition** to the global token information. -- If your asset is a Collection (`tokenType = 2`), the token ID-specific medatada is **mandatory**. +- If your asset is a Collection (`tokenType = 2`), the token ID-specific metadata is **mandatory**. diff --git a/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md b/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md index 48cb117f75..0ea59f317f 100644 --- a/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md +++ b/docs/learn/digital-assets/nft/create-nft-collection-lsp8.md @@ -33,7 +33,7 @@ When creating smart contracts representing digital assets on LUKSO, you need to - `1` = NFT - `2` = Collection -For this example we will use the `Collection` token type. You can create a custom 🌄 [LSP8 Identfiable Digital Asset Collection](../../../standards/tokens/LSP8-Identifiable-Digital-Asset.md) that extends [LSP8Mintable](../../../contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md) so that new assets can be created within the smart contract. +For this example we will use the `Collection` token type. You can create a custom 🌄 [LSP8 Identifiable Digital Asset Collection](../../../standards/tokens/LSP8-Identifiable-Digital-Asset.md) that extends [LSP8Mintable](../../../contracts/contracts/LSP8IdentifiableDigitalAsset/presets/LSP8Mintable.md) so that new assets can be created within the smart contract. ```solidity title="contracts/BasicNFTCollection.sol" // SPDX-License-Identifier: MIT diff --git a/docs/learn/digital-assets/nft/read-nft-metadata.md b/docs/learn/digital-assets/nft/read-nft-metadata.md index 1711133355..c9df909a43 100644 --- a/docs/learn/digital-assets/nft/read-nft-metadata.md +++ b/docs/learn/digital-assets/nft/read-nft-metadata.md @@ -389,7 +389,7 @@ Assets created with LSP versions below 🛠️ [`@lukso/lsp-smart-contracts`](/t ::: -You can fetch the [`LSP8TokenMetadataBaseURI`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenmetadatabaseuri) and build the correct metadata link by concatinating the [formatted](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenidformat) token ID. Based on the [`LSP8TokenIDFormat`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenidformat), the Base URI can either be: +You can fetch the [`LSP8TokenMetadataBaseURI`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenmetadatabaseuri) and build the correct metadata link by concatenating the [formatted](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenidformat) token ID. Based on the [`LSP8TokenIDFormat`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#lsp8tokenidformat), the Base URI can either be: - **equal across all token IDs**: To fetch the global Base URI, use the [`getData(...)`](../../../contracts/contracts/ERC725/ERC725.md#getdata) function of the asset to receive the [ERC725Y data storage](/standards/erc725.md#erc725y-generic-data-keyvalue-store). This applies if the [`LSP8TokenIDFormat`](#preparing-the-token-ids) is `0, 1, 2, or 4`. - **mixed across all token IDs**: To fetch the individual Base URI, use the [`getDataFromTokenID(...)`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-8-IdentifiableDigitalAsset.md#getdatafortokenid) function using a specific token ID. This has to be done if the [`LSP8TokenIDFormat`](#preparing-the-token-ids) is `100, 101, 102, or 104`. @@ -501,7 +501,7 @@ function generateMetadataLink(link: string) { // Use your default IPFS Gateway address return link; } - // If link has custom protocoll, adjust the link + // If link has custom protocol, adjust the link if (link.startsWith('ipfs://')) { // Use your default IPFS Gateway address return `https://api.universalprofile.cloud/ipfs/${link.slice(7)}`; @@ -529,7 +529,7 @@ if (metadataJsonLink) {
How to decode a tokenID from Byte32 Hex String according to LSP8TokenIdFormat
diff --git a/docs/learn/digital-assets/token/create-lsp7-token.md b/docs/learn/digital-assets/token/create-lsp7-token.md
index 914dde09fc..27896d6659 100644
--- a/docs/learn/digital-assets/token/create-lsp7-token.md
+++ b/docs/learn/digital-assets/token/create-lsp7-token.md
@@ -155,7 +155,7 @@ module.exports = [
];
```
-To verify the deployed token, you can use the **blockscout API properties** set up within the [Getting Started](../../../learn/getting-started.mdx) section. If you configured the API, you will be able to run the verification by specifying the _token address_, _paramter file_, and _network_:
+To verify the deployed token, you can use the **blockscout API properties** set up within the [Getting Started](../../../learn/getting-started.mdx) section. If you configured the API, you will be able to run the verification by specifying the _token address_, _parameter file_, and _network_:
```bash
npx hardhat verify .default})
-Transfering 0.5 LYXt between two Universal Profiles. +Transferring 0.5 LYXt between two Universal Profiles.
.default})
-Transfering 1,000 CHILL tokens between two Universal Profiles. +Transferring 1,000 CHILL tokens between two Universal Profiles.
Example 1: allow only to CALL a specific LSP0 at a specific address
-To allow a controller to only do `CALL` to any function on a LSP0ERC725Account (interface ID `0x3e89ad98`) deployed at address `0xCA41e4ea94c8fA99889c8EA2c8948768cBaf4bc0`, the following value for the CompactBYytesArray of allowed calls will be used:
+To allow a controller to only do `CALL` to any function on a LSP0ERC725Account (interface ID `0x3e89ad98`) deployed at address `0xCA41e4ea94c8fA99889c8EA2c8948768cBaf4bc0`, the following value for the CompactBytesArray of allowed calls will be used:
`0x002000000002CA41e4ea94c8fA99889c8EA2c8948768cBaf4bc03e89ad98ffffffff`
@@ -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 569120d5e6..5ba6e3a884 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/lsp1-universal-receiver.md b/docs/standards/accounts/lsp1-universal-receiver.md
index 6b21004802..c67295a35b 100644
--- a/docs/standards/accounts/lsp1-universal-receiver.md
+++ b/docs/standards/accounts/lsp1-universal-receiver.md
@@ -66,7 +66,7 @@ For example, **to notify the recipient that he is about to receive tokens**, dur
- bytes32 `typeId`: **Hash**('ERCXXXXTokenReceived')
- bytes `data`: **packedData**(amount of token sent, the sender address, the block timestamp)
-In this way, instead of **listening to all the events of the token contrats on the network**, and checking which one of these transfers is relative to the recipient, users can listen to the **[UniversalReceiver](../../contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md#universalreceiver-1)** event on the contract implementing the `universalReceiver(..)` and know the token transfer details.
+In this way, instead of **listening to all the events of the token contracts on the network**, and checking which one of these transfers is relative to the recipient, users can listen to the **[UniversalReceiver](../../contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md#universalreceiver-1)** event on the contract implementing the `universalReceiver(..)` and know the token transfer details.
As well as emitting an event, the `universalReceiver(...)` function can implement **custom logic** to make the contract behave differently based on the data received. Some ideas include:
diff --git a/docs/standards/accounts/lsp15-transaction-relayer-api.md b/docs/standards/accounts/lsp15-transaction-relayer-api.md
index 7f2f788fd4..0cf75f32b9 100644
--- a/docs/standards/accounts/lsp15-transaction-relayer-api.md
+++ b/docs/standards/accounts/lsp15-transaction-relayer-api.md
@@ -57,7 +57,7 @@ Executes a signed transaction on behalf of a Universal Profile using [`executeRe
Returns the available quota left for a registered Universal Profile.
-- `signature` is the message value signed by a controller key with the [`SIGN` permission](../access-control/lsp6-key-manager#permissions) of the Universal Profile. The hash to sign should be calculated as [EIP-712](https://eips.ethereum.org/EIPS/eip-712) hash where the message is `keccack256(address, timestamp)`. Make sure that no matter the language or platform timestamp is of type `int`, `int256`, `uint` or `uint256`. In the backend the message is reconstructed using [soliditysha3()](https://web3js.readthedocs.io/en/v1.7.4/web3-utils.html#soliditysha3) to verify the signature.
+- `signature` is the message value signed by a controller key with the [`SIGN` permission](../access-control/lsp6-key-manager#permissions) of the Universal Profile. The hash to sign should be calculated as [EIP-712](https://eips.ethereum.org/EIPS/eip-712) hash where the message is `keccak256(address, timestamp)`. Make sure that no matter the language or platform timestamp is of type `int`, `int256`, `uint` or `uint256`. In the backend the message is reconstructed using [soliditysha3()](https://web3js.readthedocs.io/en/v1.7.4/web3-utils.html#soliditysha3) to verify the signature.
[Web3.js](https://web3js.readthedocs.io/en/v1.8.0/web3-eth-accounts.html?#sign) and [ethers.js](https://docs.ethers.io/v5/api/signer/#Signer-signMessage) both automatically hash when using their native sign functions. This may need to be done manually if using a different library.
diff --git a/docs/standards/accounts/lsp17-contract-extension.md b/docs/standards/accounts/lsp17-contract-extension.md
index d4d58b776d..617dc75570 100644
--- a/docs/standards/accounts/lsp17-contract-extension.md
+++ b/docs/standards/accounts/lsp17-contract-extension.md
@@ -72,7 +72,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 2e0709ec4c..3d904138aa 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 22bb76b6f1..c3322d4b08 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 9d9e5eaffd..018bc83aad 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 8390a52f99..1d5da93f3b 100644
--- a/docs/standards/metadata/lsp2-json-schema.md
+++ b/docs/standards/metadata/lsp2-json-schema.md
@@ -56,7 +56,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 single 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.
```json
{
diff --git a/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md b/docs/standards/tokens/LSP4-Digital-Asset-Metadata.md
index 47a4dd60bc..e9d76db520 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 a987f814cd..656b5f44a7 100644
--- a/docs/standards/tokens/LSP7-Digital-Asset.md
+++ b/docs/standards/tokens/LSP7-Digital-Asset.md
@@ -59,7 +59,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/standards/tokens/LSP8-Identifiable-Digital-Asset.md b/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md
index 41a467de12..02e1223c71 100644
--- a/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md
+++ b/docs/standards/tokens/LSP8-Identifiable-Digital-Asset.md
@@ -125,7 +125,7 @@ During an **ERC721 token transfer**, the ownership of the tokenId is changed fro
-During an **LSP8 token transfer**, as well as updating the tokenId ownership, both the sender and recipient are informed of the transfer by calling the **[`universalReceiever(...)`](../accounts/lsp1-universal-receiver.md#lsp1---universal-receiver)** function on their profiles.
+During an **LSP8 token transfer**, as well as updating the tokenId ownership, both the sender and recipient are informed of the transfer by calling the **[`universalReceiver(...)`](../accounts/lsp1-universal-receiver.md#lsp1---universal-receiver)** function on their profiles.
diff --git a/docs/tools/apis/up-rpc-api.md b/docs/tools/apis/up-rpc-api.md
index 4b9b8c45cf..d84b39f0a9 100644
--- a/docs/tools/apis/up-rpc-api.md
+++ b/docs/tools/apis/up-rpc-api.md
@@ -70,7 +70,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 request
### personal_sign
diff --git a/docs/tools/dapps/eip191-signerjs/getting-started.md b/docs/tools/dapps/eip191-signerjs/getting-started.md
index b196dbf764..1ea901ae15 100644
--- a/docs/tools/dapps/eip191-signerjs/getting-started.md
+++ b/docs/tools/dapps/eip191-signerjs/getting-started.md
@@ -18,7 +18,7 @@ The following format is used to sign data :
In the case of an Ethereum Signed Message:
- 1 byte version = `0x45`
-- version specific data = `thereum Signed Message:\n + len(message)`
+- version specific data = `Ethereum Signed Message:\n + len(message)`
In the case of data with intended validator:
diff --git a/docs/tools/dapps/erc725js/methods.md b/docs/tools/dapps/erc725js/methods.md
index 1b3b3a0fa7..a147007c1a 100644
--- a/docs/tools/dapps/erc725js/methods.md
+++ b/docs/tools/dapps/erc725js/methods.md
@@ -278,7 +278,7 @@ myErc725.encodeData(
const schemas = [
{
name: 'DynamicKey:
- Cookbook LSP Libraries
- Visual Studio Code Extension 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',