diff --git a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-cpu.png b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-cpu.png
index a50e1eebd92..341c7c82236 100644
Binary files a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-cpu.png and b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-cpu.png differ
diff --git a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-disk-usage.png b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-disk-usage.png
index 71fb3b0dbc1..20e392547ee 100644
Binary files a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-disk-usage.png and b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-disk-usage.png differ
diff --git a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-res-memory.png b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-res-memory.png
index 67355e8b2ba..2163d88301d 100644
Binary files a/docs/website/root/manual/getting-started/images/cardano-transaction-signer-res-memory.png and b/docs/website/root/manual/getting-started/images/cardano-transaction-signer-res-memory.png differ
diff --git a/docs/website/root/manual/getting-started/run-signer-node.md b/docs/website/root/manual/getting-started/run-signer-node.md
index a2447bf0358..39b28127250 100644
--- a/docs/website/root/manual/getting-started/run-signer-node.md
+++ b/docs/website/root/manual/getting-started/run-signer-node.md
@@ -72,18 +72,18 @@ Thus, there are no extra requirements on the recommended hardware than for runni
 Here are some figures about the Mithril signer node running on the `mainnet` Cardano network:
 
 - It is **idle** most of the time with a very low **CPU** usage of less than `5%`.
-- It is using less than `400MB` of **resident memory**.
-- It sends to the aggregator a **new signature** roughly every `10 minutes` and a **new registration** every `5 days` (`<1MB` per day).
-- When launched for the **first time**, a **pre-loading** phase occurs where the Cardano transactions will be imported with a spike of `50-70%` CPU on one core for `~6 hours`.
+- It is using less than `200 MB` of **resident memory**.
+- It sends to the aggregator a **new signature** roughly every `10 minutes` and a **new registration** every `5 days` (`<1 MB` per day).
+- When launched for the **first time**, a **pre-loading** phase occurs where the Cardano transactions will be imported with a spike of `50-70%` CPU on one core for `~5 hours`.
 - When signing for the **first time**, the Cardano database digest cache needs to be built with a spike of `50-70%` CPU on one core for `~1 hour`.
 - Also, the full Cardano database files will be **read from disk once** during this cache building process.
-- Only **stake distributions**, **Mithril keys** and some **cache** (for the **Cardano database** and the **Cardano transactions**) are stored on the disk (`<200MB`).
+- Only **stake distributions**, **Mithril keys** and some **cache** (for the **Cardano database** and the **Cardano transactions**) are stored on the disk (`<200 MB`).
 
 :::
 
 ### Cardano transactions certification footprint
 
-Here is detailed view of the impact of the signature of the Cardano transaction on the SPO infrastructure on the `mainnet`:
+Here is detailed view of the impact of the signature of the Cardano transactions (the most resource intensive part of Mithril) on the SPO infrastructure on the `mainnet`:
 
 #### CPU