diff --git a/docs/content/en/docs/pipeline/operation.md b/docs/content/en/docs/pipeline/operation.md
index d2786ca70..bab2733a0 100644
--- a/docs/content/en/docs/pipeline/operation.md
+++ b/docs/content/en/docs/pipeline/operation.md
@@ -177,6 +177,7 @@ Kurator's CLI provides a very convenient way to view the execution status of a p
 which user can directly list all the pipeline execution and access all task execution logs with a specific command.
 
 You can view the execution instance of the currently triggered pipeline using the following command.
+Note: You need to specify the kubeconfig file to use via the `--kubeconfig` flag in the command line, even if you are running the Kurator Pipeline in a single cluster environment.
 
 ```console
 $ kurator pipeline execution list  -n kurator-pipeline  --kubeconfig /root/.kube/kurator-host.config
diff --git a/docs/content/en/docs/pipeline/setting.md b/docs/content/en/docs/pipeline/setting.md
index 3e5a65231..5fb606448 100644
--- a/docs/content/en/docs/pipeline/setting.md
+++ b/docs/content/en/docs/pipeline/setting.md
@@ -27,6 +27,8 @@ Since the first task in a pipeline often involves pulling code from a Git reposi
 This can be done by creating a Kubernetes secret containing the authentication details. Use the following command to create this secret:
 
 ```console
+kubectl create ns kurator-pipeline
+
 kubectl create secret generic git-credentials \
   --namespace=kurator-pipeline \
   --from-literal=.gitconfig=$'[credential "https://github.com"]\n\thelper = store' \