multi: Fix typos [skip ci]

docs/INSTALL.md

@@ -459,7 +459,7 @@ below):
   `lnd` plus any application that consumes the RPC could cause `lnd` to miss
   crucial updates from the backend.
 - The default fee estimate mode in `bitcoind` is CONSERVATIVE. You can set
-  `bitcoind.estimatemode=ECONOMICAL` to change it into ECONOMICAL. Futhermore,
+  `bitcoind.estimatemode=ECONOMICAL` to change it into ECONOMICAL. Furthermore,
   if you start `bitcoind` in `regtest`, this configuration won't take any effect.
 
 

docs/MAKEFILE.md

@@ -179,7 +179,7 @@ Arguments:
 
 `unit-cover`
 ------------
-Runs the unit test suite with test coverage, compiling the statisitics in
+Runs the unit test suite with test coverage, compiling the statistics in
 `profile.cov`.
 
 Arguments:

docs/code_contribution_guidelines.md

@@ -12,7 +12,7 @@
    1. [Code Spacing](#code-spacing)
    1. [Protobuf Compilation](#protobuf-compilation)
    1. [Additional Style Constraints On Top of gofmt](#additional-style-constraints-on-top-of-gofmt)
-   1. [Pointing to Remote Dependant Branches in Go Modules](#pointing-to-remote-dependant-branches-in-go-modules)
+   1. [Pointing to Remote Dependent Branches in Go Modules](#pointing-to-remote-dependent-branches-in-go-modules)
    1. [Use of Log Levels](#use-of-log-levels)
 5. [Code Approval Process](#code-approval-process)
    1. [Code Review](#code-review)
@@ -546,7 +546,7 @@ to `gofmt` we've opted to enforce the following style guidelines.
 log and error messages, committers should attempt to minimize the number of
 lines utilized, while still adhering to the 80-character column limit.
 
-## Pointing to Remote Dependant Branches in Go Modules
+## Pointing to Remote Dependent Branches in Go Modules
 
 It's common that a developer may need to make a change in a dependent project
 of `lnd` such as `btcd`, `neutrino`, `btcwallet`, etc. In order to test changes

docs/etcd.md

@@ -2,7 +2,7 @@
 
 With the recent introduction of the `kvdb` interface LND can support multiple
 database backends allowing experimentation with the storage model as well as
-improving robustness trough eg. replicating essential data.
+improving robustness through eg. replicating essential data.
 
 Building on `kvdb` in v0.11.0 we're adding experimental [etcd](https://etcd.io)
 support to LND. As this is an unstable feature heavily in development, it still
@@ -71,7 +71,7 @@ db.etcd.keyfile=/home/user/etcd/bin/default.etcd/fixtures/client/key.pem
 db.etcd.insecure_skip_verify=true
 ```
 
-Optionally users can specifiy `db.etcd.user` and `db.etcd.pass` for db user
+Optionally users can specify `db.etcd.user` and `db.etcd.pass` for db user
 authentication. If the database is shared, it is possible to separate our data
 from other users by setting `db.etcd.namespace` to an (already existing) etcd
 namespace. In order to test without TLS, users are able to set `db.etcd.disabletls`

docs/leader_election.md

@@ -1,4 +1,4 @@
-# Increasing LND reliablity by clustering
+# Increasing LND reliability by clustering
 
 Normally LND nodes use the embedded bbolt database to store all important states.
 This method of running has been proven to work well in a variety of environments,
@@ -9,7 +9,7 @@ do updates and be more resilient to datacenter failures.
 It is now possible to store all essential state in a replicated etcd DB and to
 run multiple LND nodes on different machines where only one of them (the leader) 
 is able to read and mutate the database. In such setup if the leader node fails
-or decomissioned, a follower node will be elected as the new leader and will
+or decommissioned, a follower node will be elected as the new leader and will
 quickly come online to minimize downtime.
 
 The leader election feature currently relies on etcd to work both for the election

docs/recovery.md

@@ -286,7 +286,7 @@ the same format.
 
 #### Streaming Updates via `SubscribeChannelBackups`
 
-Using the gRPC interace directly, [a new call:
+Using the gRPC interface directly, [a new call:
 `SubscribeChannelBackups`](https://api.lightning.community/#subscribechannelbackups).
 This call allows users to receive a new notification each time the underlying
 SCB state changes. This can be used to implement more complex backup

docs/rest/websockets.md

@@ -53,7 +53,7 @@ ws.onmessage = function (event) {
     console.log(JSON.parse(event.data).result);
 }
 ws.onerror = function (event) {
-    // An error occured, let's log it to the console.
+    // An error occurred, let's log it to the console.
     console.log(event);
 }
 ```