diff --git a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
index d528bcdd1..51e31937e 100644
--- a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
+++ b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
@@ -65,18 +65,14 @@ CONS:
 
 #### _Option 2_ go approach [2]: Reuse the kubernetes own e2e test infrastructure and framework
 
-As mentioned above, Sonobuoy already provides [Kubernetes own e2e tests][k8s-e2e-tests] as a plugin.
-These tests contain a vast number of examples that we could reuse and adapt to our needs.
-For the implementation, we could reuse the e2e tests and the framework in an adapted structure.
-More precisely this would lead us to make use of the test framework [ginkgo][ginkgo].
-The entry point for the implementation would be the build process of the Dockerimage which contains
-the e2e tests. Therefore we could copy the setup of the build process from
-[kubernetes/test/conformance/image][conformance-image] and adapt it to our requirements.
-The build process requires some files from the kubernetes repository.
-More precisely from:
-  - [kubernetes/cluster](https://github.com/kubernetes/kubernetes/tree/master/cluster)
-  - [kubernetes/test/e2e/framework](https://github.com/kubernetes/kubernetes/tree/master/test/e2e)
-  - [kubernetes/test/conformance/image/go-runner](https://github.com/kubernetes/kubernetes/tree/master/test/conformance/image/go-runner)
+The existing Sonobuoy e2e plugin already provides a vast number of tests that could be adapted or reused for the SCS project.
+
+If these e2e tests are to be reused in a customized structure, a framework like [ginkgo][ginkgo] must be used as it is provided by the Kubernetes e2e test infrastructure.
+This could use the implementation of the build process responsible for the Docker image containing the e2e tests. The setup could be copied from [kubernetes/test/conformance/image][conformance-image] and adapted to the projects requirements.
+The mentioned build process would use the following files from the Kubernetes repository:
+- [kubernetes/cluster](https://github.com/kubernetes/kubernetes/tree/master/cluster)
+- [kubernetes/test/e2e/framework](https://github.com/kubernetes/kubernetes/tree/master/test/e2e)
+- [kubernetes/test/conformance/image/go-runner](https://github.com/kubernetes/kubernetes/tree/master/test/conformance/image/go-runner)
 
 
 PROS: