diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index 2d4ec69999..465dd1b1a0 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -342,17 +342,16 @@ syscalls. Here seccomp has been instructed to error on any syscall by setting
 ability to do anything meaningful. What you really want is to give workloads
 only the privileges they need.
 
-Clean up that Pod and Service before moving to the next section:
+Clean up that Pod before moving to the next section:
 
 ```shell
-kubectl delete service violation-pod --wait
 kubectl delete pod violation-pod --wait --now
 ```
 
 ## Create Pod with seccomp profile that only allows necessary syscalls
 
-If you take a look at the `fine-pod.json`, you will notice some of the syscalls
-seen in the first example where the profile set `"defaultAction":
+If you take a look at the `fine-grained.json` profile, you will notice some of the syscalls
+seen in syslog of the first example where the profile set `"defaultAction":
 "SCMP_ACT_LOG"`. Now the profile is setting `"defaultAction": "SCMP_ACT_ERRNO"`,
 but explicitly allowing a set of syscalls in the `"action": "SCMP_ACT_ALLOW"`
 block. Ideally, the container will run successfully and you will see no messages