diff --git a/docs/assets/images/screenshot-monitoring-backup.jpg b/docs/assets/images/screenshot-monitoring-backup.jpg
new file mode 100644
index 000000000..9301e75ce
Binary files /dev/null and b/docs/assets/images/screenshot-monitoring-backup.jpg differ
diff --git a/docs/assets/images/screenshot-slack-monitoring.jpg b/docs/assets/images/screenshot-slack-monitoring.jpg
index 417aae4b1..c47b46112 100644
Binary files a/docs/assets/images/screenshot-slack-monitoring.jpg and b/docs/assets/images/screenshot-slack-monitoring.jpg differ
diff --git a/docs/salesforce-monitoring-home.md b/docs/salesforce-monitoring-home.md
index fea0b2a25..970b9145b 100644
--- a/docs/salesforce-monitoring-home.md
+++ b/docs/salesforce-monitoring-home.md
@@ -18,7 +18,7 @@ Salesforce provide **Audit Trail** to trace configuration updates in **productio
 
 You can **know who updated what**, but not with details (before / after).
 
-Sfdx-hardis monitoring provides a **simple way to know the exact state of your orgs metadatas everyday**, or even several times a day, and provides an **exact and detailed comparison with the previous metadata configuration**.
+Sfdx-hardis monitoring provides a **simple way to know the exact state of your orgs metadatas everyday**, or even several times a day, and provides an **exact and detailed comparison with the previous metadata configuration** (using git commits comparison)
 
 Installation and usage are **admin-friendly**, and **notifications** can be sent via **Slack** or **Microsoft Teams**.
 
@@ -33,6 +33,8 @@ Extra features are also available, like:
 
 You don't need to work in CI/CD to use Monitoring, it is **compliant with any API enabled org** :)
 
+![](assets/images/screenshot-monitoring-backup.jpg)
+
 ## How does it work ?
 
 Every night (or even more frequently, according to your schedule), a CI job will be triggered.