From b78d6dceb4d50bb8ce13e204b58d3e75af1d1f42 Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Fri, 10 Jan 2020 18:17:37 -0500 Subject: [PATCH] axe two stray words in service.md (#18160) changes for #14526 had either a stray "for a" or missed "service" as in "for a service". Since it's quite lengthy and "for a service" is unnecessary in service.md, I opted to removed it. --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index c57a03c14b..9479d02ec8 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -1015,7 +1015,7 @@ worth understanding. One of the primary philosophies of Kubernetes is that you should not be exposed to situations that could cause your actions to fail through no fault of your own. For the design of the Service resource, this means not making -you choose your own port number for a if that choice might collide with +you choose your own port number if that choice might collide with someone else's choice. That is an isolation failure. In order to allow you to choose a port number for your Services, we must