diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c21c371002..d7a73ec83b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -46,7 +46,7 @@ In the process of submitting your PRs, please read and abide by the template pro
 
 1. Provide Proof Manifests allowing the maintainers and other contributors to verify your changes without requiring they understand the nuances of all your code.
 2. For new or changed functionality, this typically requires documentation and so raise a corresponding issue (or, better yet, raise a separate PR) on the [documentation repository](https://github.com/kyverno/website).
-3. Test your change with the [Kyverno CLI](https://kyverno.io/docs/kyverno-cli/) and provide a test manifest in the proper format. If your feature/fix does not work with the CLI, a separate issue requesting CLI support must be made. For changes which can be tested as an end user, we require conformance/e2e tests by using the `kuttl` tool. See [here](https://github.com/kyverno/kyverno/tree/main/test/conformance/kuttl/README.md) for a specific guide on how and when to write these tests.
+3. Test your change with the [Kyverno CLI](https://kyverno.io/docs/kyverno-cli/) and provide a test manifest in the proper format. If your feature/fix does not work with the CLI, a separate issue requesting CLI support must be made. For changes which can be tested as an end user, we require conformance/e2e tests by using the `chainsaw` tool. See [here](https://github.com/kyverno/kyverno/tree/main/test/conformance/chainsaw/README.md) for a specific guide on how and when to write these tests.
 4. Indicate which release this PR is triaged for (maintainers). This step is important especially for the documentation maintainers in order to understand when and where the necessary changes should be made.
 
 #### How to Create a PR
diff --git a/test/conformance/chainsaw/mutate/e2e/jmespath-logic/README.md b/test/conformance/chainsaw/mutate/e2e/jmespath-logic/README.md
index 3b283f1498..506b6412d5 100644
--- a/test/conformance/chainsaw/mutate/e2e/jmespath-logic/README.md
+++ b/test/conformance/chainsaw/mutate/e2e/jmespath-logic/README.md
@@ -1,6 +1,6 @@
 ## Description
 
-This is test migrated from e2e which roughly tests that mutations are successful when the value of key being mutated contains both a context variable as well as a context variable plus additional JMESPath filtering in that variable reference. The test migrated here to kuttl represents a condensed version of the original test to eliminate minor redundancy.
+This is test migrated from e2e which roughly tests that mutations are successful when the value of key being mutated contains both a context variable as well as a context variable plus additional JMESPath filtering in that variable reference. The test migrated here to chainsaw represents a condensed version of the original test to eliminate minor redundancy.
 
 ## Expected Behavior
 
diff --git a/test/conformance/chainsaw/verifyImages/clusterpolicy/standard/configmap-context-lookup/README.md b/test/conformance/chainsaw/verifyImages/clusterpolicy/standard/configmap-context-lookup/README.md
index 73e0b53bb4..55fc673559 100644
--- a/test/conformance/chainsaw/verifyImages/clusterpolicy/standard/configmap-context-lookup/README.md
+++ b/test/conformance/chainsaw/verifyImages/clusterpolicy/standard/configmap-context-lookup/README.md
@@ -2,7 +2,7 @@
 
 The configmap context lookup uses informer's cache internally, the background processing should use the same to resolve configmap context without crashing Kyverno.
 
-This is the second test for configmap lookup, see `test/conformance/kuttl/validate/clusterpolicy/standard/audit/configmap-context-lookup/README.md` for another.
+This is the second test for configmap lookup, see `test/conformance/chainsaw/validate/clusterpolicy/standard/audit/configmap-context-lookup/README.md` for another.
 
 ## Expected Behavior