From baa9b17cacebe6de8b11c55b84676b7a1f9c8a38 Mon Sep 17 00:00:00 2001 From: ppggff Date: Fri, 19 Jan 2018 17:53:18 +0800 Subject: [PATCH] Documentation/learning: Fix a typo --- Documentation/learning/why.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/learning/why.md b/Documentation/learning/why.md index 29a86b86c..d11fe54a5 100644 --- a/Documentation/learning/why.md +++ b/Documentation/learning/why.md @@ -1,6 +1,6 @@ # etcd versus other key-value stores -The name "etcd" originated from two ideas, the unix "/etc" folder and "d"istibuted systems. The "/etc" folder is a place to store configuration data for a single system whereas etcd stores configuration information for large scale distributed systems. Hence, a "d"istributed "/etc" is "etcd". +The name "etcd" originated from two ideas, the unix "/etc" folder and "d"istributed systems. The "/etc" folder is a place to store configuration data for a single system whereas etcd stores configuration information for large scale distributed systems. Hence, a "d"istributed "/etc" is "etcd". etcd is designed as a general substrate for large scale distributed systems. These are systems that will never tolerate split-brain operation and are willing to sacrifice availability to achieve this end. etcd stores metadata in a consistent and fault-tolerant way. An etcd cluster is meant to provide key-value storage with best of class stability, reliability, scalability and performance.