Fix typos

Author: vuittont60

lightning-network-tools/lnd/etcd.md

@@ -57,7 +57,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 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` flag to `true`.
+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` flag to `true`.
 
 ## Migrating existing channel.db to etcd
 

lightning-network-tools/lnd/lnd.conf.md

@@ -1150,7 +1150,7 @@ A sample configuration file [can be found here](https://github.com/lightningnetw
 
 [routerrpc]
 
-; Probability estimator used for pathfinding. Two estimators are availabe:
+; Probability estimator used for pathfinding. Two estimators are available:
 ; apriori and bimodal.
 ; Note that the bimodal estimator is experimental.
 ; Default:

lightning-network-tools/lnd/recovery.md

@@ -216,7 +216,7 @@ As shown above, a user can either: specify a specific channel to backup, backup
 
 **Streaming Updates via SubscribeChannelBackups**
 
-Using the gRPC interace 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 schemes, compared to the file system notification based approach.
+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 schemes, compared to the file system notification based approach.
 
 #### Recovering Using SCBs
 

lightning-network-tools/pool/batch_execution.md

@@ -22,7 +22,7 @@ Note that the trader can reject signing the batch for any reason, even when the
 
 ### Batch Publication
 
-When all participating traders have signed their inputs in the Batch Execution Transaction, the auctioneer can sign the final input and broadcast the transaction. This transaction can be large, and serve as the funding transaction for potentially hundres of channels! The participating traders only pay chain fees for their inputs and outputs in the transaction, so everybody is saving substantially on fees compared to individually funding channels.
+When all participating traders have signed their inputs in the Batch Execution Transaction, the auctioneer can sign the final input and broadcast the transaction. This transaction can be large, and serve as the funding transaction for potentially hundreds of channels! The participating traders only pay chain fees for their inputs and outputs in the transaction, so everybody is saving substantially on fees compared to individually funding channels.
 
 ## Batched Uniform-Price Clearing
 

lightning-network-tools/pool/orders.md

@@ -252,7 +252,7 @@ $ pool orders cancel order_nonce
 
 ## Match with specific nodes
 
-To match with a specific node, or to limit your match to a set of nodes you may use the `allowed_node_id` flag. Alternatively you can also specifiy nodes you do not want to match with using the `not_allowed_node_id` option.
+To match with a specific node, or to limit your match to a set of nodes you may use the `allowed_node_id` flag. Alternatively you can also specify nodes you do not want to match with using the `not_allowed_node_id` option.
 
 ```
 $ pool order submit bid --not_allowed_node_id 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d

the-lightning-network/multihop-payments/understanding-submarine-swaps.md

@@ -12,7 +12,7 @@ A submarine swap is a trade between on-chain and off-chain digital assets (i.e.b
 
 Without counterparty risk, submarine swaps can be performed without additional barriers such as background checks or contractual arrangements. Either, the two parties successfully swap their assets or the swap fails. But, at no point, is either side able to walk away with the other party’s funds.
 
-To achieve these trustless properties, the on-chain transaction makes use of the same hash time-locked contracts (HTLC) as the Lightning Network. Before on-chain BTC are transfered, the recipient of the Lightning transaction generates a preimage, a random 32-byte secret. This preimage is hashed and used to construct the HTLCs for both on- and off-chain payments.
+To achieve these trustless properties, the on-chain transaction makes use of the same hash time-locked contracts (HTLC) as the Lightning Network. Before on-chain BTC are transferred, the recipient of the Lightning transaction generates a preimage, a random 32-byte secret. This preimage is hashed and used to construct the HTLCs for both on- and off-chain payments.
 
 ### **1. Generate a bitcoin smart contract**
 

the-lightning-network/taproot-assets/taproot-assets-protocol.md

@@ -26,7 +26,7 @@ While a conventional transaction requires the entire script to be revealed, a Ta
 
 This makes it possible to create more complicated scripts without the added cost of submitting extra data to the blockchain in the keySpend path, and efficient verification of a pruned script data. In the context of Taproot Assets, it allows us to provably attach arbitrary data to a transaction without revealing this data on-chain.
 
-### Commiting to a hash: Taptweak
+### Committing to a hash: Taptweak
 
 We refer to a transaction that includes such arbitrary data as a commitment. Once the transaction has been included in a block, we have committed to this data and can no longer change or amend it.
 
@@ -120,7 +120,7 @@ Once we publish this transaction and have it confirmed on the bitcoin blockchain
 
 ### Asset proof
 
-The asset issuer can now selectively reveal what assets were created and to whom they were allotted. Most importantly, the issuer can prove to the recipient that an asset has been transfered to them, by revealing a specific asset proof, which contains the asset script as well as the path of the sparse Merkle sum tree with the recipient’s account as the key.
+The asset issuer can now selectively reveal what assets were created and to whom they were allotted. Most importantly, the issuer can prove to the recipient that an asset has been transferred to them, by revealing a specific asset proof, which contains the asset script as well as the path of the sparse Merkle sum tree with the recipient’s account as the key.
 
 The recipient can verify the partial sparse Merkle sum tree to recreate the script, tweak the issuer’s public key and verify that the genesis transaction exists on the blockchain, while the partial Merkle tree gives them assurance over the assets issued to them, as well as the total number of assets issued.