Fix Typos and Minor Documentation Updates Across Multiple Files

apps/docs/src/guide/contracts/configurable-constants.md

@@ -16,7 +16,7 @@ In this contract, the function `echo_configurables` returns the values of the co
 
 ## Setting New Values For Configurable Constants
 
-During contract deployment, you can define new values for any/all of the configurable constants. The example below shows setting of one configurable constant, while the others will have default values.
+During contract deployment, you can define new values for any/all the configurable constants. The example below shows setting of one configurable constant, while the others will have default values.
 
 <<< @./snippets/configurable-constants.ts#setting-configurable-constant{ts:line-numbers}
 

apps/docs/src/guide/contracts/deploying-contracts.md

@@ -57,6 +57,6 @@ In the above guide we use the recommended `deploy` method. If you are working wi
 
 <<< @./snippets/deploying-contracts/deployment.ts#blobs{ts:line-numbers}
 
-In the above example, we also pass a `chunkSizeMultiplier` option to the deployment method. The SDK will attempt to chunk the contract to the most optimal about, however the transaction size can fluctuate and you can also be limited by request size limits against the node. By default we set a multiplier of 0.95, meaning the chunk size will be 95% of the potential maximum size, however you can adjust this to suit your needs and ensure the transaction passes. It must be set to a value between 0 and 1.
+In the above example, we also pass a `chunkSizeMultiplier` option to the deployment method. The SDK will attempt to chunk the contract to the most optimal about, however the transaction size can fluctuate and you can also be limited by request size limits against the node. By default, we set a multiplier of 0.95, meaning the chunk size will be 95% of the potential maximum size, however you can adjust this to suit your needs and ensure the transaction passes. It must be set to a value between 0 and 1.
 
 > **Note:** Deploying large contracts using blob transactions will take more time. Each transaction is dependent and has to wait for a block to be produced before it gets mined. Then a create transaction is submitted as normal. So you will need to wait longer than usual for the contract to be fully deployed and can be interacted with.

apps/docs/src/guide/cookbook/custom-transactions-from-contract-calls.md

@@ -1,6 +1,6 @@
 # Custom Transactions From Contract Calls
 
-In the previous example we demonstrated how you can instantiate a [`ScriptTransactionRequest`](../../api/Account/ScriptTransactionRequest.md) to customize and build out a more complex transaction via a script. The same can be done using contracts, but this allows us to utilize functions available in the contract and access on-chain state. Allowing us to harness all of the power from an invocation scope and a transaction request.
+In the previous example we demonstrated how you can instantiate a [`ScriptTransactionRequest`](../../api/Account/ScriptTransactionRequest.md) to customize and build out a more complex transaction via a script. The same can be done using contracts, but this allows us to utilize functions available in the contract and access on-chain state. Allowing us to harness all the power from an invocation scope and a transaction request.
 
 This cookbook demonstrates how we can utilize a contract call to build out a custom transaction, allowing us to update on-chain state and transfer assets to a recipient address.
 

apps/docs/src/guide/cookbook/custom-transactions.md

@@ -1,6 +1,6 @@
 # Custom Transactions
 
-There may be scenarios where you need to build out transactions that involve multiple program types and assets; this can be done by instantiating a [`ScriptTransactionRequest`](../../api/Account/ScriptTransactionRequest.md). This class allows you to a append multiple program types and assets to a single transaction.
+There may be scenarios where you need to build out transactions that involve multiple program types and assets; this can be done by instantiating a [`ScriptTransactionRequest`](../../api/Account/ScriptTransactionRequest.md). This class allows you to an append multiple program types and assets to a single transaction.
 
 Consider the following script that transfers multiple assets to a contract:
 

apps/docs/src/guide/scripts/deploying-scripts.md

@@ -11,7 +11,7 @@ To deploy a script, we can use the [Fuels CLI](../fuels-cli/index.md) and execut
 This will perform the following actions:
 
 1. Compile the script using your `forc` version
-1. Deploy the built script binary to the chain as a blob
+1. Deploy the build script binary to the chain as a blob
 1. Generate a script that loads the blob that can be used to execute the script
 1. Generate types for both the script and the loader that you can use in your application
 

apps/docs/src/guide/wallets/wallet-manager.md

@@ -56,7 +56,7 @@ A key feature of the `WalletManager` is its ability to manage multiple vaults, e
 
 After executing this, you will find that your `WalletManager` is managing two `privateKey` vaults, both storing the same wallet.
 
-Remember, both `title` and `secret` are optional when adding vaults, but providing a `title` makes it easier to manage your vaults and wallets. If you add a vault without providing a `secret`, this will result in one new account (wallet) being generated by the vault it self.
+Remember, both `title` and `secret` are optional when adding vaults, but providing a `title` makes it easier to manage your vaults and wallets. If you add a vault without providing a `secret`, this will result in one new account (wallet) being generated by the vault itself.
 
 ### Using The `WalletManager`
 

internal/forc/CHANGELOG.md

@@ -308,7 +308,7 @@
 
 ### Patch Changes
 
-- [#565](https://github.com/FuelLabs/fuels-ts/pull/565) [`bdfa9d6`](https://github.com/FuelLabs/fuels-ts/commit/bdfa9d6e453a9c47177b19f2811265d740fc4ac4) Thanks [@segfault-magnet](https://github.com/segfault-magnet)! - Adapted to forc v0.28.0+ with respect to vectors now using an untyped raw ptr instead of a u64 for the vec ptr.
+- [#565](https://github.com/FuelLabs/fuels-ts/pull/565) [`bdfa9d6`](https://github.com/FuelLabs/fuels-ts/commit/bdfa9d6e453a9c47177b19f2811265d740fc4ac4) Thanks [@segfault-magnet](https://github.com/segfault-magnet)! - Adapted to forc v0.28.0+ with respect to vectors now using an untyped raw ptr instead of an u64 for the vec ptr.
 
 ## 0.26.1