Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(docs): typos #1853

Merged
merged 2 commits into from
Aug 10, 2023
Merged

fix(docs): typos #1853

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
27aae96
fix: typos
dcroote Aug 10, 2023
035e4ac
fixup! revert upgradeability
dcroote Aug 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/lazy-tables-lick.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
6 changes: 2 additions & 4 deletions packages/airnode-examples/integrations/failing-example/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,7 @@
# Failing example integration

This is a very basic example showcasing `config.json` and `secrets.env` (which is automatically generated for you with
one of our scripts). Although most of the data is same as in the Coingecko example, the endpoint URL is intentionally
invalid, causing the request to fail everytime one tries to make it. This is to show what the behaviour of Airnode is
like in case of failure.
This integration is similar to the coingecko integration, but the endpoint URL is intentionally invalid. This causes
requests to fail and therefore serves to demonstrate Airnode behaviour in the case of failure.

For more information about how the Airnode is configured, refer to the
[docs](https://docs.api3.org/reference/airnode/latest/understand/configuring.html).
2 changes: 1 addition & 1 deletion packages/airnode-operation/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ yarn run dev:eth-requests

A deployment file (`evm-dev.json`) must be present in the deployments folder before running this script.

Airnode can now be invoked which will cause these requests to be actioned.
Airnode can now be invoked which will cause these requests to be processed.

### Configuration

Expand Down
2 changes: 1 addition & 1 deletion packages/airnode-protocol/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -348,7 +348,7 @@ the request by deriving the sponsor wallet address itself.
For requesters to be able to access an airnode endpoint , they need to be whitelisted on the airnode endpoint via the
`RequesterAuthorizerWithManager` or the `RequesterAuthorizerWithAirnode`. The former is managed by the API3DAO for all
airnodes and the latter is managed by each airnode individually. The token locking contract `AirnodeTokenLock.sol` has
the indefinite whitelister role of the `RequesterAuthorizerWithManager`, this allows this contract to indefinently
the indefinite whitelister role of the `RequesterAuthorizerWithManager`, this allows this contract to indefinitely
whitelist a requester. Requesters who want to be whitelisted need to lock in API3 tokens for each endpoint they wish to
access. Unlocking these locked tokens revokes the whitelisting.

Expand Down