fix: Some typos (#2206)

* fix: Some typos * Update docs/2.build/1.chain-abstraction/wallet.md --------- Co-authored-by: Damián Parrino <[email protected]>
near · Aug 12, 2024 · f0a9fb8 · f0a9fb8
1 parent 2a91c1b
commit f0a9fb8
Show file tree

Hide file tree

Showing 20 changed files with 28 additions and 29 deletions.
diff --git a/docs/1.concepts/3.advanced/indexers.md b/docs/1.concepts/3.advanced/indexers.md
@@ -88,4 +88,4 @@ We hope this article gives you an understanding of the Indexer concept. Also, we
 ## What's next?
 We encourage you to learn more about the [Lake Indexer project](/build/data-infrastructure/lake-framework/near-lake). Please, proceed to [Tutorials](/build/data-infrastructure/lake-framework/near-lake-state-changes-indexer) section to learn how to build an indexer on practice.
 
-Alternatively, there are a few other third-party indexers that are tightly integrated with the NEAR ecosystem. You can review all of your data sourcing options (including The Graph, Pagoda, Pipespeak, and SubQuery) under [data tools](/concepts/data-flow/data-storage#data-tools).
+Alternatively, there are a few other third-party indexers that are tightly integrated with the NEAR ecosystem. You can review all of your data sourcing options (including The Graph, Pagoda, Pikespeak, and SubQuery) under [data tools](/concepts/data-flow/data-storage#data-tools).
diff --git a/docs/1.concepts/web3/blockchain.md b/docs/1.concepts/web3/blockchain.md
@@ -153,7 +153,7 @@ There are a lot of blockchains out there and it might be hard to choose the most
 
 Historically, the first blockchain to introduce smart contracts was Ethereum. However, as the number of users grew, transaction speed and cost skyrocketed, and it became apparent that it couldn't handle the demand. So, a number of [scaling solutions](https://ethereum.org/en/developers/docs/scaling/) appeared - [layer 2 chains](https://ethereum.org/en/developers/docs/scaling/#layer-2-scaling), [sidechains](https://ethereum.org/en/developers/docs/scaling/sidechains/), and [plasma chains](https://ethereum.org/en/developers/docs/scaling/plasma/). However, they all use some kind of workarounds with their own unique drawbacks. Ethereum tries to fix the core problem and redesign its network - like switching to a Proof-of-stake consensus, which is ongoing for quite a long time, but exact timeline when all of the problems will be fixed is very unclear.
 
-Meanwhile, a new generation of blockchains started to appear. They learned from the Etherium mistakes, and designed them from ground-up to be fast, cheap and scalable. 
+Meanwhile, a new generation of blockchains started to appear. They learned from the Ethereum mistakes, and designed them from ground-up to be fast, cheap and scalable. 
 Choosing the right one is by no means an easy task, but for us we found the [NEAR](https://near.org/) blockchain to be an ideal solution, because of the following properties:
 - Transactions are cheap and very fast.
 - Designed to be extremely scalable from the beginning. This means we can count that transaction cost and speed will remain stable in the future.

diff --git a/docs/1.concepts/web3/near.md b/docs/1.concepts/web3/near.md
@@ -148,7 +148,7 @@ As an alternative to building your own indexer with a database and an API server
 
 By now, we should be familiar with necessary concepts to start developing WEB 3.0 applications, so let’s explore the development tools available.
 
-First of all, we need a development and testing environment. Of course, we could theoraticaly perform development and testing on the main blockchain network, but this would not be cheap. For this reason, NEAR provides [several networks](../../1.concepts/basics/networks.md) that can be used during development:
+First of all, we need a development and testing environment. Of course, we could theoretically perform development and testing on the main blockchain network, but this would not be cheap. For this reason, NEAR provides [several networks](../../1.concepts/basics/networks.md) that can be used during development:
 - testnet - public NEAR network which is identical to mainnet and can be used for free.
 - localnet - you can deploy your personal NEAR network on your own environment. Because it’s owned by you, data and code can be kept private during development. More info on how you can run your own node can be [found here](https://near-nodes.io/validator/running-a-node). Alternatively, you can bootstrap an entire testing infrastructure in Docker on your local machine using Kurtosis - [guide is here](../../2.build/2.smart-contracts/testing/kurtosis-localnet.md).
 - workspaces - you can start your own local network to perform e2e testing. More info [here](../../2.build/2.smart-contracts/testing/integration-test.md).

diff --git a/docs/1.concepts/web3/nfts.md b/docs/1.concepts/web3/nfts.md
@@ -325,7 +325,7 @@ In the blockchain world, creation of new NFTs is usually called minting. And as
 
 
 
-* Users can mint them directly. This can be done by either allowing creation of NFTs from scratch, or by using more complex processes, like breeding or upgrading. The most famous example of such process is breeding in [CrytoKitties](https://www.cryptokitties.co/) game - new NFTs are created by combining existing ones. With this approach users usually have to pay to cover the storage and gas cost of NFTs creation.
+* Users can mint them directly. This can be done by either allowing creation of NFTs from scratch, or by using more complex processes, like breeding or upgrading. The most famous example of such process is breeding in [CryptoKitties](https://www.cryptokitties.co/) game - new NFTs are created by combining existing ones. With this approach users usually have to pay to cover the storage and gas cost of NFTs creation.
 * NFTs can be distributed by the developer to a set of users - it is usually called [NFTs airdrop](https://www.investopedia.com/terms/a/airdrop-cryptocurrency.asp). Most often this is used as a marketing strategy to kickstart NFTs usage in applications. Storage and gas costs in this case are covered by developers.
 * NFTs can be bought on a market or obtained from the lootbox. Depending on an exact strategy, costs can either be paid by a user or by developer. Also, in this case NFTs sometimes can be minted on-demand, to avoid paying upfront costs.
 
@@ -516,7 +516,7 @@ Implementing an own Marketplace contract is more involved since there is no stan
 * [Basic marketplace example](../../3.tutorials/nfts/8-marketplace.md)
 * [Paras ](https://paras.id/)marketplace contract - [source](https://github.com/ParasHQ/paras-marketplace-contract/tree/master/paras-marketplace-contract/src). 
 
-As for third-party solutions, the most complete one is [Mintibase](https://www.mintbase.io/), which provides a full suite of components for NFTs integration - including contracts, indexer, API and a web client:
+As for third-party solutions, the most complete one is [Mintbase](https://www.mintbase.io/), which provides a full suite of components for NFTs integration - including contracts, indexer, API and a web client:
 
 
 

diff --git a/docs/2.build/1.chain-abstraction/fastauth-sdk.md b/docs/2.build/1.chain-abstraction/fastauth-sdk.md
@@ -75,7 +75,7 @@ service cloud.firestore {
 - Press the gear button next to "Project Overview", and go to "Project settings"
 - Under "Your apps", click on the `</>` button
 - Set the app nickname as `issuer-gcp` and hit "Register app"
-- You should see the code needed for initilization and authentication of Firestore, such as:
+- You should see the code needed for initialization and authentication of Firestore, such as:
 ```js
 // Import the functions you need from the SDKs you need
 import { initializeApp } from "firebase/app";
@@ -253,7 +253,7 @@ const onCLick = () => selector.then((selector: any) => selector.wallet('fast-aut
         }),);
 ```
 
-Wehenever the user tries to login, call `onClick`.
+Whenever the user tries to login, call `onClick`.
 
 ### Getting added to the MPC recovery service
 

diff --git a/docs/2.build/1.chain-abstraction/meta-transactions.md b/docs/2.build/1.chain-abstraction/meta-transactions.md
@@ -86,7 +86,7 @@ In this method we are creating an arbitrary smart contract call, instantiating a
 
 As mentioned in the above note in order to be able to relay on the client side it's necessary to have access to signing transactions directly on the client. Luckily leveraging the near biometric library it's possible to do so in a non custodial way.
 
-By calling this method and passing in the URL for the account creation endpoint (mentioned in the server section) as well as the `accoundId` everything is handled under the hood to successfully create an account.
+By calling this method and passing in the URL for the account creation endpoint (mentioned in the server section) as well as the `accountId` everything is handled under the hood to successfully create an account.
 
 <Github language='typescript' url='https://github.com/SurgeCode/near-relay/blob/main/example/src/app/page.tsx' start='17' end='23'/>
 

diff --git a/docs/2.build/1.chain-abstraction/wallet.md b/docs/2.build/1.chain-abstraction/wallet.md
@@ -10,7 +10,7 @@ You'll also learn how to ensure that a signature on one chain is not used to tak
 
 ### Key derivation
 
-When signing using [chain signatures](./chain-signatures.md) each account has an unlimited number of keys. Each key's public key is derived from the account name and the key extension which is an arbitrary string. 
+When signing using [chain signatures](./chain-signatures/chain-signatures.md) each account has an unlimited number of keys. Each key's public key is derived from the account name and the key extension which is an arbitrary string.
 
 User's keys can be described as follow:
 
@@ -94,7 +94,7 @@ In the following examples, the messages are coming from the user's wallet fronte
 - [Using a personal Bitcoin key](#using-a-personal-bitcoin-key)
 - [Using a personal EVM key to sign a Binance transaction](#using-a-personal-evm-key-to-sign-a-binance-transaction)
 - [Using an untyped domain key](#using-an-untyped-domain-key)
-- [Using another domains Bitcoin key](#using-another-domains-bitcoin-key)
+- [Using another domain's Bitcoin key](#using-another-domains-bitcoin-key)
 
 :::tip
 Wallet developers should follow this user flow format.

diff --git a/docs/2.build/2.smart-contracts/testing/kurtosis-localnet.md b/docs/2.build/2.smart-contracts/testing/kurtosis-localnet.md
@@ -622,9 +622,9 @@ Once you've logged in, you can sign a message with an optional donation.
 
 ---
 
-## Managing NEAR Pacakages
+## Managing NEAR Packages
 
-The Kurtosis NEAR Pacakages you create will continue to run on your local machine for as long as your Docker engine is running. This package runs inside of a Kurtosis "enclave" which is an environment isolated from both your computer and other enclaves. In practice, this means that you can have multiple independent local NEAR clusters running on your machine simply by rerunning the script we executed from the [setup instructions](#setup).
+The Kurtosis NEAR Packages you create will continue to run on your local machine for as long as your Docker engine is running. This package runs inside of a Kurtosis "enclave" which is an environment isolated from both your computer and other enclaves. In practice, this means that you can have multiple independent local NEAR clusters running on your machine simply by rerunning the script we executed from the [setup instructions](#setup).
 
 ### View Package Status
 

diff --git a/docs/2.build/5.primitives/ft.md b/docs/2.build/5.primitives/ft.md
@@ -33,7 +33,7 @@ import CLICreateToken from "./ft/near-cli/create.md"
 import SmartContractSendToken from "./ft/smart-contract/send.md"
 import SmartContractAttachTokenToCall from "./ft/smart-contract/attach-to-call.md"
 
-Besides the native NEAR token, NEAR accounts have access to a [multitude of tokens](https://guide.ref.finance/developers-1/cli-trading#query-whitelisted-tokens) to use thoughtout the ecosystem. Moreover, it is even possible for users to create their own fungible tokens.
+Besides the native NEAR token, NEAR accounts have access to a [multitude of tokens](https://guide.ref.finance/developers-1/cli-trading#query-whitelisted-tokens) to use throughout the ecosystem. Moreover, it is even possible for users to create their own fungible tokens.
 
 In contrast with the NEAR native token, fungible token (FT) are **not stored** in the user's account. In fact, each FT lives in **their own contract** which is in charge of doing **bookkeeping**. This is, the contract keeps track of how many tokens each user has, and handles transfers internally.
 

diff --git a/docs/2.build/6.data-infrastructure/lake-data-structures/state_change.mdx b/docs/2.build/6.data-infrastructure/lake-data-structures/state_change.mdx
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 
 ## Definition
 
-This entitiy from `nearcore` describes how account's state has changed and the reason
+This entity from `nearcore` describes how account's state has changed and the reason
 
 ## `StateChangeWithCauseView`
 
@@ -101,4 +101,3 @@ export type StateChange = {
 
   </TabItem>
 </Tabs>
-
diff --git a/docs/2.build/6.data-infrastructure/lake-data-structures/transaction.mdx b/docs/2.build/6.data-infrastructure/lake-data-structures/transaction.mdx
@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 
 ## Definition
 
-Transaction is the main way of interraction between a user and a blockchain. Transaction contains:
+Transaction is the main way of interaction between a user and a blockchain. Transaction contains:
 - Signer account ID
 - Receiver account ID
 - Actions

diff --git a/....build/6.data-infrastructure/lake-framework/migrating-to-near-lake-framework.md b/....build/6.data-infrastructure/lake-framework/migrating-to-near-lake-framework.md
@@ -499,7 +499,7 @@ We are posting the complete diffs for the reference
 -    /// Specify a custom download URL for the genesis file.
 -    #[clap(long)]
 -    pub download_genesis_url: Option<String>,
--    /// Download the verified NEAR config file automtically.
+-    /// Download the verified NEAR config file automatically.
 -    #[clap(long)]
 -    pub download_config: bool,
 -    /// Specify a custom download URL for the config file.

diff --git a/docs/2.build/6.data-infrastructure/lake-framework/running-near-lake/credentials.md b/docs/2.build/6.data-infrastructure/lake-framework/running-near-lake/credentials.md
@@ -30,7 +30,7 @@ aws_secret_access_key=<YOUR_AWS_ACCESS_KEY>
 
 [AWS docs: Configuration and credential file settings](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html)
 
-#### Environment varibales
+#### Environment variables
 
 Alternatively, you can provide your AWS credentials via environment variables with constant names:
 

diff --git a/docs/4.tools/cli-rs.md b/docs/4.tools/cli-rs.md
@@ -66,7 +66,7 @@ You'll get redirected to `wallet.testnet.near.org`. Once there, grant authorizat
 
 If you're on Mac you'll have the option to use the [Mac Keychain](https://support.apple.com/guide/keychain-access/what-is-keychain-access-kyca1083/mac) option.
 
-Either storage option is fine. Using the legacy storage option will save a file in your root directory in a hidden folder called `./near-credentials`. This storage option is compatable with the `near-cli` tool (a cli tool without the guided prompts but similar functionality).
+Either storage option is fine. Using the legacy storage option will save a file in your root directory in a hidden folder called `./near-credentials`. This storage option is compatible with the `near-cli` tool (a cli tool without the guided prompts but similar functionality).
 
 **Good Job!**
 Now you can use `near-cli-rs` to it's full capacity.
@@ -129,7 +129,7 @@ Operate Transactions
 | Option                 | Description                 |
 | ---------------------- | --------------------------- |
 | `view-status`          | View a transaction status   |
-| `construct-tansaction` | Construct a new transaction |
+| `construct-transaction` | Construct a new transaction |
 
 ### Config
 

diff --git a/docs/4.tools/near-api-js/quick-reference.md b/docs/4.tools/near-api-js/quick-reference.md
@@ -245,7 +245,7 @@ const provider = new FailoverRpcProvider(jsonProviders);
 await connect({
   networkId: 'mainnet',
   provider: provider,
-  // this isn't used if `provider` is specified, but is still required for backward compativility
+  // this isn't used if `provider` is specified, but is still required for backward compatibility
   nodeUrl: 'https://rpc.mainnet.near.org',
 });
 ```

diff --git a/docs/pagoda/alerts/setup.md b/docs/pagoda/alerts/setup.md
@@ -42,7 +42,7 @@ Follow the steps above to begin setting-up telegram alerts. When selecting the d
 
 ### Private Message Alerts
 
-1. On the device that is logged into the telegram aclick "Open Telegram" or scan the QR code. 
+1. On the device that is logged into the telegram click "Open Telegram" or scan the QR code. 
 
    <img width="60%" src="/docs/pagoda/setup8.png" />
 

diff --git a/docs/pagoda/alerts/webhooks.md b/docs/pagoda/alerts/webhooks.md
@@ -140,7 +140,7 @@ copy that entire line and head on over to console.pagoda.co
 
 ## Step 5: Integrating Webhook into Pagoda Console
 
-Once at console.pagoda.co, you should be greeted by the log-in page. Select the Non-funcable Token (NFT) project to start exploring the NFT contract
+Once at console.pagoda.co, you should be greeted by the log-in page. Select the Non-fungible Token (NFT) project to start exploring the NFT contract
 
 <img width="60%" src="/docs/pagoda/webhook19.png" />
 
@@ -181,12 +181,12 @@ But for now, we'll keep it easy and select any Successful Action.
 We're almost done! Under destination select webhooks. Now that webhook we created earlier go ahead and copy and paste it into here. Then hit "Create"
 
 :::tip
-Don't forget to remove the `{}` around the name of your event! `ifttt.com/trigger/...`, not `ifftt.com/{trigger}/...`
+Don't forget to remove the `{}` around the name of your event! `ifttt.com/trigger/...`, not `ifttt.com/{trigger}/...`
 :::
 
 <img width="60%" src="/docs/pagoda/webhook26.png" />
 
-Remember to hit the "+ Create Alert" button on this page... 
+Remember to hit the "+ Create Alert" button on this page...
 
 <img width="60%" src="/docs/pagoda/webhook27.png" />
 
@@ -210,6 +210,6 @@ Select the `new_default_metadata` function (we are choosing this one because we
 
 And that's it! You've just triggered something in the real world with an event that happened on the NEAR Blockchain. Hopefully this inspires you to create your own webhook using IFTTT and the Pagoda Console. 
 
-We'd love to see what you create! Tag [@PagodaPlatform](https://twitter.com/PagodaPlatform) on Twitter with a novel implementation of a webhhook and trigger and we might retweet it. 
+We'd love to see what you create! Tag [@PagodaPlatform](https://twitter.com/PagodaPlatform) on Twitter with a novel implementation of a webhook and trigger and we might retweet it. 
 
 Happy hacking!
diff --git a/docs/pagoda/rpc/intro.md b/docs/pagoda/rpc/intro.md
@@ -19,7 +19,7 @@ The Pagoda RPC provides you with instant access to maintenance free, scalable NE
 
 Developers can interact with on-chain data and send different types of transactions to the network by utilizing the RPC endpoints.
 
-In addition to the powerful node infrastructure, we also created the Pagoda RPC Stats page so that you can have visibility into your RPC usage and performances and take control of your project from the infrastructure level. What’s more? You can subscribe to the alerts from our Status page so that you can follow the health of Pagoda RPC real time. All accesible via [Pagoda Console](https://console.pagoda.co/).
+In addition to the powerful node infrastructure, we also created the Pagoda RPC Stats page so that you can have visibility into your RPC usage and performances and take control of your project from the infrastructure level. What’s more? You can subscribe to the alerts from our Status page so that you can follow the health of Pagoda RPC real time. All accessible via [Pagoda Console](https://console.pagoda.co/).
 
 ## Setup
 

diff --git a/docs/pagoda/rpc/setup.md b/docs/pagoda/rpc/setup.md
@@ -37,7 +37,7 @@ With a dedicated API key, developers are able to:
 
 -    Access higher request throughput and increased concurrent requests
 -    Query data from [Enhanced APIs](api.md), gaining access to free processed data for NFT, FT and NEAR balances, ownership, and metadata
--    Utlize dedicated, individualized usage metrics
+-    Utilize dedicated, individualized usage metrics
 
 ### Test your API keys
 

diff --git a/docs/pagoda/rpc/stats.md b/docs/pagoda/rpc/stats.md
@@ -28,7 +28,7 @@ Aggregated key metrics available at the top of the dashboard are
 
 ## Set a Time Period
 
-Data is sent with UTC time to the browser and the browser adjusts to the user’s timezon.
+Data is sent with UTC time to the browser and the browser adjusts to the user’s timezone.
 
 -    Last 15 Minutes is the last complete 15 minutes. This updates every few seconds.
 -    Last 1 Hour is the last fully completed hour; from 00 to 59 minutes and 59 seconds.