diff --git a/packages/library/README.md b/packages/library/README.md index 9ae7e4363a27..5bec344e6ceb 100644 --- a/packages/library/README.md +++ b/packages/library/README.md @@ -882,7 +882,7 @@ const signedTransaction = await signTransaction([signer], transactionMessageWith ### Calibrating A Transaction Message's Compute Unit Budget -Correctly budgeting a compute unit limit for your transaction message can increase the probabilty that your transaction will be accepted for processing. If you don't declare a compute unit limit on your transaction, validators will assume an upper limit of 200K compute units (CU) per instruction. +Correctly budgeting a compute unit limit for your transaction message can increase the probability that your transaction will be accepted for processing. If you don't declare a compute unit limit on your transaction, validators will assume an upper limit of 200K compute units (CU) per instruction. Since validators have an incentive to pack as many transactions into each block as possible, they may choose to include transactions that they know will fit into the remaining compute budget for the current block over transactions that might not. For this reason, you should set a compute unit limit on each of your transaction messages, whenever possible. diff --git a/packages/library/src/compute-limit-internal.ts b/packages/library/src/compute-limit-internal.ts index b2e389b250a0..17fe252e303e 100644 --- a/packages/library/src/compute-limit-internal.ts +++ b/packages/library/src/compute-limit-internal.ts @@ -63,7 +63,7 @@ function isSetComputeLimitInstruction( * consumed during simulation. * * The estimate this function returns can be used to set a compute unit limit on the transaction. - * Correctly budgeting a compute unit limit for your transaction message can increase the probabilty + * Correctly budgeting a compute unit limit for your transaction message can increase the probability * that your transaction will be accepted for processing. * * If you don't declare a compute unit limit on your transaction, validators will assume an upper