diff --git a/docs/src/calling-contracts/call-response.md b/docs/src/calling-contracts/call-response.md
index 309c9b25b1..f0660c6393 100644
--- a/docs/src/calling-contracts/call-response.md
+++ b/docs/src/calling-contracts/call-response.md
@@ -22,7 +22,7 @@ Once you unwrap the `FuelCallResponse`, you have access to this struct:
 <!-- call_resp_fields:example:start -->
 Where `value` will hold the value returned by its respective contract method, represented by the exact type returned by the FuelVM, E.g., if your contract returns a FuelVM's `u64`, `value`'s `D` will be a `u64`. If it's a FuelVM's tuple `(u8,bool)`, then `D` will be a `(u8,bool)`. If it's a custom type, for instance, a Sway struct `MyStruct` containing two components, a `u64`, and a `b256`, `D` will be a struct generated at compile-time, called `MyStruct` with `u64` and a `[u8; 32]` (the equivalent of `b256` in Rust).
 
-- `receipts` will hold all [receipts](https://specs.fuel.network/master/protocol/abi/receipts.html) generated by that specific contract call.
+- `receipts` will hold all [receipts](https://docs.fuel.network/docs/specs/abi/receipts/) generated by that specific contract call.
 - `gas_used` is the amount of gas it consumed by the contract call.
 - `tx_id` will hold the ID of the corresponding submitted transaction.
 <!-- call_resp_fields:example:end -->
diff --git a/docs/src/calling-contracts/variable-outputs.md b/docs/src/calling-contracts/variable-outputs.md
index 76f962a664..93473e6420 100644
--- a/docs/src/calling-contracts/variable-outputs.md
+++ b/docs/src/calling-contracts/variable-outputs.md
@@ -2,7 +2,7 @@
 
 <!-- This section should explain variable outputs  -->
 <!-- variable_outputs:example:start -->
-Sometimes, the contract you call might transfer funds to a specific address, depending on its execution. The underlying transaction for such a contract call has to have the appropriate number of [variable outputs](https://specs.fuel.network/master/tx-format/output.html#outputvariable) to succeed.
+Sometimes, the contract you call might transfer funds to a specific address, depending on its execution. The underlying transaction for such a contract call has to have the appropriate number of [variable outputs](https://docs.fuel.network/docs/specs/tx-format/output/#outputvariable) to succeed.
 <!-- variable_outputs:example:end -->
 
 Let's say you deployed a contract with the following method:
diff --git a/docs/src/cli/fuels-abi-cli.md b/docs/src/cli/fuels-abi-cli.md
index 5a6e81f684..da4baa03b6 100644
--- a/docs/src/cli/fuels-abi-cli.md
+++ b/docs/src/cli/fuels-abi-cli.md
@@ -1,6 +1,6 @@
 # `fuels-abi-cli`
 
-Simple CLI program to encode Sway function calls and decode their output. The ABI being encoded and decoded is specified [here](https://specs.fuel.network/master/abi/index.html).
+Simple CLI program to encode Sway function calls and decode their output. The ABI being encoded and decoded is specified [here](https://docs.fuel.network/docs/specs/abi/).
 
 ## Usage
 
diff --git a/docs/src/codec/index.md b/docs/src/codec/index.md
index 2d6e43f269..69fa1762ee 100644
--- a/docs/src/codec/index.md
+++ b/docs/src/codec/index.md
@@ -1,6 +1,6 @@
 # Codec
 
-Encoding and decoding are done as per [the fuel spec](https://specs.fuel.network/master/abi/argument-encoding.html). To this end, `fuels` makes use of the [`ABIEncoder`](https://docs.rs/fuels/latest/fuels/core/codec/struct.ABIEncoder.html) and the [`ABIDecoder`](https://docs.rs/fuels/latest/fuels/core/codec/struct.ABIDecoder.html).
+Encoding and decoding are done as per [the fuel spec](https://docs.fuel.network/docs/specs/abi/argument-encoding/). To this end, `fuels` makes use of the [`ABIEncoder`](https://docs.rs/fuels/latest/fuels/core/codec/struct.ABIEncoder.html) and the [`ABIDecoder`](https://docs.rs/fuels/latest/fuels/core/codec/struct.ABIDecoder.html).
 
 ## Prerequisites for decoding/encoding