Skip to content

Commit

Permalink
chore: fix docs links
Browse files Browse the repository at this point in the history
  • Loading branch information
danielbate committed Jan 10, 2025
1 parent b1f053f commit e8bb60c
Show file tree
Hide file tree
Showing 5 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions apps/docs/src/guide/contracts/call-parameters.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ When interacting with contracts, you can configure specific parameters for contr
2. `gasLimit`
<!-- call_params:example:end -->

> **Note**: Setting transaction parameters is also available when calling contracts. More information on this can be found at [Transaction Parameters](../transactions/transaction-parameters.md).
> **Note**: Setting transaction parameters is also available when calling contracts. More information on this can be found at [Transaction Parameters](../transactions/adding-parameters.md).
The contract in use in this section has the following implementation:

Expand Down Expand Up @@ -39,7 +39,7 @@ The `gasLimit` refers to the maximum amount of gas that can be consumed specific

## Call Parameter `gasLimit` vs Transaction Parameter `gasLimit`

The call parameter `gasLimit` sets the maximum gas allowed for the actual contract call, whereas the transaction parameter `gasLimit` _(see [Transaction Parameters](../transactions/transaction-parameters.md))_ sets the maximum gas allowed for the entire transaction and constrains the `gasLimit` call parameter. If the call parameter `gasLimit` is set to a value greater than the _available_ transaction gas, then the entire available transaction gas will be allocated for the contract call execution.
The call parameter `gasLimit` sets the maximum gas allowed for the actual contract call, whereas the transaction parameter `gasLimit` _(see [Transaction Parameters](../transactions/adding-parameters.md))_ sets the maximum gas allowed for the entire transaction and constrains the `gasLimit` call parameter. If the call parameter `gasLimit` is set to a value greater than the _available_ transaction gas, then the entire available transaction gas will be allocated for the contract call execution.

If you don't set the `gasLimit` for the call, the transaction `gasLimit` will be applied.

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/src/guide/predicates/custom-transactions.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Utilizing predicate logic unlocks a wide range of possibilities for your dApps when creating transactions. Therefore, pairing predicates with custom transactions can help you achieve more complex use cases. This can be achieved by instantiating a custom transaction, appending the predicate resources, and submitting the transaction via a successfully validated predicate.

Custom transactions can be shaped via a `ScriptTransactionRequest` instance. For more information on crafting custom transactions and the methods available to them, please refer to the [Transaction Request](../transactions/transaction-request.md) guide.
Custom transactions can be shaped via a `ScriptTransactionRequest` instance. For more information on crafting custom transactions and the methods available to them, please refer to the [Transaction Request](../transactions/modifying-the-request.md) guide.

However, this guide will demonstrate how to use a predicate in a custom transaction. Consider the following predicate, where a configurable pin must be used to validate the predicate and unlock the funds:

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/src/guide/scripts/custom-script-call.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Preparing a Script Transaction

Akin to Contracts, we can configure the [call parameters](../contracts/call-parameters.md) and [transaction parameters](../transactions/transaction-parameters.md) for Scripts, as well as retrieve the entire transaction request or transaction ID prior to submission.
Akin to Contracts, we can configure the [call parameters](../contracts/call-parameters.md) and [transaction parameters](../transactions/adding-parameters.md) for Scripts, as well as retrieve the entire transaction request or transaction ID prior to submission.

<<< @./snippets/script-with-configurable.ts#preparing-scripts{ts:line-numbers}
2 changes: 1 addition & 1 deletion apps/docs/src/guide/transactions/adding-parameters.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Adding Parameters

Transaction parameters allow you to configure various aspects of your blockchain transactions. Dependent on these parameters, it may introduce a [transaction policy](./transaction-policies.md).
Transaction parameters allow you to configure various aspects of your blockchain transactions. Dependent on these parameters, it may introduce a [transaction policy](./adding-policies.md).

All available parameters are shown below:

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/src/guide/transactions/adding-policies.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Adding Policies

Transaction policies are rules that can govern how a transaction is processed, introduced by the [transaction parameters](./transaction-parameters.md) that you pass to a transaction request. The available policies are as follows:
Transaction policies are rules that can govern how a transaction is processed, introduced by the [transaction parameters](./adding-parameters.md) that you pass to a transaction request. The available policies are as follows:

### Tip

Expand Down

0 comments on commit e8bb60c

Please sign in to comment.