Update content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md

Co-authored-by: Nate W <natew@cncf.io>

Author: ArushKachru

content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md

@@ -211,7 +211,7 @@ The support for UDP protocol is tracked in
 
 Access to `kubectl port-forward` is controlled by Kubernetes authorization mechanisms like {{< glossary_tooltip text="Role-Based Access Control (RBAC)" term_id="rbac" >}}. Authorization is enforced by the Kubernetes API server, not by the `kubectl` client.
 
-To use `kubectl port-forward`, a user must have permission to access the target resource (for example, a Pod or Service) and the `portforward` subresource. Typical required permissions include `get` on pods and `create` on `pods/portforward`.
+To use `kubectl port-forward`, a user must have permission to access the target resource (for example, a Pod or Service) and the `portforward` subresource. Typical required permissions include `get` on `pods` and `create` on `pods/portforward`.
 
 Cluster administrators should carefully restrict these permissions, as port-forwarding can provide direct network access to workloads and may bypass network-level controls.