diff options
| author | Micah Anderson <micah@riseup.net> | 2016-04-14 15:25:05 -0400 |
|---|---|---|
| committer | Micah Anderson <micah@riseup.net> | 2016-04-14 15:25:05 -0400 |
| commit | fd64ab5336a335569b828e8b6d16a0bb5137f371 (patch) | |
| tree | c3f05ccce24ede6ae9a43015e8d23f3ef2b047cf | |
| parent | 1e8143db7372b14bafbeaababe80fb50aa3409b0 (diff) | |
fix typo
| -rw-r--r-- | pages/docs/platform/services/couchdb.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pages/docs/platform/services/couchdb.md b/pages/docs/platform/services/couchdb.md index 7bcc48c..2263971 100644 --- a/pages/docs/platform/services/couchdb.md +++ b/pages/docs/platform/services/couchdb.md @@ -152,7 +152,7 @@ If you add a node, or remove one node from the cluster, Here are the steps needed to replace BigCouch with CouchDB. -At the end of this process, you will have just *one* noe with `services` property equal to `couchdb`. If you had a BigCouch cluster before, you will be removing all but one of those machines to consolidate them into one couchdb machine. +At the end of this process, you will have just *one* node with `services` property equal to `couchdb`. If you had a BigCouch cluster before, you will be removing all but one of those machines to consolidate them into one couchdb machine. 1. if you have multiple nodes with the couchdb service on them, pick one of them to be your couchdb server, and remove the service from the others. If these machines were only doing couchdb, you can remove the nodes completely with `leap node rm <nodename>` and then you can decommission the servers |