stakey/vspd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix minor spelling (#211)

Browse Source
This commit is contained in:
Julian Y 2020-12-17 00:40:19 -10:00 committed by GitHub
parent 2a096d81f9
commit 2bee3203bd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api.md
View File

@ -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

4
docs/deployment.md
View File

@ -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