Configuration API for v1.23

content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md

@@ -76,7 +76,7 @@ to customize the behavior of your scheduler implementation. This configuration h
 the `kube-scheduler` during initialization with the `--config` option. The `my-scheduler-config` ConfigMap stores the configuration file. The Pod of the`my-scheduler` Deployment mounts the `my-scheduler-config` ConfigMap as a volume.
 
 In the aforementioned Scheduler Configuration, your scheduler implementation is represented via
-a [KubeSchedulerProfile](/docs/reference/config-api/kube-scheduler-config.v1beta2/#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerProfile).
+a [KubeSchedulerProfile](/docs/reference/config-api/kube-scheduler-config.v1beta3/#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerProfile).
 {{< note >}}
 To determine if a scheduler is responsible for scheduling a specific Pod, the `spec.schedulerName` field in a 
 PodTemplate or Pod manifest must match the `schedulerName` field of the `KubeSchedulerProfile`.
@@ -89,7 +89,7 @@ Also, note that you create a dedicated service account `my-scheduler` and bind t
 Please see the
 [kube-scheduler documentation](/docs/reference/command-line-tools-reference/kube-scheduler/) for
 detailed description of other command line arguments and
-[Scheduler Configuration reference](https://kubernetes.io/docs/reference/config-api/kube-scheduler-config.v1beta2/) for
+[Scheduler Configuration reference](/docs/reference/config-api/kube-scheduler-config.v1beta3/) for
 detailed description of other customizable `kube-scheduler` configurations.
 
 ## Run the second scheduler in the cluster