From 8dd44465c3ff4cc2f77247816a403fb62f0e1c8f Mon Sep 17 00:00:00 2001 From: Ian Kelling Date: Sat, 15 Aug 2015 17:56:17 -0700 Subject: [PATCH] documentation: fix misspelled word --- Documentation/proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/proxy.md b/Documentation/proxy.md index ba0e1ceeb..bf2140f2e 100644 --- a/Documentation/proxy.md +++ b/Documentation/proxy.md @@ -1,6 +1,6 @@ ## Proxy -etcd can now run as a transparent proxy. Running etcd as a proxy allows for easily discovery of etcd within your infrastructure, since it can run on each machine as a local service. In this mode, etcd acts as a reverse proxy and forwards client requests to an active etcd cluster. The etcd proxy does not participant in the consensus replication of the etcd cluster, thus it neither increases the resilience nor decreases the write performance of the etcd cluster. +etcd can now run as a transparent proxy. Running etcd as a proxy allows for easily discovery of etcd within your infrastructure, since it can run on each machine as a local service. In this mode, etcd acts as a reverse proxy and forwards client requests to an active etcd cluster. The etcd proxy does not participate in the consensus replication of the etcd cluster, thus it neither increases the resilience nor decreases the write performance of the etcd cluster. etcd currently supports two proxy modes: `readwrite` and `readonly`. The default mode is `readwrite`, which forwards both read and write requests to the etcd cluster. A `readonly` etcd proxy only forwards read requests to the etcd cluster, and returns `HTTP 501` to all write requests.