From cb6d23b186dfa17284affb6bd10d03e4b076f339 Mon Sep 17 00:00:00 2001 From: Eric Tune Date: Wed, 21 Jan 2015 13:28:35 -0800 Subject: [PATCH] Fix. --- docs/availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/availability.md b/docs/availability.md index b8085268cef..3f8db2b6ebf 100644 --- a/docs/availability.md +++ b/docs/availability.md @@ -126,7 +126,7 @@ calls for maximum 100 node clusters at v1.0 and maximum 1000 node clusters in th ## Working with multiple clusters -When you have multiple clusters, you would typically copies of a given service in each cluster and put each of those +When you have multiple clusters, you would typically create services with the same config in each cluster and put each of those service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer), so that failures of a single cluster are not visible to end users.