mirror of
https://github.com/lightninglabs/lightning-terminal.git
synced 2026-08-13 12:33:36 +02:00
docs fix spelling issues (#862)
* Update WALKTHROUGH.md * Update accounts.md * Update config-lnd-integrated.md * Update WALKTHROUGH.md * Update accounts.md * Update config-lnd-integrated.md
This commit is contained in:
parent
f73b43a70e
commit
d7869cccc1
3 changed files with 4 additions and 4 deletions
|
|
@ -141,7 +141,7 @@ submitted.
|
|||
swap id, amount, and current status as a progress bar.
|
||||
|
||||
Swaps require on-chain transactions, so you will need to wait for confirmations before
|
||||
they will complete successfully. For more detailed information about the swap process,
|
||||
they will completed successfully. For more detailed information about the swap process,
|
||||
take a look at the
|
||||
[Loop Out In-depth](https://lightning.engineering/posts/2019-04-15-loop-out-in-depth/)
|
||||
blog post.
|
||||
|
|
|
|||
|
|
@ -15,12 +15,12 @@ amount of the node's channel balance.
|
|||
NOTE: An account's balance is purely virtual. If an account is created with an
|
||||
initial balance higher than the node's actual overall channel balance, that is
|
||||
equivalent to fractional reserve banking. Therefore, the user accepting an
|
||||
account restricted access enters a trust relationship with the node operator
|
||||
account-restricted access enters a trust relationship with the node operator
|
||||
that the promised balance of the account is actually spendable.
|
||||
|
||||
## How do accounts work?
|
||||
|
||||
The accounts systems is made possible thanks to the power of
|
||||
The accounts system is made possible thanks to the power of
|
||||
[macaroons](https://github.com/lightningnetwork/lnd/blob/master/docs/macaroons.md)
|
||||
and the [RPC middleware
|
||||
interceptor](https://github.com/lightningnetwork/lnd/blob/master/lnrpc/lightning.proto#L558)
|
||||
|
|
|
|||
|
|
@ -310,7 +310,7 @@ as it is the default directory (`~/.lnd` on Linux).
|
|||
|
||||
### Example `loop` command
|
||||
|
||||
This is where things get a bit tricky. Because as mentioned above, `loopd` also
|
||||
This is where things get a bit tricky, because as mentioned above, `loopd` also
|
||||
runs on the same gRPC server as `lnd`. That's why we have to both specify the
|
||||
`host:port` as well as the TLS certificate of `lnd`. But `loopd` verifies its
|
||||
own macaroon, so we have to specify that one from the `.loop` directory.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue