diff --git a/content/courses/token-extensions/default-account-state.md b/content/courses/token-extensions/default-account-state.md index 535aea8be..dcbea482c 100644 --- a/content/courses/token-extensions/default-account-state.md +++ b/content/courses/token-extensions/default-account-state.md @@ -66,7 +66,8 @@ is `Initialized`. ### Adding default account state -Initializing a mint with the default account state extension involves three instructions: +Initializing a mint with the default account state extension involves three +instructions: - `SystemProgram.createAccount` - `createInitializeDefaultAccountStateInstruction` diff --git a/content/guides/advanced/verified-builds.md b/content/guides/advanced/verified-builds.md index e601ab46d..b137776b1 100644 --- a/content/guides/advanced/verified-builds.md +++ b/content/guides/advanced/verified-builds.md @@ -271,7 +271,7 @@ solana-verify get-program-hash -u $NETWORK_URL $PROGRAM_ID ``` > You may have different versions deployed on different -> [Solana clusters](/docs/core//clusters.md) (i.e. devnet, testnet, mainnet). +> [Solana clusters](/docs/core/clusters.md) (i.e. devnet, testnet, mainnet). > Ensure you use the correct network URL for the desired Solana cluster you want > to verify a program against. Remote verification will only work on mainnet. diff --git a/content/guides/javascript/get-program-accounts.md b/content/guides/javascript/get-program-accounts.md index fdad11bb4..c3e02716d 100644 --- a/content/guides/javascript/get-program-accounts.md +++ b/content/guides/javascript/get-program-accounts.md @@ -18,9 +18,9 @@ altRoutes: An RPC method that returns all accounts owned by a program. Currently pagination is not supported. Requests to -[`getProgramAccounts`](/docs/rpc//http/getProgramAccounts.mdx) should include -the `dataSlice` and/or `filters` parameters to improve response time and return -only intended results. +[`getProgramAccounts`](/docs/rpc/http/getProgramAccounts.mdx) should include the +`dataSlice` and/or `filters` parameters to improve response time and return only +intended results. ## getProgramAccounts RPC Method @@ -101,8 +101,7 @@ can efficiently request just the data we intend to use. ### `filters` The most common parameter to use with `getProgramAccounts` is the `filters` -array. This array accepts two types of filters, `dataSize` and `memcmp`. -Before +array. This array accepts two types of filters, `dataSize` and `memcmp`. Before using either of these filters, we should be familiar with how the data we are requesting is laid out and serialized. @@ -129,10 +128,9 @@ any field stored on our account. Specifically, we can query only for accounts that match a particular set of bytes at a particular position. `memcmp` requires two arguments: -- `offset`: the position at which to begin comparing data. This position is +- `offset`: the position at which to begin comparing data. This position is measured in bytes and is expressed as an integer. -- `bytes`: the data that should match the account's data. This is represented - as +- `bytes`: the data that should match the account's data. This is represented as a base-58 encoded string should be limited to less than 129 bytes. It's important to note that `memcmp` will only return results that are an exact diff --git a/docs/advanced/retry.md b/docs/advanced/retry.md index dfea6dac3..be27ecefa 100644 --- a/docs/advanced/retry.md +++ b/docs/advanced/retry.md @@ -290,7 +290,7 @@ fork. If an application has access to RPC nodes behind a load balancer, it can also choose to divide its workload amongst specific nodes. RPC nodes that serve data-intensive requests such as -[getProgramAccounts](/content//guides/javascript/get-program-accounts.md) may be +[getProgramAccounts](/content/guides/javascript/get-program-accounts.md) may be prone to falling behind and can be ill-suited for also forwarding transactions. For applications that handle time-sensitive transactions, it may be prudent to have dedicated nodes that only handle `sendTransaction`.