diff --git a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
index 51e31937e..ebdfdbbea 100644
--- a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
+++ b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
@@ -33,10 +33,10 @@ Additionally, the tests would need to be able to run inside a pod in the K8s clu
 
 ## Design Considerations
 
-Among the different ways to create a Sonobuoy plugin, there are three potential approaches that might work best for us.
-These are described in more detail below, where we discuss the pros and cons of each approach.
-One of these three approaches must be chosen for implementation.
-For the purposes of the investigation and the preparation of this decision record, there are examples(proof of work) for each different approach.
+There are different approaches to create a Sonobuoy plugin, which are discussed below in order to find a best practice for the SCS project.
+The documented approaches show one example each in order to give a better representation to the reader.
+
+Sonobuoy provides plugin examples in the repository [https://github.com/vmware-tanzu/sonobuoy-plugins][sonobuoy-plugins-repo], which are referenced throughout this section.
 
 #### _Option 1_ GO [1]: Pick framework from the Sonobuoy plugin examples