Fix issue of document link in some documents

content/en/docs/tasks/inject-data-application/podpreset.md

@@ -140,7 +140,7 @@ verify that the preset has been applied.
 
 ## ReplicaSet with Pod spec example
 
-This is an example to show that only Pod specs are modified by Pod presets. Other workload types 
+This is an example to show that only Pod specs are modified by Pod presets. Other workload types
 like ReplicaSets or Deployments are unaffected.
 
 Here is the manifest for the PodPreset for this example:
@@ -290,7 +290,7 @@ kubectl get pod website -o yaml
 You can see there is no preset annotation (`podpreset.admission.kubernetes.io`). Seeing no annotation tells you that no preset has not been applied to the Pod.
 
 However, the
-[PodPreset admission controller](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#podpreset)
+[PodPreset admission controller](/docs/reference/access-authn-authz/admission-controllers/#podpreset)
 logs a warning containing details of the conflict.
 You can view the warning using `kubectl`:
 
@@ -301,7 +301,7 @@ kubectl -n kube-system logs -l=component=kube-apiserver
 The output should look similar to:
 
 ```
-W1214 13:00:12.987884       1 admission.go:147] conflict occurred while applying podpresets: allow-database on pod:  err: merging volume mounts for allow-database has a conflict on mount path /cache: 
+W1214 13:00:12.987884       1 admission.go:147] conflict occurred while applying podpresets: allow-database on pod:  err: merging volume mounts for allow-database has a conflict on mount path /cache:
 v1.VolumeMount{Name:"other-volume", ReadOnly:false, MountPath:"/cache", SubPath:"", MountPropagation:(*v1.MountPropagationMode)(nil), SubPathExpr:""}
 does not match
 core.VolumeMount{Name:"cache-volume", ReadOnly:false, MountPath:"/cache", SubPath:"", MountPropagation:(*core.MountPropagationMode)(nil), SubPathExpr:""}
@@ -321,5 +321,3 @@ The output shows that the PodPreset was deleted:
 ```
 podpreset "allow-database" deleted
 ```
-
-