From bbfae805942afe46a653c3844eb14b4b46f559ce Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Mon, 1 Jun 2015 11:27:39 +0200 Subject: [PATCH] fix typo: s/can not/cannot/ --- docs/services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/services.md b/docs/services.md index fe6ffa4f808..daa20f3fa04 100644 --- a/docs/services.md +++ b/docs/services.md @@ -6,7 +6,7 @@ Kubernetes [`Pods`](pods.md) are mortal. They are born and they die, and they are not resurrected. [`ReplicationControllers`](replication-controller.md) in particular create and destroy `Pods` dynamically (e.g. when scaling up or down or when doing rolling updates). While each `Pod` gets its own IP address, even -those IP addresses can not be relied upon to be stable over time. This leads to +those IP addresses cannot be relied upon to be stable over time. This leads to a problem: if some set of `Pods` (let's call them backends) provides functionality to other `Pods` (let's call them frontends) inside the Kubernetes cluster, how do those frontends find out and keep track of which backends are