From 434dae9ad7e397405f9b335f3637b87dd4c2894f Mon Sep 17 00:00:00 2001
From: divyabhushan <divya_bhushan@hotmail.com>
Date: Sat, 23 May 2020 14:38:59 +0200
Subject: [PATCH] Linked entrypoint command to the right page#21139

Reference issue: https://github.com/kubernetes/website/issues/21139
File modified: content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md
Line no: 122
---
 .../docs/tasks/access-application-cluster/web-ui-dashboard.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md b/content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md
index 0069334214..88132f5218 100644
--- a/content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md
+++ b/content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md
@@ -119,7 +119,7 @@ track=stable
 
 - **CPU requirement (cores)** and **Memory requirement (MiB)**: You can specify the minimum [resource limits](/docs/tasks/configure-pod-container/limit-range/) for the container. By default, Pods run with unbounded CPU and memory limits.
 
-- **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/user-guide/containers/#containers-and-commands). You can use the command options and arguments to override the default.
+- **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/tasks/inject-data-application/define-command-argument-container/). You can use the command options and arguments to override the default.
 
 - **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.