From cad680faa76cd50a22675d4eeb509ec1759a110f Mon Sep 17 00:00:00 2001 From: PiVortex Date: Wed, 18 Dec 2024 11:01:10 +0000 Subject: [PATCH] fix links --- docs/2.build/2.smart-contracts/release/upgrade.md | 4 ++-- docs/2.build/4.web3-apps/frontend.md | 4 ++-- docs/5.api/rpc/providers.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/2.build/2.smart-contracts/release/upgrade.md b/docs/2.build/2.smart-contracts/release/upgrade.md index 28b3db0c8b2..ece58a4914a 100644 --- a/docs/2.build/2.smart-contracts/release/upgrade.md +++ b/docs/2.build/2.smart-contracts/release/upgrade.md @@ -11,8 +11,8 @@ allowing the code to be changed. Contract's can be updated in two ways: -1. **Through tools** such as [NEAR CLI](../../../4.tools/cli.md) or - [near-api-js](../../../4.tools/near-api-js/quick-reference.md) (if you hold +1. **Through tools** such as [NEAR CLI](../../../4.tools/cli.md) or the + [NEAR API](../../../4.tools/near-api.md) (if you hold the account's [full access key](../../../1.concepts/protocol/access-keys.md)). 2. **Programmatically**, by implementing a method that diff --git a/docs/2.build/4.web3-apps/frontend.md b/docs/2.build/4.web3-apps/frontend.md index b4e27a0ea33..2fae10c11cc 100644 --- a/docs/2.build/4.web3-apps/frontend.md +++ b/docs/2.build/4.web3-apps/frontend.md @@ -29,12 +29,12 @@ While your user interface layer will remain centralized, the backend layer—inc When building a frontend that can connect with the NEAR blockchain using standard web2 tooling will require you to import two dependencies: -- [NEAR API JS](../../4.tools/near-api-js/quick-reference.md) - A JavaScript API tool that allows frontend clients the ability to view and retrieve data directly from the blockchain. +- [NEAR API JS](../../4.tools/near-api.md) - A JavaScript API tool that allows frontend clients the ability to view and retrieve data directly from the blockchain. - [Wallet Selector](../../4.tools/wallet-selector.md) - Wallet integration tool allowing developers to choose which wallets are supported and allows users to choose which wallet they would like to connect with. :::tip -[Checkout this article](integrate-contracts.md) to learn how to integrate smart contracts to your frontend, using [Wallet Selector](../../4.tools/wallet-selector.md) and [NEAR API JS](../../4.tools/near-api-js/quick-reference.md). +[Checkout this article](integrate-contracts.md) to learn how to integrate smart contracts to your frontend, using [Wallet Selector](../../4.tools/wallet-selector.md) and [NEAR API JS](../../4.tools/near-api.md). ::: diff --git a/docs/5.api/rpc/providers.md b/docs/5.api/rpc/providers.md index 59f8b6e6ca2..4b00449033e 100644 --- a/docs/5.api/rpc/providers.md +++ b/docs/5.api/rpc/providers.md @@ -45,7 +45,7 @@ If you want to use a custom RPC provider with NEAR Wallet Selector, [check this ## RPC Failover -In `near-api-js` you can use [`FailoverRpcProvider`](../../4.tools/near-api-js/quick-reference.md#rpc-failover) to automatically switch RPC providers when one provider is experiencing downtime, or implement an RPC selection widget that allows users to add their own RPC provider. +In `near-api-js` you can use [`FailoverRpcProvider`](../../4.tools/near-api.md#rpc-failover) to automatically switch RPC providers when one provider is experiencing downtime, or implement an RPC selection widget that allows users to add their own RPC provider. As a user, if a dApp or wallet doesn't support RPC failover and the primary provider is down, you can use an RPC Selector browser extension to redirect all requests to an RPC provider of your choice.