From 3d8344f23c0af09e124bde45accc7e506478eb24 Mon Sep 17 00:00:00 2001
From: Rohit Yandigeri <91059418+RohitYandigeri@users.noreply.github.com>
Date: Wed, 24 Aug 2022 19:07:54 +0530
Subject: [PATCH] Update container-image-vulnerability-adaptor.md

---
 docs/proposals/container-image-vulnerability-adaptor.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/proposals/container-image-vulnerability-adaptor.md b/docs/proposals/container-image-vulnerability-adaptor.md
index 93a2941b..2d8a5e78 100644
--- a/docs/proposals/container-image-vulnerability-adaptor.md
+++ b/docs/proposals/container-image-vulnerability-adaptor.md
@@ -11,7 +11,7 @@ source #287
 
 ### Relation to this proposal
 
-Multiple changes and design decisions need to be made before Kubescape will support the above outlined controls. However, a focal point in the whole picutre is the ability to access vulnerability of databases of container images. We anticipate that most container image repositories will support image vulnerability scanning, like some major players already do. Since there is no single API available which all of these data sources support, it is important to create an adaption layer within Kubescape so that different datasources can serve Kubescape's goals.
+Multiple changes and design decisions need to be made before Kubescape will support the above outlined controls. However, a focal point in the whole picture is the ability to access vulnerability of databases of container images. We anticipate that most container image repositories will support image vulnerability scanning, like some major players already do. Since there is no single API available which all of these data sources support, it is important to create an adaption layer within Kubescape so that different datasources can serve Kubescape's goals.
 
 ## High level design of Kubescape