diff --git a/src/content/any-api/get-request/examples/single-word-response.mdx b/src/content/any-api/get-request/examples/single-word-response.mdx index 58d1fc9b2d9..cecf980e93f 100644 --- a/src/content/any-api/get-request/examples/single-word-response.mdx +++ b/src/content/any-api/get-request/examples/single-word-response.mdx @@ -109,7 +109,7 @@ To use this contract: - The `req._add("get", "CRYPTOCOMPARE_URL")` request parameter provides the oracle node with the [URL](https://min-api.cryptocompare.com/data/pricemultifull?fsyms=ETH&tsyms=USD) from which to fetch _ETH-USD_ trading info. - The `req._add('path', 'RAW,ETH,USD,VOLUME24HOUR')` request parameter tells the oracle node where to fetch the 24h ETH volume in the _json_ response. It uses a [JSONPath expression](https://jsonpath.com/) with comma(,) delimited string for nested objects. For example: `'RAW,ETH,USD,VOLUME24HOUR'`. - The `req._addInt('times', timesAmount)` request parameter provides the oracle node with the multiplier `timesAmount` by which the fetched volume is multiplied. Use this to remove any decimals from the volume. **_Note_**: The `times` parameter is mandatory. If the API that you call returns a number without any decimals then provide `1`as `timesAmount`. - The `APIConsumer` in the example above is flexible enough to call any public API as long as the URL in _get_, _path_, and _timesAmounnt_ are correct. + The `APIConsumer` in the example above is flexible enough to call any public API as long as the URL in _get_, _path_, and _timesAmount_ are correct. 1. After few seconds, call the `volume` function. You should get a non-zero response. diff --git a/src/content/any-api/introduction.mdx b/src/content/any-api/introduction.mdx index 8070413acc9..33d9395b355 100644 --- a/src/content/any-api/introduction.mdx +++ b/src/content/any-api/introduction.mdx @@ -51,7 +51,7 @@ Outlined below are multiple ways developers can connect smart contracts to offch | [HTTP GET Single Word Response](/any-api/get-request/examples/single-word-response) | This guide explains how to make an HTTP GET request and parse the _json_ response to retrieve the value of one single attribute. | | [HTTP GET Multi-Variable Responses](/any-api/get-request/examples/multi-variable-responses) | This guide explains how to make an HTTP GET request and parse the _json_ response to retrieve the values of multiple attributes. | | [HTTP GET Element in Array Response](/any-api/get-request/examples/array-response) | This guide explains how to make an HTTP GET request that returns a _json_ array and parse it to retrieve the target element's value. | -| [HTTP GET Large Reponses](/any-api/get-request/examples/large-responses) | This guide explains how to make an HTTP Get request that returns a _json_ containing an arbitrary-length raw byte data and parse it to return the data as _bytes_ data type. | +| [HTTP GET Large Responses](/any-api/get-request/examples/large-responses) | This guide explains how to make an HTTP Get request that returns a _json_ containing an arbitrary-length raw byte data and parse it to return the data as _bytes_ data type. | | [Existing Job Request](/any-api/get-request/examples/existing-job-request) | This guide explains how to call a job that leverages [External adapters](/chainlink-nodes/external-adapters/external-adapters) and returns the relevant data to the smart contract. This allows building succinct smart contracts that do not need to comprehend the URL or the response format of the target API. | ### Building external adapters diff --git a/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-foundry.mdx b/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-foundry.mdx index f59b09bb730..4aa7812fad5 100644 --- a/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-foundry.mdx +++ b/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-foundry.mdx @@ -265,7 +265,7 @@ forge script ./script/UpdateRateLimiters.s.sol:UpdateRateLimiters \ Suppose you want to enable inbound and outbound rate limits for your token pool on Avalanche Fuji to control the number of tokens received or sent from/to Arbitrum Sepolia. We will use an existing token pool that interacts with an ERC20 token with 18 decimals: -- **Token Pool on Avalance Fuji**: +- **Token Pool on Avalanche Fuji**: | Property | Outbound Rate Limiter | Inbound Rate Limiter | | ---------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | diff --git a/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-hardhat.mdx b/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-hardhat.mdx index ab805f9c788..c4a4c640fe2 100644 --- a/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-hardhat.mdx +++ b/src/content/ccip/tutorials/cross-chain-tokens/update-rate-limiters-hardhat.mdx @@ -244,7 +244,7 @@ npx hardhat updateRateLimiters \ Suppose you want to enable inbound and outbound rate limits for your token pool on Avalanche Fuji to control the number of tokens received or sent from/to Arbitrum Sepolia. We will use an existing token pool that interacts with an ERC20 token with 18 decimals: -- **Token Pool on Avalance Fuji**: +- **Token Pool on Avalanche Fuji**: - **Outbound Rate Limiter**: diff --git a/src/content/chainlink-automation/tutorials/vault-harvester.mdx b/src/content/chainlink-automation/tutorials/vault-harvester.mdx index c8025ba764c..f877564c4f4 100644 --- a/src/content/chainlink-automation/tutorials/vault-harvester.mdx +++ b/src/content/chainlink-automation/tutorials/vault-harvester.mdx @@ -439,4 +439,4 @@ abstract contract KeeperCompatibleHarvester is IHarvester, Ownable { } ``` -This is an abstract contract that iterates vaults from a provided list and fits vaults within upkeep gas limit. The contract also provides helper functions to calculate gas consumption and estimate profit and contains a trigger mechanism can be time-based, profit-based or custom. Finally, the cotract reports profits, successful harvests, and failed harvests. +This is an abstract contract that iterates vaults from a provided list and fits vaults within upkeep gas limit. The contract also provides helper functions to calculate gas consumption and estimate profit and contains a trigger mechanism can be time-based, profit-based or custom. Finally, the contract reports profits, successful harvests, and failed harvests. diff --git a/src/content/chainlink-functions/api-reference/functions-client.mdx b/src/content/chainlink-functions/api-reference/functions-client.mdx index 48b68cac957..6b9311584f7 100644 --- a/src/content/chainlink-functions/api-reference/functions-client.mdx +++ b/src/content/chainlink-functions/api-reference/functions-client.mdx @@ -96,7 +96,7 @@ _Either response or error parameter will be set, but never both_ function handleOracleFulfillment(bytes32 requestId, bytes response, bytes err) external ``` -Chainlink Functions response handler called by the Functions Router during fullilment from the designated transmitter node in an OCR round +Chainlink Functions response handler called by the Functions Router during fulfillment from the designated transmitter node in an OCR round _Either response or error parameter will be set, but never both_ diff --git a/src/content/chainlink-functions/supported-networks.mdx b/src/content/chainlink-functions/supported-networks.mdx index ce871b3ed39..1659aa74f5e 100644 --- a/src/content/chainlink-functions/supported-networks.mdx +++ b/src/content/chainlink-functions/supported-networks.mdx @@ -39,7 +39,7 @@ Read the [LINK Token Contracts](/resources/link-token-contracts) page to learn w | Item | Value | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Functions router |
| +| Functions router |
| | | / | | Encrypted secrets upload endpoints |
| diff --git a/src/content/chainlink-functions/tutorials/abi-decoding.mdx b/src/content/chainlink-functions/tutorials/abi-decoding.mdx index eb4a6d5862f..8e031cf9353 100644 --- a/src/content/chainlink-functions/tutorials/abi-decoding.mdx +++ b/src/content/chainlink-functions/tutorials/abi-decoding.mdx @@ -93,7 +93,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0x5618089ec9b5e662ec72c81241d78cb6daa135ecc3fa3a33032d910e3b47c2b1. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0x5618089ec9b5e662ec72c81241d78cb6daa135ecc3fa3a33032d910e3b47c2b1 - ✅ Request 0xdf22fa28c81a3ea78f356334b6d28d969e953009fae8ece4fe544f2eb466419b successfully fulfilled. Cost is 0.282344694329387405 LINK.Complete reponse: { + ✅ Request 0xdf22fa28c81a3ea78f356334b6d28d969e953009fae8ece4fe544f2eb466419b successfully fulfilled. Cost is 0.282344694329387405 LINK.Complete response: { requestId: '0xdf22fa28c81a3ea78f356334b6d28d969e953009fae8ece4fe544f2eb466419b', subscriptionId: 2303, totalCostInJuels: 282344694329387405n, diff --git a/src/content/chainlink-functions/tutorials/api-multiple-calls.mdx b/src/content/chainlink-functions/tutorials/api-multiple-calls.mdx index a710ed24165..9ecdabca408 100644 --- a/src/content/chainlink-functions/tutorials/api-multiple-calls.mdx +++ b/src/content/chainlink-functions/tutorials/api-multiple-calls.mdx @@ -87,7 +87,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0x8defda7d48f91efa4f7bfa8e7d99f115a4e1d71882852ee6e91f438542d840ec. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0x8defda7d48f91efa4f7bfa8e7d99f115a4e1d71882852ee6e91f438542d840ec - ✅ Request 0xff18de309a7845ef99b042d008aa3c5e67c51e649b771cbaab7dd96fada66e27 successfully fulfilled. Cost is 0.25590956997723491 LINK.Complete reponse: { + ✅ Request 0xff18de309a7845ef99b042d008aa3c5e67c51e649b771cbaab7dd96fada66e27 successfully fulfilled. Cost is 0.25590956997723491 LINK.Complete response: { requestId: '0xff18de309a7845ef99b042d008aa3c5e67c51e649b771cbaab7dd96fada66e27', subscriptionId: 2303, totalCostInJuels: 255909569977234910n, diff --git a/src/content/chainlink-functions/tutorials/api-post-data.mdx b/src/content/chainlink-functions/tutorials/api-post-data.mdx index 75247fe9fd3..a34101507fa 100644 --- a/src/content/chainlink-functions/tutorials/api-post-data.mdx +++ b/src/content/chainlink-functions/tutorials/api-post-data.mdx @@ -76,7 +76,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0x5a315eeebea90f4828d176906d13dd3133e8a8d9afa912b1f8c34e90e775d081. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0x5a315eeebea90f4828d176906d13dd3133e8a8d9afa912b1f8c34e90e775d081 - ✅ Request 0xc760ee5ca5c73999ca9c4ce426b9d2d44eab4429d3110276e57c445537ad5ddd successfully fulfilled. Cost is 0.257726519296170771 LINK.Complete reponse: { + ✅ Request 0xc760ee5ca5c73999ca9c4ce426b9d2d44eab4429d3110276e57c445537ad5ddd successfully fulfilled. Cost is 0.257726519296170771 LINK.Complete response: { requestId: '0xc760ee5ca5c73999ca9c4ce426b9d2d44eab4429d3110276e57c445537ad5ddd', subscriptionId: 2303, totalCostInJuels: 257726519296170771n, diff --git a/src/content/chainlink-functions/tutorials/api-query-parameters.mdx b/src/content/chainlink-functions/tutorials/api-query-parameters.mdx index 7d8ca784fad..4fb60b3cb66 100644 --- a/src/content/chainlink-functions/tutorials/api-query-parameters.mdx +++ b/src/content/chainlink-functions/tutorials/api-query-parameters.mdx @@ -62,7 +62,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0xbbe473ccc6593b6f3baf30fd66b2329b05a32fe0321a319d09142f4b9ba4547c. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0xbbe473ccc6593b6f3baf30fd66b2329b05a32fe0321a319d09142f4b9ba4547c - ✅ Request 0xe55201188012e3ec198427937f7897729999ab7b287207ff8f0c157a9662e5f0 successfully fulfilled. Cost is 0.249819373001796045 LINK.Complete reponse: { + ✅ Request 0xe55201188012e3ec198427937f7897729999ab7b287207ff8f0c157a9662e5f0 successfully fulfilled. Cost is 0.249819373001796045 LINK.Complete response: { requestId: '0xe55201188012e3ec198427937f7897729999ab7b287207ff8f0c157a9662e5f0', subscriptionId: 2303, totalCostInJuels: 249819373001796045n, diff --git a/src/content/chainlink-functions/tutorials/api-use-secrets-gist.mdx b/src/content/chainlink-functions/tutorials/api-use-secrets-gist.mdx index 7010b5b377f..cafaf9fd717 100644 --- a/src/content/chainlink-functions/tutorials/api-use-secrets-gist.mdx +++ b/src/content/chainlink-functions/tutorials/api-use-secrets-gist.mdx @@ -94,7 +94,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0xe5db77b3994e0c30934dbac779608af0b08eb9ddf57fb121c0f481a95ea9b579. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0xe5db77b3994e0c30934dbac779608af0b08eb9ddf57fb121c0f481a95ea9b579 - ✅ Request 0x37f860fba46af84b84f5ce48efbb7c6ebbfb2ecde5063621f695bbd1c2547975 successfully fulfilled. Cost is 0.237283011969506455 LINK.Complete reponse: { + ✅ Request 0x37f860fba46af84b84f5ce48efbb7c6ebbfb2ecde5063621f695bbd1c2547975 successfully fulfilled. Cost is 0.237283011969506455 LINK.Complete response: { requestId: '0x37f860fba46af84b84f5ce48efbb7c6ebbfb2ecde5063621f695bbd1c2547975', subscriptionId: 2303, totalCostInJuels: 237283011969506455n, diff --git a/src/content/chainlink-functions/tutorials/api-use-secrets-offchain.mdx b/src/content/chainlink-functions/tutorials/api-use-secrets-offchain.mdx index 4c2d3e8b1b6..d5a8b014e89 100644 --- a/src/content/chainlink-functions/tutorials/api-use-secrets-offchain.mdx +++ b/src/content/chainlink-functions/tutorials/api-use-secrets-offchain.mdx @@ -72,7 +72,7 @@ Before you make a request, prepare the secrets file and host it offchain: 1. Follow these [steps](https://docs.aws.amazon.com/AmazonS3/latest/userguide/uploading-an-object-bucket.html) to upload the file `offchain-secrets.json` to your AWS S3 bucket. -1. To make the file publically accessible without authentication: +1. To make the file publicly accessible without authentication: 1. Find the file in the bucket list, and click on it to open the object overview. 1. Click on the _Permissions_ tab to display the _Access control list (ACL)_. @@ -133,7 +133,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0xadc0db0ddea7b9836b86a9c9e008bc97d47e5f92b0dcec9694d3944d0065c789. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0xadc0db0ddea7b9836b86a9c9e008bc97d47e5f92b0dcec9694d3944d0065c789 - ✅ Request 0xb308ca293859dab47d8848578291e687a0d9373274d1451a9c9667dc4bba5fca successfully fulfilled. Cost is 0.260029208488139025 LINK.Complete reponse: { + ✅ Request 0xb308ca293859dab47d8848578291e687a0d9373274d1451a9c9667dc4bba5fca successfully fulfilled. Cost is 0.260029208488139025 LINK.Complete response: { requestId: '0xb308ca293859dab47d8848578291e687a0d9373274d1451a9c9667dc4bba5fca', subscriptionId: 2303, totalCostInJuels: 260029208488139025n, diff --git a/src/content/chainlink-functions/tutorials/api-use-secrets.mdx b/src/content/chainlink-functions/tutorials/api-use-secrets.mdx index a83210b389a..ecd8ebb7bef 100644 --- a/src/content/chainlink-functions/tutorials/api-use-secrets.mdx +++ b/src/content/chainlink-functions/tutorials/api-use-secrets.mdx @@ -82,7 +82,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0xcac39aeea98651f307da185aed387314c453272d185e58b26b3bb399b82a90b6. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0xcac39aeea98651f307da185aed387314c453272d185e58b26b3bb399b82a90b6 - ✅ Request 0xbc09de04f4dd39fa78d4b00b7ab4d2f4a37d8b9a8edf97df5c86061175b9d9c3 successfully fulfilled. Cost is 0.23730142355580769 LINK.Complete reponse: { + ✅ Request 0xbc09de04f4dd39fa78d4b00b7ab4d2f4a37d8b9a8edf97df5c86061175b9d9c3 successfully fulfilled. Cost is 0.23730142355580769 LINK.Complete response: { requestId: '0xbc09de04f4dd39fa78d4b00b7ab4d2f4a37d8b9a8edf97df5c86061175b9d9c3', subscriptionId: 2303, totalCostInJuels: 237301423555807690n, diff --git a/src/content/chainlink-functions/tutorials/encode-request-offchain.mdx b/src/content/chainlink-functions/tutorials/encode-request-offchain.mdx index 913590a80bf..fb7a6e52e48 100644 --- a/src/content/chainlink-functions/tutorials/encode-request-offchain.mdx +++ b/src/content/chainlink-functions/tutorials/encode-request-offchain.mdx @@ -91,7 +91,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0x730a66676cd797b11943635d53af9941c561d90a7088106800d05b4fdb2de189. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0x730a66676cd797b11943635d53af9941c561d90a7088106800d05b4fdb2de189 - ✅ Request 0x8329a6e56461117508885f9eaee338f25095eb0f863d6972877f38c4412c0a29 successfully fulfilled. Cost is 0.236443904180225775 LINK.Complete reponse: { + ✅ Request 0x8329a6e56461117508885f9eaee338f25095eb0f863d6972877f38c4412c0a29 successfully fulfilled. Cost is 0.236443904180225775 LINK.Complete response: { requestId: '0x8329a6e56461117508885f9eaee338f25095eb0f863d6972877f38c4412c0a29', subscriptionId: 2303, totalCostInJuels: 236443904180225775n, diff --git a/src/content/chainlink-functions/tutorials/importing-packages.mdx b/src/content/chainlink-functions/tutorials/importing-packages.mdx index 93f77026fd6..97f184fe5f3 100644 --- a/src/content/chainlink-functions/tutorials/importing-packages.mdx +++ b/src/content/chainlink-functions/tutorials/importing-packages.mdx @@ -14,7 +14,7 @@ This tutorial demonstrates how to import modules and use them with your Function - Each import must be 10 MB or less in size. - Up to 100 imports total are supported. -- Deno supports [ESM compatible NPM imports](https://docs.deno.com/runtime/manual/node/npm_specifiers) and some [standard Node modules](https://docs.deno.com/runtime/manual/node/node_specifiers). See the [Compatability List](https://docs.deno.com/runtime/manual/node/compatibility) for details. +- Deno supports [ESM compatible NPM imports](https://docs.deno.com/runtime/manual/node/npm_specifiers) and some [standard Node modules](https://docs.deno.com/runtime/manual/node/node_specifiers). See the [Compatibility List](https://docs.deno.com/runtime/manual/node/compatibility) for details. - Third-party modules are imported at runtime, so import statements must use asynchronous logic like the following examples: - Importing from `deno.land`: @@ -95,7 +95,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0xa73d895adb28360d1737a695647390a3a7f000368d976135fcfe9c834ee75ed6. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0xa73d895adb28360d1737a695647390a3a7f000368d976135fcfe9c834ee75ed6 - ✅ Request 0x5bac800974596113a3013bf788919a6b3df5ea65ec6238a1c98114a60daff6d2 successfully fulfilled. Cost is 0.236901088749168095 LINK.Complete reponse: { + ✅ Request 0x5bac800974596113a3013bf788919a6b3df5ea65ec6238a1c98114a60daff6d2 successfully fulfilled. Cost is 0.236901088749168095 LINK.Complete response: { requestId: '0x5bac800974596113a3013bf788919a6b3df5ea65ec6238a1c98114a60daff6d2', subscriptionId: 2303, totalCostInJuels: 236901088749168095n, diff --git a/src/content/chainlink-functions/tutorials/simple-computation.mdx b/src/content/chainlink-functions/tutorials/simple-computation.mdx index 08dad2b17d3..fb4db928d06 100644 --- a/src/content/chainlink-functions/tutorials/simple-computation.mdx +++ b/src/content/chainlink-functions/tutorials/simple-computation.mdx @@ -62,7 +62,7 @@ To run the example: ✅ Functions request sent! Transaction hash 0x7df8240d23ef5c951ea73634b2346a459c8cd5b9a0bf76dbe0bb4d912e099b22. Waiting for a response... See your request in the explorer https://sepolia.etherscan.io/tx/0x7df8240d23ef5c951ea73634b2346a459c8cd5b9a0bf76dbe0bb4d912e099b22 - ✅ Request 0x91a72a36a94ddedfc9e7bcfe33aaa13dd5747c4e985d9baa8c0c34175ac6c715 successfully fulfilled. Cost is 0.240613623834519812 LINK.Complete reponse: { + ✅ Request 0x91a72a36a94ddedfc9e7bcfe33aaa13dd5747c4e985d9baa8c0c34175ac6c715 successfully fulfilled. Cost is 0.240613623834519812 LINK.Complete response: { requestId: '0x91a72a36a94ddedfc9e7bcfe33aaa13dd5747c4e985d9baa8c0c34175ac6c715', subscriptionId: 2303, totalCostInJuels: 240613623834519812n, diff --git a/src/content/chainlink-local/build/ccip/hardhat/local-simulator.mdx b/src/content/chainlink-local/build/ccip/hardhat/local-simulator.mdx index 53aa67be357..56564b55398 100644 --- a/src/content/chainlink-local/build/ccip/hardhat/local-simulator.mdx +++ b/src/content/chainlink-local/build/ccip/hardhat/local-simulator.mdx @@ -82,8 +82,8 @@ the sender and receiver accounts. 1. Initialize the [CCIP local simulator](/chainlink-local/api-reference/solidity/ccip/cciplocalsimulator#cciplocalsimulator) contract: ```typescript - const ccipLocalSimualtorFactory = await hre.ethers.getContractFactory("CCIPLocalSimulator") - const ccipLocalSimulator: CCIPLocalSimulator = await ccipLocalSimualtorFactory.deploy() + const ccipLocalSimulatorFactory = await hre.ethers.getContractFactory("CCIPLocalSimulator") + const ccipLocalSimulator: CCIPLocalSimulator = await ccipLocalSimulatorFactory.deploy() ``` 1. Initialize the sender and receiver accounts: diff --git a/src/content/chainlink-nodes/external-initiators/building-external-initiators.mdx b/src/content/chainlink-nodes/external-initiators/building-external-initiators.mdx index 6f598770763..36a349e2126 100644 --- a/src/content/chainlink-nodes/external-initiators/building-external-initiators.mdx +++ b/src/content/chainlink-nodes/external-initiators/building-external-initiators.mdx @@ -47,7 +47,7 @@ External initiators make the same API call, with 2 added headers: These are keys generated when you register your external initiator with your node. -Triggering a run through an external initiator is as simple as making this API call to your node. All jobs with this EI configured will then be kicked off in this way. A simple external initiator in psedo code could look like this: +Triggering a run through an external initiator is as simple as making this API call to your node. All jobs with this EI configured will then be kicked off in this way. A simple external initiator in pseudo code could look like this: ```text while(True): diff --git a/src/content/chainlink-nodes/node-versions.mdx b/src/content/chainlink-nodes/node-versions.mdx index 0b4e722bd6d..3489f0d8566 100644 --- a/src/content/chainlink-nodes/node-versions.mdx +++ b/src/content/chainlink-nodes/node-versions.mdx @@ -1,7 +1,7 @@ --- section: nodeOperator date: Last Modified -title: "Chanlink Node Releases" +title: "Chainlink Node Releases" whatsnext: { "Running a Chainlink Node": "/chainlink-nodes/v1/running-a-chainlink-node" } metadata: title: "Node Versions and Release Notes" diff --git a/src/content/chainlink-nodes/resources/evm-performance-configuration.mdx b/src/content/chainlink-nodes/resources/evm-performance-configuration.mdx index 486567c847c..cd6c8921ee6 100644 --- a/src/content/chainlink-nodes/resources/evm-performance-configuration.mdx +++ b/src/content/chainlink-nodes/resources/evm-performance-configuration.mdx @@ -147,7 +147,7 @@ Before you make any changes to your Chainlink configuration, you must ensure tha Chainlink supports an arbitrary number of keys for any given chain. By default, tasks will round-robin through keys, but you can assign them individually to keys as well. Assigning tasks to keys is the preferred way to improve throughput because increasing the max number of in-flight requests can have complicated effects based on the mempool - conmfigurations of other RPC nodes. If you are unable to distribute transmission load across multiple keys, try the + configurations of other RPC nodes. If you are unable to distribute transmission load across multiple keys, try the following options to increase throughput. diff --git a/src/content/chainlink-nodes/v1/node-config.mdx b/src/content/chainlink-nodes/v1/node-config.mdx index 37f58b37262..904ee9b53ff 100644 --- a/src/content/chainlink-nodes/v1/node-config.mdx +++ b/src/content/chainlink-nodes/v1/node-config.mdx @@ -1237,7 +1237,7 @@ KeyBundleID is a sha256 hexadecimal hash identifier. CaptureEATelemetry = false # Default ``` -CaptureEATelemetry toggles collecting extra information from External Adaptares +CaptureEATelemetry toggles collecting extra information from External Adapters ### CaptureAutomationCustomTelemetry @@ -1378,7 +1378,7 @@ TransmitterAddress is the default sending address to use for OCR. If you have an CaptureEATelemetry = false # Default ``` -CaptureEATelemetry toggles collecting extra information from External Adaptares +CaptureEATelemetry toggles collecting extra information from External Adapters ### TraceLogging @@ -2405,7 +2405,7 @@ CACertFile = 'cert-file' # Example ``` CACertFile is the file path of the TLS certificate used for secure communication with the OTEL Collector. -Required unless InescureConnection is true. +Required unless InsecureConnection is true. ### InsecureConnection diff --git a/src/content/quickstarts/pass-cost-to-end-user.mdx b/src/content/quickstarts/pass-cost-to-end-user.mdx index f10861f4376..c9819958198 100644 --- a/src/content/quickstarts/pass-cost-to-end-user.mdx +++ b/src/content/quickstarts/pass-cost-to-end-user.mdx @@ -172,7 +172,7 @@ At the root of the `vrf-direct-funding-example/` directory, run: make install ``` -This command will install the project dependencies, which include [chainlink](https://github.com/smartcontractkit/chainlink) and [openzepplin-contracts](https://github.com/OpenZeppelin/openzeppelin-contracts) for secure smart contract development. +This command will install the project dependencies, which include [chainlink](https://github.com/smartcontractkit/chainlink) and [openzeppelin-contracts](https://github.com/OpenZeppelin/openzeppelin-contracts) for secure smart contract development. diff --git a/src/content/resources/hackathon-rules-waiver-and-release.mdx b/src/content/resources/hackathon-rules-waiver-and-release.mdx index d24e700350f..0f091cbb1c0 100644 --- a/src/content/resources/hackathon-rules-waiver-and-release.mdx +++ b/src/content/resources/hackathon-rules-waiver-and-release.mdx @@ -39,10 +39,10 @@ If you feel uncomfortable or think there may be a potential violation of the cod ##### **Event Rules & Conditions** 1. The following rules & conditions (the “Rules”) apply to this Chainlink hackathon (the “Event"). By clicking the “I Accept” button, you acknowledge that you have read these Rules, understand them, and agree to be bound as follows: -1. You assume full responsibility for any damage or injury caused by you in your participation in the Event (whether to persons or property, and whether to yourself or others) and release SmartContract Chainlink Limited SEZC (and its affiliates) (“Chainlink”), the Event, the organizers of the Event (the “Organizers”), all sponsors of the Event (“Sponsors”), the Event volunteers and the Event staff, (collectively, the “Releasees”) from any liability therefore. **YOU ARE AWARE THAT YOUR PARTICIPATION IN THE EVENT IS SOLELY AT YOUR OWN RISK, AND THAT THE RELEASE HEREIN IS INTENDED TO REFLECT THAT UNDERSTANDING** +1. You assume full responsibility for any damage or injury caused by you in your participation in the Event (whether to persons or property, and whether to yourself or others) and release SmartContract Chainlink Limited SEZC (and its affiliates) (“Chainlink”), the Event, the organizers of the Event (the “Organizers”), all sponsors of the Event (“Sponsors”), the Event volunteers and the Event staff, (collectively, the “Releases”) from any liability therefore. **YOU ARE AWARE THAT YOUR PARTICIPATION IN THE EVENT IS SOLELY AT YOUR OWN RISK, AND THAT THE RELEASE HEREIN IS INTENDED TO REFLECT THAT UNDERSTANDING** 1. You will own any developments that you create during the Event, and all right, title and interest in those developments, including the intellectual property rights therein, shall belong to you. However, you acknowledge that during the course of the Event, you may obtain access to products, developments, information and other materials belonging to Chainlink, other participants of the Event, the Sponsors and/or other third parties (“Third Party Materials”), and that nothing in this Agreement is deemed to transfer any ownership, right, title or interest in such Third Party Materials to you. Your only rights to the Third Party Materials shall be those expressly granted to you by the owner(s) of the Third Party Materials. Specifically, any APIs or other software provided to you by the Sponsors are subject to the subscription terms and software licenses associated with such APIs or other software. 1. By entering this Event, you represent and warrant that your participation complies with these Rules and that you have sufficient rights to (1) authorize the publication and dissemination of any submission materials and presentations (“Submitted Materials”); (2) allow the Organizers and Sponsors to use and to authorize others to use, publish and disseminate your Submitted Materials. Further, you are entirely responsible for your Submitted Materials, in whole or in part, if: (a) determined to be defamatory, offensive or otherwise inappropriate; (b) determined to violate any laws, rules or regulations; (c) determined to be infringing, or constitute a misappropriation of any intellectual property rights or confidential or proprietary information of any third party; or (d) determined to violate these Rules. Your Submitted Materials must be true and accurate and in compliance with these Rules in all regards. At any time, the Organizers at their sole discretion, reserve the right to remove your Submitted Materials from the Event, in whole or in part, for any violation of these Official Rules. -1. You acknowledge that the Event is intended to be a place where ideas are shared freely, and therefore acknowledge that any information that you share with other participants of the Event, the Sponsors and/or other third parties during the Event is solely at your discretion and risk. If you wish to protect your information, it is solely your responsibility to implement confidentiality and security measures with respect to the persons to whom you are disclosing your information. None of the Releasees shall have any responsibility under this Agreement or by virtue of their participation in the Event with respect to your information. +1. You acknowledge that the Event is intended to be a place where ideas are shared freely, and therefore acknowledge that any information that you share with other participants of the Event, the Sponsors and/or other third parties during the Event is solely at your discretion and risk. If you wish to protect your information, it is solely your responsibility to implement confidentiality and security measures with respect to the persons to whom you are disclosing your information. None of the Releases shall have any responsibility under this Agreement or by virtue of their participation in the Event with respect to your information. 1. You are not be a citizen or resident of any jurisdiction subject to sanctions as enforced by the Office of Foreign Assets Control, including without limitation Burma, Crimea and Sevastopol, Cote d'Ivoire, Cuba, Democratic Republic of Congo, Iran, Iraq, Libya, North Korea, Sudan, Syria, Zimbabwe, and you must not be named by OFAC as a Specially Designated National or Blocked Person which can be found at: [www.treasury.gov](https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx) 1. You acknowledge that the Organizers and Chainlink have the right to reject participants in the Event at their sole discretion. 1. The Organizers have the unrestricted right to use your likeness, image, voice, opinions, and appearance, and also any images of your projects, developments, materials and belongings made at or brought to the Event, captured through video, photographs or other media during the Event for the express purpose of creating promotional material (the “Images”), for the purposes of use in websites, promotional materials, publications and other media of any of the Organizers, whether in print or electronically (the “Materials”). The foregoing right includes permission to copyright, use, re-use, publish, and republish Images in which you may be included, intact or in part, composite or distorted in character or form, without restriction as to changes or transformations, in conjunction with your own or a fictitious name, reproduction in color or otherwise, made through any and all media now or hereafter known; @@ -51,7 +51,7 @@ If you feel uncomfortable or think there may be a potential violation of the cod 1. You relinquish any right that you may have to examine or approve the Materials in which you or your Images may appear or the use to which they may be applied; and 1. You hereby release, discharge and agree to save harmless each and all of the Organizers from any liability by virtue of any blurring, distortion, alteration, optical illusion, or use in composite form of the Images whether intentional or otherwise, that may occur or be produced in the recording of the Images or in any subsequent processing thereof, as well as any publication thereof, including without limitation any claims for libel or invasion of privacy. 1. You agree that the Organizers may share your registration details, LinkedIn/Github profiles, details of your Hackathon submission, and other information obtained from you in the course of, or relating to, the Event with the Sponsors, and acknowledge that such Sponsors may contact you during and after the Event. By agreeing to this document and/or participating in the Event, you are providing your express consent to communications by the Organizers and Sponsors (including email communications, both marketing and informational) respecting the products and services of the Organizers and Sponsors, and future events. -1. For valuable consideration, including permission to take part in the Event, you hereby covenant not to sue, and release, waive, and discharge the Releasees, their owners, officers, agents, affiliates, employees, volunteers, and/or any other person or entity in any way associated with the Event, from liability for any injury to your person or property or death arising out of or related to your participation in the Event, whether caused by an act of negligence of the Releasees or otherwise; and hereby assume full responsibility for any risk of bodily injury, death or property damage arising out of or related to your participation in the Event, whether occurring to you or to any other person or entity for whom you are responsible or with whom you are associated, and whether caused by an act of negligence of the Releasees or otherwise. The foregoing release includes, but is not limited to, any occurrences of personal injury, illness (food-borne or otherwise), and loss of belongings, whether by theft or otherwise. You further agree that this instrument (the terms of which collectively are referred to as the Rules) is intended to be as broad and inclusive as is permitted by the laws of the State of California and that if any portion thereof is held invalid, that portion shall be invalid only to the extent required by law, and the balance shall, notwithstanding, continue in full force and effect. +1. For valuable consideration, including permission to take part in the Event, you hereby covenant not to sue, and release, waive, and discharge the Releases, their owners, officers, agents, affiliates, employees, volunteers, and/or any other person or entity in any way associated with the Event, from liability for any injury to your person or property or death arising out of or related to your participation in the Event, whether caused by an act of negligence of the Releases or otherwise; and hereby assume full responsibility for any risk of bodily injury, death or property damage arising out of or related to your participation in the Event, whether occurring to you or to any other person or entity for whom you are responsible or with whom you are associated, and whether caused by an act of negligence of the Releases or otherwise. The foregoing release includes, but is not limited to, any occurrences of personal injury, illness (food-borne or otherwise), and loss of belongings, whether by theft or otherwise. You further agree that this instrument (the terms of which collectively are referred to as the Rules) is intended to be as broad and inclusive as is permitted by the laws of the State of California and that if any portion thereof is held invalid, that portion shall be invalid only to the extent required by law, and the balance shall, notwithstanding, continue in full force and effect. 1. You agree to indemnify and hold the Organizers and Sponsors (and judges, mentors, volunteers, organizers, Chainlink team administering the Event) and each of their employees, representatives, agents, attorneys, affiliates, directors, employees, officers, managers, and shareholders (the “Indemnified Parties”) harmless from any damage, loss, cost, or expense (including without limitation, attorneys’ fees and costs) incurred in connection with any third-party claim, demand, or action (“Claim”) brought or asserted against any of the Indemnified Parties, alleging facts or circumstances that would constitute a breach of any provision of these Rules by you; arising from, related to, or connected with your entry, Submitted Materials, presentations and participation in any way in any aspect of Event, including receipt of any prize. If you are obligated to provide indemnification pursuant to this provision, the Indemnified Parties may, in their sole discretion, control the disposition of any claim at your sole cost and expense. Without limitation of the foregoing, you may not settle, compromise, or in any other manner dispose of any claim without the Organizers’s express written consent. 1. If selected as a winner of a Chainlink award, your acceptance of the Chainlink award means you agree to the following: 1. You will not disparage Chainlink or its products, services, agents, representatives, directors, officers, shareholders, attorneys, employees, vendors, business partners, affiliates, successors or assigns, or any person acting by, through, under or in concert with any of them, with any written or oral statement. Nothing in this paragraph shall prohibit the winner from providing truthful information in response to a valid subpoena or other legal process; however, the winning participant agrees to provide Company sufficient notice of such to allow Company the opportunity to oppose such subpoena or legal process prior to providing any information (unless expressly prohibited by applicable law). diff --git a/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx b/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx index 00ce0f015f7..5a513d9c2cf 100644 --- a/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx +++ b/src/content/vrf/v2-5/direct-funding/get-a-random-number.mdx @@ -101,7 +101,7 @@ The contract includes the following functions: - `fulfillRandomWords()`: Receives random values and stores them with your contract. -- `getRequestStatus()`: Retrive request details for a given `_requestId`. +- `getRequestStatus()`: Retrieve request details for a given `_requestId`. - `withdrawLink()`: At any time, the owner of the contract can withdraw the outstanding LINK balance from it. diff --git a/src/content/vrf/v2-5/subscription/get-a-random-number.mdx b/src/content/vrf/v2-5/subscription/get-a-random-number.mdx index 828fedcb9c1..b1320ff8437 100644 --- a/src/content/vrf/v2-5/subscription/get-a-random-number.mdx +++ b/src/content/vrf/v2-5/subscription/get-a-random-number.mdx @@ -155,7 +155,7 @@ The contract includes the following functions: - `fulfillRandomWords()`: Receives random values and stores them with your contract. -- `getRequestStatus()`: Retrive request details for a given `_requestId`. +- `getRequestStatus()`: Retrieve request details for a given `_requestId`.