From 2bee3203bd252fb3ec260a13d17ca1dcb0c0cc68 Mon Sep 17 00:00:00 2001 From: Julian Y Date: Thu, 17 Dec 2020 00:40:19 -1000 Subject: [PATCH] Fix minor spelling (#211) --- docs/api.md | 2 +- docs/deployment.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/api.md b/docs/api.md index 7724e92..c1bcbba 100644 --- a/docs/api.md +++ b/docs/api.md @@ -5,7 +5,7 @@ - Success responses use HTTP status 200 and a JSON encoded body. - Error responses use HTTP status 500 to indicate a server error or 4XX to - indiciate a client error, and will include a JSON body describing the error. + indicate a client error, and will include a JSON body describing the error. For example: ```json diff --git a/docs/deployment.md b/docs/deployment.md index 6257dc6..eacb74d 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -23,12 +23,12 @@ it to derive a new addresses for receiving fee payments. ## Voting Servers A vspd deployment should have a minimum of three remote voting wallets. The -servers hosting these wallets should ideally be in geographically seperate +servers hosting these wallets should ideally be in geographically separate locations. Each voting server should be running an instance of dcrd and dcrwallet. The wallet on these servers should be completely empty and not used for any other -purpose. dcrwallet should be permenantly unlocked and have voting enabled +purpose. dcrwallet should be permanently unlocked and have voting enabled (`--enablevoting`). dcrwallet is also required to have the manual tickets option (`--manualtickets`) enabled which disables dcrwallet adding tickets arriving over the network. Without this option set, a user could reuse