From 28c7a312af84f86c190dcfa91b0ed80f1107794e Mon Sep 17 00:00:00 2001
From: Able Lv <26692080+able8@users.noreply.github.com>
Date: Sun, 22 Oct 2023 18:49:50 +0800
Subject: [PATCH] Fixed a typo on page "Create an External Load Balancer"

Replace `_NumNodes` with `NumNodes`
---
 .../access-application-cluster/create-external-load-balancer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md
index d0ac36881a..6c0c758467 100644
--- a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md
+++ b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md
@@ -164,7 +164,7 @@ With each target weighted equally in terms of sending traffic to Nodes, external
 traffic is not equally load balanced across different Pods. The external load balancer
 is unaware of the number of Pods on each node that are used as a target.
 
-Where `NumServicePods <<  _NumNodes` or `NumServicePods >> NumNodes`, a fairly close-to-equal
+Where `NumServicePods <<  NumNodes` or `NumServicePods >> NumNodes`, a fairly close-to-equal
 distribution will be seen, even without weights.
 
 Internal pod to pod traffic should behave similar to ClusterIP services, with equal probability across all pods.