From 8b0014260d2296f431f8ad227090b98fad1d7fdf Mon Sep 17 00:00:00 2001 From: Aleg Malinovsky Date: Fri, 11 Sep 2020 15:24:51 +0300 Subject: [PATCH] missing a word it felt like the sentence was missing a word in that place --- content/en/docs/concepts/services-networking/endpoint-slices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/endpoint-slices.md b/content/en/docs/concepts/services-networking/endpoint-slices.md index 3a2d622fc4..b028139c1d 100644 --- a/content/en/docs/concepts/services-networking/endpoint-slices.md +++ b/content/en/docs/concepts/services-networking/endpoint-slices.md @@ -23,7 +23,7 @@ Endpoints. The Endpoints API has provided a simple and straightforward way of tracking network endpoints in Kubernetes. Unfortunately as Kubernetes clusters -and {{< glossary_tooltip text="Services" term_id="service" >}} have grown to handle +and {{< glossary_tooltip text="Services" term_id="service" >}} have grown to handle and send more traffic to more backend Pods, limitations of that original API became more visible. Most notably, those included challenges with scaling to larger numbers of