From 64723464ae6bd31f718cf86f753d6988d18c2210 Mon Sep 17 00:00:00 2001 From: Quanah Gibson-Mount Date: Tue, 22 Feb 2022 17:09:54 +0000 Subject: [PATCH] ITS#9780 - Fix typos --- doc/guide/admin/loadbalancer.sdf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guide/admin/loadbalancer.sdf b/doc/guide/admin/loadbalancer.sdf index b474d63c7a..9bbd4b4ef5 100644 --- a/doc/guide/admin/loadbalancer.sdf +++ b/doc/guide/admin/loadbalancer.sdf @@ -65,7 +65,7 @@ will wait 5000ms (5 seconds) before making another attempt to that server. When a new Bind request comes from a client, it will be allocated to one of the available {{bind connections}}, each of which can only carry one request at a -time. For other reqests that need to be passed on to the backends, backends are +time. For other requests that need to be passed on to the backends, backends are considered in order: * if the number of pending/in-flight for that backend is at or above 10, it is skipped @@ -118,7 +118,7 @@ Two alternative selection strategies have been implemented: neither backend can be used, selection falls back to the regular strategy used by the roundrobin backend -The {{weighted}} tier might be appropritate when servers have differing load +The {{weighted}} tier might be appropriate when servers have differing load capacity. Due to its reinforced self-limiting feedback, the {{bestof}} tier might be appropriate in large scale environments where each backend's capacity/latency fluctuates widely and rapidly.