diff --git a/docs/explore/airnode/unlocking-real-world-data.md b/docs/explore/airnode/unlocking-real-world-data.md index 1b311039..8bb6019f 100644 --- a/docs/explore/airnode/unlocking-real-world-data.md +++ b/docs/explore/airnode/unlocking-real-world-data.md @@ -114,7 +114,7 @@ smart contract that calls an Airnode. As an example see the `myContract.sol` contract in the diagram within the -[dAPP Developers Overview](/reference/airnode/latest/developers/) doc, it is a +[dApp Developers Overview](/reference/airnode/latest/developers/) doc, it is a requester. ### What is a Sponsor? diff --git a/docs/explore/dapis/OEV.md b/docs/explore/dapis/OEV.md index aac25e80..4cc30629 100644 --- a/docs/explore/dapis/OEV.md +++ b/docs/explore/dapis/OEV.md @@ -40,7 +40,7 @@ be familiar with from Flashbots and MEV-Boost. Instead of overpaying for liquidations with a fixed incentive, that during large liquidation opportunities can be much much higher than it needs to be, a sealed bid auction hosted at the oracle can minimize the value being paid out and -return most of it back to the dapp. The liquidations will also be able to occur +return most of it back to the dApp. The liquidations will also be able to occur in a more timely manner because you do not have to wait for a deviation threshold to trigger oracle updates, creating a lower latency and more robust liquidation process. @@ -55,7 +55,7 @@ the arbitrage opportunities and returning the corresponding value to dApps. More accurate data and value capture from the auction can be used to increase profitability and sustainability of liquidity provision, allowing for a more optimal market making protocol for apps that use oracles. Better market making -from a dapps LPs creates a flywheel effect of drawing more liquidity to the +from a dApps LPs creates a flywheel effect of drawing more liquidity to the application while being able to lower fees and list more assets, which then attracts more users and volume. diff --git a/docs/guides/airnode/deploy-airnode/generate-config-chainapi/index.md b/docs/guides/airnode/deploy-airnode/generate-config-chainapi/index.md index 17ecabac..983726fd 100644 --- a/docs/guides/airnode/deploy-airnode/generate-config-chainapi/index.md +++ b/docs/guides/airnode/deploy-airnode/generate-config-chainapi/index.md @@ -28,7 +28,7 @@ Using ChainAPI, API providers can configure and deploy an Airnode which links their API data to several blockchains. ChainAPI can connect almost any API, whether open or authenticated, to Airnode. -Airnode then queries your API operations to be consumed by EVM on-chain dAPPs, +Airnode then queries your API operations to be consumed by EVM on-chain dApps, by using the request/response protocol. To get started, go to [ChainAPI](https://chainapi.com/) and login using diff --git a/docs/reference/oev-network/searchers/arguments.md b/docs/reference/oev-network/searchers/arguments.md index 1a4bc1b4..225dc14b 100644 --- a/docs/reference/oev-network/searchers/arguments.md +++ b/docs/reference/oev-network/searchers/arguments.md @@ -18,7 +18,7 @@ tags: ### Proxy Address -dAPPs use a proxy address to read the latest data point from a dAPI. The +dApps use a proxy address to read the latest data point from a dAPI. The [API3 Market](https://market.api3.org) lists the proxy addresses for dAPIs across all chains. diff --git a/docs/reference/oev-network/sidebar.js b/docs/reference/oev-network/sidebar.js index 8ee2b3c1..79cf8c82 100644 --- a/docs/reference/oev-network/sidebar.js +++ b/docs/reference/oev-network/sidebar.js @@ -49,7 +49,7 @@ module.exports = [ ], }, { - text: 'dAPPs', + text: 'dApps', collapsed: false, items: [ {