Skip to content

Commit 91fbe49

Browse files
committed
chore: fix typos
1 parent e815009 commit 91fbe49

32 files changed

+67
-67
lines changed

docs/get-started/air-gap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ image: /img/og/og-security-air-gap-environment.png
1010

1111
Developers & Cardano stake pool operators generally need an air gap environment in which to work with payment keys, stake pool keys and other cryptocurrency resources that offer high-value targets for hackers.
1212

13-
Some specialised hardware (e.g. hardware wallets) may also perform this function. If you believe you have such a device, please be certain that it offers isolation features for your stake pool or development *and* that you feel secure entrusting your assets to those who have implemented these features.
13+
Some specialized hardware (e.g. hardware wallets) may also perform this function. If you believe you have such a device, please be certain that it offers isolation features for your stake pool or development *and* that you feel secure entrusting your assets to those who have implemented these features.
1414

1515
Otherwise, generally **you need a second computer** to create this air-gapped environment, and the rest of this guide is to help you do that.
1616

docs/get-started/blockfrost/open-source.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Blockfrost [backend](https://github.com/blockfrost/blockfrost-backend-ryo), SDKs
1212

1313
Source code of the Blockfrost backend is hosted on Github, in the [blockfrost-ryo-backend](https://github.com/blockfrost/blockfrost-backend-ryo) repository.
1414

15-
To build it, you need to follow the instructuion specified in the [README](https://github.com/blockfrost/blockfrost-backend-ryo#blockfrostio-backend-service) of the repository or you can even use pre-built Docker images:
15+
To build it, you need to follow the instructions specified in the [README](https://github.com/blockfrost/blockfrost-backend-ryo#blockfrostio-backend-service) of the repository or you can even use pre-built Docker images:
1616

1717
```bash
1818
docker run --rm \
@@ -25,7 +25,7 @@ docker run --rm \
2525

2626
# OpenAPI Specification
2727

28-
The OpenAPI specification is open-source and is itended to serve as a good practice for API built on Cardano. The [source code](https://github.com/blockfrost/openapi) is hosted on Github too. Current version is rendered and available at [docs.blockfrost.io](https://docs.blockfrost.io/).
28+
The OpenAPI specification is open-source and is intended to serve as a good practice for API built on Cardano. The [source code](https://github.com/blockfrost/openapi) is hosted on Github too. Current version is rendered and available at [docs.blockfrost.io](https://docs.blockfrost.io/).
2929

3030
# SDKs and other tooling
3131

docs/get-started/cardano-serialization-lib/create-react-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ image: /img/og/og-getstarted-serialization-lib.png
1111
`cardano-wallet-connector` is a Create React App boilerplate code that includes examples of how to use the Serialization-Lib to connect
1212
to different Cardano Web wallets and send transactions. This lets developers who are familiar with React JS to get started
1313
quickly with Cardano. The boilerplate code includes examples of how to execute simple transaction of sending someone ADA
14-
and also how to interact with Plutus scripts (locking and redeeming assests from scripts). A developer familiar with React JS can clone
14+
and also how to interact with Plutus scripts (locking and redeeming assets from scripts). A developer familiar with React JS can clone
1515
the GitHub repo and start building DApps
1616

1717
GitHub: [cardano-wallet-connector](https://github.com/dynamicstrategies/cardano-wallet-connector)
@@ -35,8 +35,8 @@ GitHub: [cardano-wallet-connector](https://github.com/dynamicstrategies/cardano-
3535

3636
## Introduction
3737
React JS is by far the most popular front-end framework and continues to grow fast, judging by the number of
38-
Stackoverflow questions when compared to other frameworks such as Angular, Vue and Svetle ([source](https://gist.github.com/tkrotoff/b1caa4c3a185629299ec234d2314e190)).
39-
It is also well documented, sothat a beginner with some Javascript knowledge can pick-it-up,
38+
Stackoverflow questions when compared to other frameworks such as Angular, Vue and Svelte ([source](https://gist.github.com/tkrotoff/b1caa4c3a185629299ec234d2314e190)).
39+
It is also well documented, so that a beginner with some Javascript knowledge can pick it up,
4040
and powerful enough that more sophisticated full stack frameworks such as Next JS incorporate it.
4141

4242
A Create React App is the command that any new application is created with in React JS and anyone who has used this framework before

docs/get-started/cardano-wallet-js.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -799,7 +799,7 @@ you'll need to install stak >= 1.9.3
799799
you can find it here: https://docs.haskellstack.org/en/stable/README/.
800800
You may need to install the libsodium-dev, libghc-hsopenssl-dev, gmp, sqlite and systemd development libraries for the build to succeed.
801801

802-
Also you will need `cardano-node` and `cardano-cli` binaries availables on your PATH.
802+
Also you will need `cardano-node` and `cardano-cli` binaries available on your PATH.
803803

804804
The setup steps are quite simple:
805805
clone: `cardano-wallet`

docs/get-started/cardanosharp-wallet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ Lets assume the following...
168168
### Build Transaction Body
169169

170170
```cs
171-
// Generate the Recieving Address
171+
// Generate the Receiving Address
172172
Address paymentAddr = addressService.GetAddress(
173173
paymentNode.Derive(1).PublicKey,
174174
stakingNode.PublicKey,

docs/get-started/cscli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ image: /img/og/og-getstarted-cscli.png
77
---
88

99
`cscli` is a lightweight cross-platform CLI tool for Cardano supporting the following features out of the box:
10-
- Building and serialising wallet primitives (i.e. recovery-phrases, keys, addresses and transactions)
10+
- Building and serializing wallet primitives (i.e. recovery-phrases, keys, addresses and transactions)
1111
- Live querying of accounts, addresses, transactions and native assets across both Testnet and Mainnet networks
1212
- Submitting transactions to the Testnet or Mainnet network
1313
- Cryptographic and encoding transformations (blake2b, bech32, etc.)

docs/get-started/koios.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Let's start with basics from consumer point of view, and then we can dive to a b
1515

1616
### API Documentation
1717

18-
You can access API documentation [here](https://api.koios.rest). Koios leverages [PostgREST](https://postgrest.org/) to provide data, which means you can easily filter your data vertically as well as horizontally, and leverage in-built ordering/custom paging benefits as per the guide [here](https://api.koios.rest/#overview--api-usage). There isn't any centralised registry to be able to access the endpoints for most of the usage.
18+
You can access API documentation [here](https://api.koios.rest). Koios leverages [PostgREST](https://postgrest.org/) to provide data, which means you can easily filter your data vertically as well as horizontally, and leverage in-built ordering/custom paging benefits as per the guide [here](https://api.koios.rest/#overview--api-usage). There isn't any centralized registry to be able to access the endpoints for most of the usage.
1919

2020
Each endpoint in the document provides a sample curl command that can be used to test using an example, which can be executed directly from the browser for testing as well.
2121

@@ -31,7 +31,7 @@ If you notice an issue or have a feature request (existing or new endpoint), we
3131

3232
## Participating as instance provider
3333

34-
There will always be an audience who might want to run everything locally instead of relying on any external connection. Typically, these would be heavy users of the API (explorers/wallet providers/marketplaces), who'd like to override default API limits, have customisation requirements, remove latency hops OR enthusiasts who'd like to contribute back and add to the strength of the API layer.
34+
There will always be an audience who might want to run everything locally instead of relying on any external connection. Typically, these would be heavy users of the API (explorers/wallet providers/marketplaces), who'd like to override default API limits, have customization requirements, remove latency hops OR enthusiasts who'd like to contribute back and add to the strength of the API layer.
3535

3636
For this audience, we've tried to leverage the existing widely adopted `guild-operators` suite to build simpler scripts that'd allow you to create a gRest instance. This independent gRest instance will give you 100% of features and compatibility with the API documentation hosted on api.koios.rest (assuming it's built from the latest `koios` tags).
3737

@@ -51,7 +51,7 @@ Typical steps involved for setting up your gRest instance would be (assuming you
5151

5252
1. Set up your OS for dependencies and create folder structures using [prereqs script](https://cardano-community.github.io/guild-operators/basics/#pre-requisites).
5353

54-
2. Install PostgreSQL server, followed by a tuning excercise that fits your infrastructure. See sample guide [here](https://cardano-community.github.io/guild-operators/Appendix/postgres/)
54+
2. Install PostgreSQL server, followed by a tuning exercise that fits your infrastructure. See sample guide [here](https://cardano-community.github.io/guild-operators/Appendix/postgres/)
5555

5656
3. Set up your Cardano Node and wait for node to sync to current epoch. See sample instructions [here](https://cardano-community.github.io/guild-operators/Build/node-cli/). You can optionally also install `cardano-submit-api` on the same server to be able to submit transactions using consistent paths from API documentation.
5757

docs/get-started/mesh/transactions-smart-contract.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ const txHash = await wallet.submitTx(signedTx);
5151

5252
## Unlock Assets from Smart Contract
5353

54-
As we may have locked assets in the contract, you can create transactions to unlock the assets with a redeemer that corresponds to the datum. Define the corresponding code to create the datum, only a transaction with the corrent datum hash is able to unlock the asset. Define the unit of the locked asset to search for the UTXO in the smart contract, which is required for the transaction's input.
54+
As we may have locked assets in the contract, you can create transactions to unlock the assets with a redeemer that corresponds to the datum. Define the corresponding code to create the datum, only a transaction with the correct datum hash is able to unlock the asset. Define the unit of the locked asset to search for the UTXO in the smart contract, which is required for the transaction's input.
5555

5656
```javascript
5757
async function _getAssetUtxo({ scriptAddress, asset, datum }) {

docs/get-started/plu-ts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ description: Get Started with `plu-ts`
99

1010
## Installation
1111

12-
### Add `plu-ts` as dependecy
12+
### Add `plu-ts` as dependency
1313

14-
To install `plu-ts` you can use `npm` (or the node package manager of your coiche) and run the following in you root project.
14+
To install `plu-ts` you can use `npm` (or the node package manager of your choice) and run the following in you root project.
1515

1616
```sh
1717
npm install @harmoniclabs/plu-ts

docs/get-started/running-cardano.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This guide does not cover the topic of running a block-producing `cardano-node`
2121
### Testnet
2222
There are two types of testnet: `preview` and `pre-prod`.
2323

24-
- **Preview Testnet**: Testing release candidates and Mainnet releases. Leads Mainnet hard forks by at least 4 weeks. This net is for those who just want to see how it runs, get familiarised and play with cardano-node.
24+
- **Preview Testnet**: Testing release candidates and Mainnet releases. Leads Mainnet hard forks by at least 4 weeks. This net is for those who just want to see how it runs, get familiarized and play with cardano-node.
2525

2626
- **Pre-Production Testnet**: Testing release candidates and Mainnet releases. Forks at approximately same time as Mainnet (within an epoch of each other). This net is ideal for those who are ready to run the Mainnet but want to test it before running it.
2727

docs/get-started/secure-workflow.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ All transactions will be done in these 3 steps:
3939
Therefore, the payment signing key (the private component of the [Cardano wallet address key pair](../operate-a-stake-pool/cardano-key-pairs#wallet-address-key-pairs)) **never leaves the air gap environment**. This is vital because:
4040

4141
- A standard assumption in security is that *any* Internet connection on *any* computer creates opportunities for malicious people or programs to copy, view, or modify *anything* unencrypted on that computer.
42-
- Unlike transactions with cryptocurrenty wallet software, in which the wallet's private payment keys are carefully encrypted and securely managed, the payment key (in this documentation, `payment.skey`) used for the raw transactions of development & stake pool operations is *not encrypted*.
42+
- Unlike transactions with cryptocurrency wallet software, in which the wallet's private payment keys are carefully encrypted and securely managed, the payment key (in this documentation, `payment.skey`) used for the raw transactions of development & stake pool operations is *not encrypted*.
4343
- This means that this file stored anywhere on your Internet connected computer or server, even for an instant, creates an opportunity for the funds at that address (`payment.addr`) to be ***lost***.
4444

4545
## Prerequisites
@@ -114,7 +114,7 @@ Attach your transfer memory stick to the air gap host and copy the files to your
114114

115115
Create a draft for the transaction and save it in `tx.draft`. Notes:
116116

117-
- As in the insecure example, `payment2.addr` is the address you're sending a payment *to*, while `payment.addr` (holding the UTxO where the runds are coming *from*), will store the "change" from this transaction.
117+
- As in the insecure example, `payment2.addr` is the address you're sending a payment *to*, while `payment.addr` (holding the UTxO where the funds are coming *from*), will store the "change" from this transaction.
118118
- For `--tx-in` we use the following syntax: `TxHash#TxIx` where `TxHash` is the transaction hash and `TxIx` is the index.
119119
- For `--tx-out` we use: `TxOut+Lovelace` where `TxOut` is the hex encoded address followed by the amount in `Lovelace`.
120120
- For the transaction draft, the `--tx-out` amounts and `--fee` can be set to zero.
@@ -224,7 +224,7 @@ Therefore this guide suggests *only* assembling transaction *details* outside th
224224

225225
## Other pending topics in secure workflow
226226

227-
These are not directly related to transacations, and will all eventually be addressed in their own pages on the Developer Portal:
227+
These are not directly related to transactions, and will all eventually be addressed in their own pages on the Developer Portal:
228228

229229
- pool key installation & updates: transferring keys (e.g. VRF and KES) securely from within the air gap to your stake pool block producer
230230
- making encrypted backups of your private keys (so they can be kept offsite / stored outside your air gap environment)

docs/integrate-cardano/creating-wallet-faucet.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
id: creating-wallet-faucet
33
title: Exploring Cardano wallets
44
sidebar_label: Exploring Cardano wallets
5-
description: This article explains how you can create different kinds of Cardano Wallets and how you can recieve some tAda(test ada) from the faucet.
5+
description: This article explains how you can create different kinds of Cardano Wallets and how you can receive some tAda(test ada) from the faucet.
66
image: /img/og/og-developer-portal.png
77
---
88

@@ -58,7 +58,7 @@ As mentioned before, in this guide we will only be focusing on the `cardano-cli`
5858
#### Creating a wallet with `cardano-cli`
5959

6060
:::note
61-
In this section, We will use the path `$HOME/cardano` to store all the `cardano-cli` related files as an example, please replace it with the directory you have choosen to store the files.
61+
In this section, We will use the path `$HOME/cardano` to store all the `cardano-cli` related files as an example, please replace it with the directory you have chosen to store the files.
6262
:::
6363

6464
:::important
@@ -346,7 +346,7 @@ cardano-cli transaction build-raw \
346346

347347
`cardano-cli transaction build-raw` : This tells `cardano-cli` to build a raw transaction.
348348

349-
`--tx-in` : This specifices the **UTXO** input that the transaction will use, you can add as many **UTXO** input as you want by adding multiple `--tx-in` in the `cardano-cli` arguments as long as they have a unique `TxHash` and `TxIdx` within all your inputs.
349+
`--tx-in` : This specifies the **UTXO** input that the transaction will use, you can add as many **UTXO** input as you want by adding multiple `--tx-in` in the `cardano-cli` arguments as long as they have a unique `TxHash` and `TxIdx` within all your inputs.
350350

351351
`--tx-out` : This specifies the target **wallet address**, **assets** and **quantity** to be sent to. You can add as many **UTXO** outputs as you want as long as the total **UTXO** input can satisfy the **assets** and **quantity** specified by the output.
352352

@@ -481,7 +481,7 @@ Congratulations, You have created and sent your first **Cardano** transaction us
481481
:::note
482482
This guide assumes you have installed `cardano-wallet` into your system. If not you can refer to [Installing cardano-wallet](/docs/get-started/installing-cardano-wallet) guide for instructions on how to do that.
483483

484-
We will use the path `$HOME/cardano/wallets` to store all the `cardano-wallet` related files as an example, please replace it with the directory you have choosen to store the files.
484+
We will use the path `$HOME/cardano/wallets` to store all the `cardano-wallet` related files as an example, please replace it with the directory you have chosen to store the files.
485485
:::
486486

487487
:::important
@@ -540,7 +540,7 @@ cardano-wallet serve \
540540
```
541541
> As you notice its almost like a network `URI` or a network `Path` than a file, this is a key difference that you will have to be aware depending on your operating system. You can replace the string `cardano-node-testnet` in the argument to whatever you like, this example path in particular is used in the [Daedalus Testnet Wallet](https://daedaluswallet.io) for **Windows**.
542542

543-
Once the server is running you should see sometihng like this (among other things):
543+
Once the server is running you should see something like this (among other things):
544544

545545
```
546546
[cardano-wallet.network:Info:12] [2021-06-03 13:48:24.82 UTC] Protocol parameters for tip are:
@@ -636,11 +636,11 @@ Our requests payload data is composed of:
636636

637637
`name` : The name of the wallet.
638638

639-
`passphrase` : Sets the security phrase to protect the funds inside the wallet. It will be required everytime you need write access to the wallet, more specifically sending assets.
639+
`passphrase` : Sets the security phrase to protect the funds inside the wallet. It will be required every time you need write access to the wallet, more specifically sending assets.
640640

641641
`mnemonic_sentence` : This is the wallet **recovery phrase** formatted into a `JSON` array.
642642

643-
If succesful, you should see something like this:
643+
If successful, you should see something like this:
644644

645645
```json
646646
{

0 commit comments

Comments
 (0)