diff --git a/book/src/become-a-validator-source.md b/book/src/become-a-validator-source.md
index dbc9717f6..3b8a78a21 100644
--- a/book/src/become-a-validator-source.md
+++ b/book/src/become-a-validator-source.md
@@ -72,9 +72,9 @@ slot: 16835, ...
 
 ## 4. Generate your validator key
 
-First, [create a wallet](./wallet-create) that can be used to generate
+First, [create a wallet](./wallet-create.md) that can be used to generate
 validator keys. Then, from that wallet [create a
-validator](./validator-create). A two-step example follows:
+validator](./validator-create.md). A two-step example follows:
 
 ### 4.1 Create a Wallet
 
@@ -117,7 +117,7 @@ used to restore your validator if there is a data loss.
 Create a validator from the wallet with:
 
 ```bash
-lighthouse account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass
+lighthouse account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass --count 1
 ```
 
 The output will look like this:
diff --git a/book/src/faq.md b/book/src/faq.md
index 5442d1b43..3839d1ecd 100644
--- a/book/src/faq.md
+++ b/book/src/faq.md
@@ -46,13 +46,13 @@ period. In times of very, very severe network issues, the network may even fail
 to vote in new Eth1 blocks, stopping all new validator deposits!
 
 > Note: you can see the list of validators included in the beacon chain using
-> our REST API: [/beacon/validators/all](./http_beacon.md#beaconvalidatorsall)
+> our REST API: [/beacon/validators/all](./http/beacon.md#beaconvalidatorsall)
 
 ### 2. Waiting for a validator to be activated
 
 If a validator has provided an invalid public key or signature, they will
 _never_ be activated or even show up in
-[/beacon/validators/all](https://lighthouse-book.sigmaprime.io/http_beacon.html#beaconvalidatorsall).
+[/beacon/validators/all](./http/beacon.html#beaconvalidatorsall).
 They will simply be forgotten by the beacon chain! But, if those parameters were
 correct, once the Eth1 delays have elapsed and the validator appears in the
 beacon chain, there's _another_ delay before the validator becomes "active"