diff --git a/19_1_Verifying_Your_Lightning_Setup.md b/19_1_Verifying_Your_Lightning_Setup.md index 4e1b8d0..ab14bf4 100644 --- a/19_1_Verifying_Your_Lightning_Setup.md +++ b/19_1_Verifying_Your_Lightning_Setup.md @@ -265,7 +265,7 @@ Before you start playing with lightning, you should make sure that your aliases ## What's Next? -Continue "Understanding Your Lightning Setup" with [§18.2: Knowing Your Lightning Setup](18_2_Knowing_Your_lightning_Setup.md). +Continue "Understanding Your Lightning Setup" with [§19.2: Knowing Your Lightning Setup](19_2_Knowing_Your_lightning_Setup.md). ## Variant: Install from Ubuntu ppa diff --git a/19_2_Knowing_Your_lightning_Setup.md b/19_2_Knowing_Your_lightning_Setup.md index 7df003b..0650db2 100644 --- a/19_2_Knowing_Your_lightning_Setup.md +++ b/19_2_Knowing_Your_lightning_Setup.md @@ -334,6 +334,6 @@ The `~/.lightning` directory contains all of your files, while `lightning-cli he ## What's Next? -You're going to need to have a second Linode node to test out the actual payment of invoices. If you need support in setting one up, read [Interlude: Accessing a Second Lightning Node](18_2__Interlude_Accessing_a_Second_Lightning_Node.md). +You're going to need to have a second Linode node to test out the actual payment of invoices. If you need support in setting one up, read [Interlude: Accessing a Second Lightning Node](19_2__Interlude_Accessing_a_Second_Lightning_Node.md). Otherwise, continue "Understanding Your Lightning Setup" with [§19.3: Setting Up_a_Channel](19_3_Setting_Up_a_Channel.md). diff --git a/19_2__Interlude_Accessing_a_Second_Lightning_Node.md b/19_2__Interlude_Accessing_a_Second_Lightning_Node.md index e286c72..8b03a7a 100644 --- a/19_2__Interlude_Accessing_a_Second_Lightning_Node.md +++ b/19_2__Interlude_Accessing_a_Second_Lightning_Node.md @@ -52,7 +52,7 @@ They can then tell you their `id` (`03240a4878a9a64aea6c3921a434e573845267b86e89 ## Create a New c-lightning Node -However, for testing purposes, you probably want to have a second node under you own control. The easiest way to do so is to create a second c-lightning node on a new machine, using either Bitcoin Standup, per [§2.1](02_1_Setting_Up_a_Bitcoin-Core_VPS_with_StackScript.md) or compiling it by hand, per [§18.1](18_1_Verifying_Your_Lightning_Setup.md). +However, for testing purposes, you probably want to have a second node under you own control. The easiest way to do so is to create a second c-lightning node on a new machine, using either Bitcoin Standup, per [§2.1](02_1_Setting_Up_a_Bitcoin-Core_VPS_with_StackScript.md) or compiling it by hand, per [§19.1](19_1_Verifying_Your_Lightning_Setup.md). Once you have your node running, you can run `getinfo` to retrieve your information, as shown above. @@ -111,7 +111,7 @@ $ sudo cp $GOPATH/bin/lnd $GOPATH/bin/lncli /usr/bin Unlike with c-lightning, you will need to create a default config file for LND. -However first, you need to enable ZMQ on your Bitcoind, if you didn't already in [§15.3](15_3_Receiving_Bitcoind_Notifications_with_C.md). +However first, you need to enable ZMQ on your Bitcoind, if you didn't already in [§16.3](16_3_Receiving_Bitcoind_Notifications_with_C.md). This requires adding the following to your `~/.bitcoin/bitcoin.conf` file if it's not already there: ```