From f89514f5e3eef2103a22d2e55a33d1d845ae14e2 Mon Sep 17 00:00:00 2001 From: Takashi Takebayashi Date: Mon, 15 Dec 2025 09:21:25 +0900 Subject: [PATCH] Fix typo: network lod balancer -> network load balancer --- articles/load-balancer/manage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/load-balancer/manage.md b/articles/load-balancer/manage.md index 182e6183e67fb..d7692ddfa1b4f 100644 --- a/articles/load-balancer/manage.md +++ b/articles/load-balancer/manage.md @@ -207,7 +207,7 @@ The following is displayed in the **Add an inbound NAT rule** creation page for | Current number of machines in backend pool | The displayed value is the number of machines in the selected backend pool, and for information only; you can't modify this value. | | Maximum number of machines in backend pool | Enter the maximum number of instances in the backend pool when scaling out. | | Backend port | Enter a port for traffic sent to on backend pool. | -| Protocol | Azure Load Balancer is a layer 4 network lod balancer.
Your options are: TCP or UDP. | +| Protocol | Azure Load Balancer is a layer 4 network load balancer.
Your options are: TCP or UDP. | | Enable TCP Reset | Load Balancer can send TCP resets to help create a more predictable application behavior on when the connection is idle.
Learn more about [TCP reset](load-balancer-tcp-reset.md) | | Idle timeout (minutes) | Keep a TCP or HTTP connection open without relying on clients to send keep-alive messages. | | Enable Floating IP | Some application scenarios prefer or require the same port to be used by multiple application instances on a single VM in the backend pool. If you want to reuse the backend port across multiple rules, you must enable [Floating IP](load-balancer-floating-ip.md) in the rule definition.|