Minor updates to website documentation

content/en/docs/components/central-dash/customize.md

@@ -17,7 +17,7 @@ For example, the below image shows the Kubeflow Central Dashboard with a custom
 
 ## Central Dashboard ConfigMap
 
-The Kubeflow Central Dashboard is configured using a Kubernetes ConfigMap.
+The Kubeflow Central Dashboard is configured using a Kubernetes [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/).
 
 The `CD_CONFIGMAP_NAME` environment variable on the central-dashboard Deployment specifies the name of the ConfigMap (`centraldashboard-config` by default).
 
@@ -121,7 +121,7 @@ data:
 
 ### Create VirtualService
 
-If you have a non-Kubeflow application running on the cluster, you may expose it through the Kubeflow Central Dashboard by creating a `VirtualService` on the Kubeflow Istio Gateway.
+If you have a non-Kubeflow application running on the cluster, you may expose it through the Kubeflow Central Dashboard by creating a [`VirtualService`](https://istio.io/latest/docs/reference/config/networking/virtual-service/) on the Kubeflow Istio Gateway.
 To do this, your app must have an injected Istio sidecar and be exposed as a Kubernetes Service.
 
 For example, the below `VirtualService` exposes `Service/my-app` from the `my-namespace` namespace on the Kubeflow Istio Gateway under the path `/my-app/`:

content/en/docs/components/central-dash/profiles.md

@@ -6,13 +6,17 @@ weight = 20
 
 ## What is a Kubeflow Profile?
 
-A Profile is a Kubernetes CRD introduced by Kubeflow that wraps a Kubernetes Namespace.
+A Kubeflow Profile is a [Kubernetes CRD](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) introduced by Kubeflow that wraps a Kubernetes [Namespace](https://kubernetes.io/docs/tasks/administer-cluster/namespaces-walkthrough/).
+
+
+
 Profile are owned by a single user, and can have multiple contributors with view or modify access.
 The owner of a profile can add and remove contributors (this can also be done by the cluster administrator).
 
 Profiles and their child Namespaces are reconciled by the [Kubeflow Profile Controller](https://github.com/kubeflow/kubeflow/tree/master/components/profile-controller) and contributors (not owners) are managed by the [Kubeflow Access Management API (KFAM)](https://github.com/kubeflow/kubeflow/tree/master/components/access-management).
 
-## Central Dashboard
+
+## Profiles in the Central Dashboard
 
 Select the active profile with the drop-down found in the top bar of Kubeflow Central Dashboard.
 Most Kubeflow components use the active profile to determine which resources to display, and what permissions to grant.