diff --git a/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc b/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc
index 19ccc70022b9..c0cd2d96ecfb 100644
--- a/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc
+++ b/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc
@@ -22,7 +22,12 @@ When executing `podman` commands as a non-root or non-privileged user, mounting
 
 . Open a shell prompt in the directory containing the `kubeconfig` file.
 +
-You provide the test image with a `kubeconfig` file in current directory and its related `$KUBECONFIG` environment variable, mounted through a volume. This allows the running container to use the `kubeconfig` file from inside the container.
+[NOTE]
+====
+You provide the test image with a `kubeconfig` file in current directory and its related `$KUBECONFIG` environment variable, mounted through a volume. This allows the running container to use the `kubeconfig` file from inside the container. 
+
+In the following command, your local `kubeconfig` is mounted to kubeconfig/kubeconfig in the cnf-tests container, which allows access to the cluster.
+====
 
 . To run the latency tests, run the following command, substituting variable values as appropriate:
 +
@@ -45,6 +50,8 @@ If the results exceed the latency threshold, the test fails.
 
 . Optional: Append `--ginkgo.timeout="24h"` flag to ensure the Ginkgo 2.0 test suite does not timeout before the latency tests complete.
 +
+Additional, and more targetted latency tests, are detailed in the following sections.
++
 [IMPORTANT]
 ====
 For valid results, the test should run for at least 12 hours.