Skip to content

docs: fixes and improvements in documentation #3731

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

Closed
Rahul-Lashkari wants to merge 1 commit into from
Closed

docs: fixes and improvements in documentation #3731

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/content/docs/basics/cpi.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description:
---

Cross Program Invocations (CPI) refer to the process of one program invoking
instructions of another program, which enables the composibility of Solana
instructions of another program, which enables the composability of Solana
programs.

This section will cover the basics of implementing CPIs in an Anchor program,
Expand Down Expand Up @@ -98,7 +98,7 @@ resulting in a successful SOL transfer.

Cross Program Invocations (CPIs) allow one program to invoke instructions on
another program. The process of implementing a CPI is the same as that of
creating a instruction where you must specify:
creating an instruction where you must specify:

1. The program ID of the program being called
2. The accounts required by the instruction
Expand Down
6 changes: 3 additions & 3 deletions docs/content/docs/installation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -468,7 +468,7 @@ To verify that the installation was successful, check the Yarn version:
yarn --version
```

You should the following output:
You should see the following output:

```
1.22.1
Expand Down Expand Up @@ -567,7 +567,7 @@ Keypair Path: /Users/test/.config/solana/id.json
Commitment: confirmed
```

The RPC URL and Websocket URL specific the Solana cluster the CLI will make
The RPC URL and Websocket URL specify the Solana cluster the CLI will make
requests to. By default this will be mainnet-beta.

You can update the Solana CLI cluster using the following commands:
Expand Down Expand Up @@ -614,7 +614,7 @@ Generating a new keypair

For added security, enter a BIP39 passphrase

NOTE! This passphrase improves security of the recovery seed phrae NOT the
NOTE! This passphrase improves security of the recovery seed phrase NOT the
keypair file itself, which is stored as insecure plain text

BIP39 Passphrase (empty for none):
Expand Down
2 changes: 1 addition & 1 deletion docs/content/docs/updates/release-notes/0-31-0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -440,7 +440,7 @@ Building the IDL via the
[`build_idl`](https://github.com/coral-xyz/anchor/blob/v0.31.0/idl/src/build.rs#L119)
function made it impossible to extend its functionality e.g. add new parameters
without a breaking change. To solve this problem, there is a new way to build
IDLs programatically:
IDLs programmatically:

```rs
let idl = IdlBuilder::new().program_path(path).skip_lint(true).build()?;
Expand Down