diff --git a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
index ebdfdbbea..9e9b1b6c3 100644
--- a/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
+++ b/Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
@@ -95,7 +95,7 @@ Sonobuoy makes it possible to write tests in Python and execute like other tests
 It would therefore be possible to keep on writing conformance tests in Python.
 
 This option would require a wrapper in order to make the tests scripts executable as Sonobuoy plugins.
-This wrapper, as mentioned earlier, would need to capture the collection of test results as well as the generation of the "Done" file after the test execution is finished. This could be managed by executing each test script in a sequential order. 
+This wrapper, as mentioned earlier, would need to capture the collection of test results as well as the generation of the "Done" file after the test execution is finished. This could be managed by executing each test script in a sequential order.
 
 The wrapper as well as the python tests and test framework could then be stored in a container image and uploaded to a registry in order to be usable by Sonobuoy within the k8s-cluster-api-provider.
 
@@ -116,8 +116,7 @@ CONS:
 
 ## Pros and Cons of Different Approaches
 
-
-### Provide Sonobuoy plug in image
+### Providing Sonobuoy plug in image
 
 There are two potential approaches for building the Sonobuoy images.
 They are completely independent of which of the above-mentioned frameworks is selected.
@@ -146,17 +145,23 @@ CONS
   - To be able to use the tests, you always have to build them first
 
 
-[k8s-e2e-tests]: https://github.com/kubernetes/kubernetes/tree/master/test/e2e
-[sonobuoy]: https://sonobuoy.io/
-[sonobuoy-plugins-repo]: https://github.com/vmware-tanzu/sonobuoy-plugins
-[sonobuoy-plugin-docu]: https://sonobuoy.io/docs/v0.57.0/plugins/)
-[e2e test plugin]: https://sonobuoy.io/docs/main/e2eplugin/
+## Decision
+
+> TODO: describe decision
+
+## Documents
+
+[k8s-e2e-tests](https://github.com/kubernetes/kubernetes/tree/master/test/e2e)
+[sonobuoy](https://sonobuoy.io/)
+[sonobuoy-plugins-repo](https://github.com/vmware-tanzu/sonobuoy-plugins)
+[sonobuoy-plugin-docu](https://sonobuoy.io/docs/v0.57.0/plugins/)
+[e2e test plugin](https://sonobuoy.io/docs/main/e2eplugin/)
 [k8s-api]: https://github.com/SovereignCloudStack/k8s-cluster-api-provider
-[e2e-skel]: https://github.com/vmware-tanzu/sonobuoy-plugins/tree/main/examples/e2e-skeleton
-[e2e-frame]: https://github.com/kubernetes-sigs/e2e-framework
-[e2e-frame-motivation]: https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#motivations
-[e2e-frame-goals]: https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#goals
-[e2e-frame-nongoals]: https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#non-goals
-[ginkgo]:https://onsi.github.io/ginkgo/
-[conformance-image]:https://github.com/kubernetes/kubernetes/tree/master/test/conformance/image
+[e2e-skel](https://github.com/vmware-tanzu/sonobuoy-plugins/tree/main/examples/e2e-skeleton)
+[e2e-frame](https://github.com/kubernetes-sigs/e2e-framework)
+[e2e-frame-motivation](https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#motivations)
+[e2e-frame-goals](https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#goals)
+[e2e-frame-nongoals](https://github.com/kubernetes-sigs/e2e-framework/blob/main/docs/design/README.md#non-goals)
+[ginkgo](https://onsi.github.io/ginkgo/)
+[conformance-image](https://github.com/kubernetes/kubernetes/tree/master/test/conformance/image)