Fix instructions in our docs (#2097)

fix #2095 

---

<!-- Consider each and tick it off one way or the other -->
* [x] CHANGELOG updated or not needed
* [x] Documentation updated or not needed
* [x] Haddocks updated or not needed
* [x] No new TODOs introduced or explained herafter

Author: noonio

docs/docs/getting-started.md

@@ -66,7 +66,7 @@ You can use [jq](https://jqlang.github.io/jq/) to follow the logs and see the no
 following command:
 
 ```
-docker compose logs -f --no-log-prefix cardano-node | jq -Rr 'fromjson? | .data.val.kind'
+docker compose logs -f --no-log-prefix cardano-node | jq -Rr 'fromjson? | .data.kind'
 ```
 :::
 

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

@@ -70,8 +70,7 @@ cardano-cli query utxo \
 Select the first `UTXO`, which has eight ada available. Use five ada to commit and rely on `hydra-node` to balance the commit transaction:
 
 ```shell
-cardano-cli transaction build-raw \
-  --babbage-era \
+cardano-cli conway transaction build-raw \
   --tx-in 14ab373afb1112d925b0f6a84518ac26d4a8cfcc99231e1f47e6996182e843a9#0 \
   --tx-out addr_test1vp5cxztpc6hep9ds7fjgmle3l225tk8ske3rmwr9adu0m6qchmx5z+5000000 \
   --fee 0 \
@@ -167,13 +166,13 @@ Next, sign and submit the draft of the commit transaction:
 
 ```shell
 
-cardano-cli transaction sign \
+cardano-cli conway transaction sign \
   --tx-file commit-tx.json \
   --signing-key-file hydra-cluster/config/credentials/alice-funds.sk \
   --out-file signed-tx.json
 
 
-cardano-cli transaction submit \
+cardano-cli conway transaction submit \
   --tx-file signed-tx.json \
   --socket-path testnets/preprod/node.socket \
   --testnet-magic 1

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

@@ -59,12 +59,12 @@ curl -X POST localhost:4001/commit \
 
 Which we can submit to the cardano network:
 ```shell
-cardano-cli transaction sign \
+cardano-cli conway transaction sign \
   --tx-file deposit-tx.json \
   --signing-key-file ${WALLET_SK} \
   --out-file deposit-tx.signed.json
 
-cardano-cli transaction submit \
+cardano-cli conway transaction submit \
   --tx-file deposit-tx.signed.json
 ```
 

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

@@ -57,7 +57,7 @@ For example, to spend the first UTXO queried above in a transaction sending the
 
 ```shell
 LOVELACE=$(jq -r 'to_entries[0].value.value.lovelace' < utxo.json)
-cardano-cli transaction build-raw \
+cardano-cli conway transaction build-raw \
   --tx-in $(jq -r 'to_entries[0].key' < utxo.json) \
   --tx-out ${WALLET_ADDR}+${LOVELACE} \
   --fee 0 \
@@ -67,14 +67,14 @@ cardano-cli transaction build-raw \
 You can inspect the transaction with
 
 ```shell
-cardano-cli transaction view --tx-file decommit.json
+cardano-cli conway transaction view --tx-file decommit.json
 ```
 
 As the transaction spends from Alice's funds in the Hydra head, we also need to
 sign it with her key:
 
 ```shell
-cardano-cli transaction sign \
+cardano-cli conway transaction sign \
   --tx-file decommit.json \
   --signing-key-file ${WALLET_SK} \
   --out-file alice-decommit-tx-signed.json

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

@@ -32,14 +32,13 @@ Below is an example response:
 Assuming the single UTXO is owned by `some-payment-key.sk` and you want to send all of it to another address, you can use `cardano-cli` (or your preferred transaction builder) to construct and sign a transaction:
 
 ```shell title="Transaction building"
-cardano-cli transaction build-raw \
-  --babbage-era \
+cardano-cli conway transaction build-raw \
   --tx-in 8690d7618bb88825d6ec7cfbe2676779b8f4633cb137a1c12cd31b4c53f90f32#0 \
   --tx-out addr_test1vp5cxztpc6hep9ds7fjgmle3l225tk8ske3rmwr9adu0m6qchmx5z+100000000 \
   --fee 0 \
   --out-file tx.json
 
-cardano-cli transaction sign \
+cardano-cli conway transaction sign \
   --tx-body-file tx.json \
   --signing-key-file some-payment-key.sk \
   --out-file tx-signed.json
@@ -53,4 +52,4 @@ This command generates a message suitable for submission to the `hydra-node` via
 cat tx-signed.json | jq -c '{tag: "NewTx", transaction: .}' | websocat "ws://127.0.0.1:4001?history=no"
 ```
 
-The transaction will be validated by all connected `hydra-node` instances. It will result in either a `TxInvalid` message, providing a reason for rejection, or a `TxValid` message followed by a `SnapshotConfirmed`, updating the UTXO available in the head shortly after that.
+`Greetings` message will be displayed as always when calling the web socket api and the transaction will be validated by all connected `hydra-node` instances. It will result in either a `TxInvalid` message, providing a reason for rejection, or a `TxValid` message followed by a `SnapshotConfirmed`, updating the UTXO available in the head shortly after that.