Update k8s-best-practices-platform-upgrade.adoc

redhat-best-practices-for-k8s · Oct 24, 2024 · a3d1b7a · a3d1b7a
1 parent b54719f
commit a3d1b7a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/modules/k8s-best-practices-platform-upgrade.adoc b/modules/k8s-best-practices-platform-upgrade.adoc
@@ -52,7 +52,7 @@ spec:
       app: db
 ----
 
-See link:https://docs.openshift.com/container-platform/latest/scalability_and_performance/index.html[Recommended performance and scalability practices].
+See link:https://docs.openshift.com/container-platform/latest/scalability_and_performance/index.html[recommended performance and scalability practices].
 
 By default, only one machine is allowed to be unavailable when applying the kubelet-related configuration to the available worker nodes. For a large cluster, it can take a long time for the configuration change to be reflected. At any time, you can adjust the number of machines that are updating to speed up the process.