From 7e5445d2ad1ecfdbc0b49dfc94c77ac6d92b4078 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vin=C3=ADcius=20Gajo?=
 <50725287+64J0@users.noreply.github.com>
Date: Wed, 1 Dec 2021 07:00:58 -0300
Subject: [PATCH] fix: change the path for images in the asff docs markdown
 (#1059)

---
 docs/asff.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/asff.md b/docs/asff.md
index 40cdfbe..c2ea6bb 100644
--- a/docs/asff.md
+++ b/docs/asff.md
@@ -8,7 +8,7 @@ You can configure kube-bench with the `--asff` to send findings to AWS Security
 * In the Security Hub console, under Integrations, search for kube-bench
 
 <p align="center">
-  <img src="../images/kube-bench-security-hub.png">
+  <img src="./images/kube-bench-security-hub.png">
 </p>
 
 * Click on `Accept findings`. This gives information about the IAM permissions required to send findings to your Security Hub account. kube-bench runs within a pod on your EKS cluster, and will need to be associated with a Role that has these permissions.
@@ -48,7 +48,7 @@ You can now run kube-bench as a pod in your cluster: `kubectl apply -f job-eks-a
 Findings will be generated for any kube-bench test that generates a `[FAIL]` or `[WARN]` output. If all tests pass, no findings will be generated. However, it's recommended that you consult the pod log output to check whether any findings were generated but could not be written to Security Hub.
 
 <p align="center">
-  <img src="../images/asff-example-finding.png">
+  <img src="./images/asff-example-finding.png">
 </p>
 
 [eks-instructions]: ../README.md#running-in-an-EKS-cluster