remove "bitcoin" language

value/value.md

@@ -85,12 +85,12 @@ Currently, there can be only a single copy of this element at each level.
 
 #### Explanation:
 
-Using Bitcoin Lightning as an example, the `type` would be "lightning".  Various possible `type` values will be kept
+Using Lightning as an example, the `type` would be "lightning".  Various possible `type` values will be kept
 in a slug list [here](valueslugs.txt).  This is the only type currently in active use.  Others are under development
 and will be added to the list as they see some measure of adoption, or at least a working example to prove viability.
 
 The `method` attribute is used to indicate a sub-protocol to use within the given `type`.  Again, returning to
-Bitcoin Lightning as an example, the `method` would be "keysend".  Normally, a Lightning payment requires an invoice
+Lightning as an example, the `method` would be "keysend".  Normally, a Lightning payment requires an invoice
 to be generated by the payee in order to fulfill a transaction.  The "keysend" protocol of Lightning allows payments
 to be streamed to what is, essentially, an open invoice.  Other cryptocurrencies may have a similar protocol that
 would be used here.  If not, a value of "default" should be given.
@@ -251,7 +251,7 @@ they will spend and charge.
 The value block is designed to be flexible enough to handle most any cryptocurrency, and even fiat currencies with a given
 API that exposes a compatible process.
 
-Currently, development is centered fully on [Bitcoin Lightning](https://github.com/lightningnetwork) using the "keysend" protocol.  Keysend allows for push
+Currently, development is centered fully on [Lightning](https://github.com/lightningnetwork) using the "keysend" protocol.  Keysend allows for push
 based payments without the recipient needing to generate an invoice to receive them.
 
 <br>