From 3e3de65859e0e4c4df2073ae9f8991a38b3449fb Mon Sep 17 00:00:00 2001 From: alec Date: Mon, 31 Aug 2020 17:21:32 +0900 Subject: [PATCH] Update endpoint-slices.md Fix a typo --- .../en/docs/concepts/services-networking/endpoint-slices.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/endpoint-slices.md b/content/en/docs/concepts/services-networking/endpoint-slices.md index 5f2522ae7e..3a2d622fc4 100644 --- a/content/en/docs/concepts/services-networking/endpoint-slices.md +++ b/content/en/docs/concepts/services-networking/endpoint-slices.md @@ -114,8 +114,8 @@ of the labels with the same names on the corresponding Node. Most often, the control plane (specifically, the endpoint slice {{< glossary_tooltip text="controller" term_id="controller" >}}) creates and manages EndpointSlice objects. There are a variety of other use cases for -EndpointSlices, such as service mesh implementations, that could result in othe -rentities or controllers managing additional sets of EndpointSlices. +EndpointSlices, such as service mesh implementations, that could result in other +entities or controllers managing additional sets of EndpointSlices. To ensure that multiple entities can manage EndpointSlices without interfering with each other, Kubernetes defines the