Fix pkill command for kubectl port-forward process termination

Author: VajiraPrabuddhaka

docs/getting-started/multi-cluster.mdx

@@ -373,7 +373,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --
 # Then access in browser at http://localhost:7007
 
 # To stop the port-forward when done:
-pkill -f "kubectl port-forward.*backstage-demo.*7007:7007"
+pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007"
 ```
 
 You can verify the portal is working correctly with curl:

docs/getting-started/single-cluster.mdx

@@ -317,7 +317,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 >
 # Then access in browser at http://localhost:7007
 
 # To stop the port-forward when done:
-pkill -f "kubectl port-forward.*backstage-demo.*7007:7007"
+pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007"
 ```
 
 You can verify the portal is working correctly with curl:

versioned_docs/version-v0.3.x/getting-started/multi-cluster.mdx

@@ -373,7 +373,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 --
 # Then access in browser at http://localhost:7007
 
 # To stop the port-forward when done:
-pkill -f "kubectl port-forward.*backstage-demo.*7007:7007"
+pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007"
 ```
 
 You can verify the portal is working correctly with curl:

versioned_docs/version-v0.3.x/getting-started/single-cluster.mdx

@@ -317,7 +317,7 @@ kubectl port-forward -n openchoreo-control-plane svc/backstage-demo 7007:7007 >
 # Then access in browser at http://localhost:7007
 
 # To stop the port-forward when done:
-pkill -f "kubectl port-forward.*backstage-demo.*7007:7007"
+pkill -f "kubectl.*port-forward.*backstage-demo.*7007:7007"
 ```
 
 You can verify the portal is working correctly with curl: