From 97fe834012e8eb86ea953870f5a0b1840e53815e Mon Sep 17 00:00:00 2001
From: Avinash Upadhyaya K R
 <52544819+avinashupadhya99@users.noreply.github.com>
Date: Fri, 27 Oct 2023 20:39:12 +0530
Subject: [PATCH] update README image scanning docs

Signed-off-by: Avinash Upadhyaya K R <52544819+avinashupadhya99@users.noreply.github.com>
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9320852..1f67c5d 100644
--- a/README.md
+++ b/README.md
@@ -136,7 +136,7 @@ The next important thing to note is that Kubescape only fixes the files. It does
 
 The Kubescape Github Action is also able to scan images. But you should be aware that image scanning cannot run in parallel with configuration scanning and file fixing at the moment. If you would like to run both image and configuration scanning, you should define at least two separate steps with the same action but different arguments: one for image scanning and the other for configuration scanning.
 
-To scan a container image with a Kubescape Github Action, use the following workflow definition, keeping in mind that you need to replace `image: "nginx"` with the appropriate image name:
+To scan a container image with a Kubescape Github Action, use the following workflow definition, keeping in mind that you need to replace `image: "quay.io/kubescape/kubescape"` with the appropriate image name:
 
 ```yaml
 name: Kubescape scanning for image vulnerabilities