Fix some commands after testing

Author: vrom911

docs/docs/how-to/commit-blueprint.md

@@ -93,7 +93,6 @@ cardano-cli query protocol-parameters \
   --testnet-magic 1 \
   --socket-path testnets/preprod/node.socket \
   --out-file pp-preprod.json
-
 ```
 
 ## Step 5
@@ -127,7 +126,7 @@ Press `i` to initialize the `head`. Once the head is in the `Initializing` state
 
 This is the valid JSON request:
 
-```shell
+```json
 {
   "blueprintTx": {
     "cborHex": "84a3008182582014ab373afb1112d925b0f6a84518ac26d4a8cfcc99231e1f47e6996182e843a900018182581d6069830961c6af9095b0f2648dff31fa9545d8f0b6623db865eb78fde81a007a12000200a0f5f6",

docs/docs/how-to/commit-script-utxo.md

@@ -6,6 +6,12 @@ sidebar_position: 2
 
 This guide provides a walkthrough on how to commit a UTxO from a script into a Hydra Head.
 
+A **Script UTxO** is a special kind of Unspent Transaction Output (UTxO) that isn't controlled by a simple private key. Instead, it's locked by a script—a small program that runs on the blockchain. To spend the funds in a Script UTxO, you must provide data (a "redeemer" and "datum") that satisfies the conditions defined in that script.
+
+Committing a script UTxO to a Hydra Head is a powerful feature that allows for more complex on-chain validation logic to be brought into the Head. This is useful for scenarios where you need to enforce specific rules on how funds can be spent, even within the Head's off-chain environment.
+
+This tutorial will guide you through the entire process, which involves creating a script, locking an on-chain UTxO with it, and then preparing a special "blueprint" transaction to commit this script UTxO into an open Head.
+
 ## Prerequisites
 
 This tutorial assumes you are familiar with the process of committing a standard UTxO to a Hydra Head. If you are not, please first read the [Commit using a blueprint](./commit-blueprint.md) tutorial.
@@ -60,19 +66,35 @@ cardano-cli query utxo \
   --socket-path testnets/preprod/node.socket
 ```
 
-Pick a UTxO from the output and use it to build a transaction that sends funds to the script address. Let's say you picked a UTxO with TxHash `a5a11c..` and index `0` containing `100 ADA`. We'll send `10 ADA` to the script address:
+Pick a UTxO from the output and use it to build a transaction that sends funds to the script address. Let's say you picked a UTxO with TxHash `<UTXO_TXIX>` containing `100 ADA`. We'll send `10 ADA` to the script address.
+
+First, create a file named `datum.json` that contains the datum. For this example, we will just use the integer `42`.
+
+```json
+{
+    "constructor": 0,
+    "fields": [
+        {
+            "int": 42
+        }
+    ]
+}
+```
+
+Now, build the transaction:
 
 ```shell
 cardano-cli conway transaction build \
   --tx-in <UTXO_TXIX> \
   --tx-out $(cat script.addr)+10000000 \
-  --tx-out-datum-embed-value 42 \
+  --tx-out-inline-datum-file datum.json \
   --change-address $(cardano-cli address build --payment-verification-key-file hydra-cluster/config/credentials/alice-funds.vk --testnet-magic 1) \
   --testnet-magic 1 \
   --socket-path testnets/preprod/node.socket \
   --out-file tx.raw
 ```
-Note that we are also providing a datum value `42`. Even though our script does not use it, a datum is required for all script UTxOs.
+
+Note that we are also providing an inline datum via the `datum.json` file. Even though our script does not use it, a datum is required for all script UTxOs.
 
 Now, sign and submit the transaction:
 
@@ -101,19 +123,23 @@ cardano-cli query utxo \
 
 Now we are ready to prepare the commit. We'll create a blueprint transaction that spends the script UTxO. Note that this transaction is not meant to be signed and submitted to the Cardano network. It's just a blueprint that we'll send to the `hydra-node` to get a properly drafted commit transaction.
 
+We use `cardano-cli ... build-raw` to construct this blueprint because it gives us full control over the transaction structure without trying to automatically balance it or calculate fees, which is perfect for a blueprint.
+
 In this transaction, we'll spend the script UTxO and send the funds to our own wallet address.
 
 ```shell
 cardano-cli conway transaction build-raw \
   --tx-in <SCRIPT_UTXO_TXIX> \
   --tx-in-script-file always-true.plutus \
   --tx-in-datum-value 42 \
-  --tx-in-reedeemer-value 42 \
+  --tx-in-redeemer-value 42 \
+  --tx-in-execution-units '(0, 0)' \
   --tx-out $(cardano-cli address build --payment-verification-key-file hydra-cluster/config/credentials/alice-funds.vk --testnet-magic 1)+10000000 \
   --fee 0 \
   --out-file tx.json
 ```
-As you can see, we are providing the script file, the datum, and a redeemer. Our "always-true" script doesn't actually check any of these, but they are required for a valid transaction spending a script UTxO.
+
+A real-world script, like one written in [Aiken](https://aiken-lang.org/), would use the datum to carry state and the redeemer to provide input for validation. Our "always-true" script doesn't actually check any of these, but they are still required fields for a valid transaction that spends a script UTxO. Note that we also provide `--tx-in-execution-units`. This is required for any script spend to tell the network how much computational resource to budget for the script's execution. Since our script does nothing, we can use `(0, 0)`.
 
 ## Step 5: Commit the script UTxO
 

docs/docs/how-to/incremental-commit.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 ---
 
 # Commit funds to an open Head

docs/docs/how-to/incremental-decommit.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 ---
 
 # Decommit funds

docs/docs/how-to/operating-hydra.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 ---
 
 # Operate a Hydra node

docs/docs/how-to/sideload-snapshot.md

@@ -1,6 +1,6 @@
 ---
 
-sidebar_position: 7
+sidebar_position: 8
 ---
 
 # Sideload Snapshot

docs/docs/how-to/submit-transaction.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 3
 ---
 
 # Submit a transaction

docs/docs/how-to/withdraw-zero.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 4
 ---
 
 # Use withdraw zero trick