updates manifest and copy (#43)

docs/instructions.md

@@ -2,7 +2,7 @@
 
 ## Dependencies
 
-LND on the Embassy requires a full archival Bitcoin node to function. Since your Embassy Bitcoin node is pruned by default, an additional service, Bitcoin Proxy, is also required.
+LND on the Embassy requires a full archival Bitcoin node to function. If you have enabled pruning for your bitcoin node, an additional service, Bitcoin Proxy, is also required.
 
 ## LND Config
 
@@ -32,15 +32,15 @@ Once your LND node is synced, it's time to open a channel. Opening a channel wit
 
 If you are looking for destinations for your first channel, we suggest you open a channel with the [Start9 HQ](025d28dc4c4f5ce4194c31c3109129cd741fafc1ff2f6ea53f97de2f58877b2295@64.225.19.231:9735) node, which is already very well connected.
 
-It is not recommended to open a channel less than 100,000 satoshi, or .001 BTC, or $50 USD in today's prices. Anything less, and it's possible that the cost to open and close the channel might approach the size of the channel itself. The bigger the channel you open, the more outbound liquidity you will have, which means you have more spending power on the network. In this tutorial, we are going to open a channel of 2,000,000 satoshi. When opening a channel with Start9 HQ, we ask that you make it a private channel, meaning it will not display publicly on network graph. The reason for this is that unless you plan to be a very active Lightning Node Operator, having public channels decreases not only the reliability of your node but also hurts Start9's ability to route payments for you. If you do intend to be a serious node operator, we require that your channel be for a minimum of 5,000,000 sats. Please contact us in one of our community channels for further details.
+It is not recommended to open a channel less than 100,000 satoshi, or .001 BTC. Anything less, and it's possible that the cost to open and close the channel might approach the size of the channel itself. The bigger the channel you open, the more outbound liquidity you will have, which means you have more spending power on the network. In this tutorial, we are going to open a channel of 2,000,000 satoshi. When opening a channel with Start9 HQ, we ask that you make it a private channel, meaning it will not display publicly on network graph. The reason for this is that unless you plan to be a very active Lightning Node Operator, having public channels decreases not only the reliability of your node but also hurts Start9's ability to route payments for you. If you do intend to be a serious node operator, we require that your channel be for a minimum of 5,000,000 sats. Please contact us in one of our community channels for further details.
 
 ## Getting Inbound Liquidity
 
 If you want to receive payments, you will need some inbound liquidity.
 
 The first, easiest, and best way to get inbound liquidity is to use your outbound liquidity to buy something. Any Bitcoin you spend using your outbound liquidity is Bitcoin you can now receive back. So if there is something you want to buy, like a Start9 Embassy or a t-shirt from the Start9 store, simply make the purchase, and you will then have inbound liquidity equal to the amount of Satoshis you spend.
 
-Option 2 is to personally ask Start9 for an invoice for however much inbound liquity you want. Then you send Bitcoin to the invoice, and in turn we will transfer fiat currency to you equal to the amount of the Bitcoin you send us. In other words, Start9 will buy some Bitcoin from you at market rate, such that you then have inbound liquidity. In either case, you are spending or selling some Bitcoin.
+Option 2 is to personally ask Start9 for an invoice for however much inbound liquidity you want. Then you send Bitcoin to the invoice, and in turn we will transfer fiat currency to you equal to the amount of the Bitcoin you send us. In other words, Start9 will buy some Bitcoin from you at market rate, such that you then have inbound liquidity. In either case, you are spending or selling some Bitcoin.
 
 The only way to get inbound liquidity without spending or selling Bitcoin is to convince someone to open a channel with you, just as you opened a channel with Start9 HQ. This may be a difficult task, since there is not much incentive for someone to open a channel with you unless you are also very well connected. Also, you will need to make sure that they too, are well connected with plenty of inbound liquidity, or else your inbound liquidity with them will not really matter. In other words, they might be the only person capable of paying you.
 
@@ -49,4 +49,3 @@ So options 1 or 2 are best. Use your Lightning node's outbound liquidity to eith
 ## Sending payments over Lightning
 
 Once you have open channels and are ready to transact on the Lightning Network, it is important to note that until "Synced to Graph" in the Properties page is reporting ✅, you may experience problems finding routes to your destination.
-

manifest.yaml

@@ -8,11 +8,10 @@ upstream-repo: "https://github.com/lightningnetwork/lnd"
 support-site: "https://lightning.engineering/slack.html"
 marketing-site: "https://lightning.engineering/"
 build: ["make"]
-min-os-version: "0.3.0"
 description:
   short: A complete implementation of a Lightning Network node by Lightning Labs
   long: |
-   LND fully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. In the current state lnd is capable of: creating channels, closing channels, managing all channel states (including the exceptional ones!), maintaining a fully authenticated+validated channel graph, performing path finding within the network, passively forwarding incoming payments, sending outgoing onion-encrypted payments through the network, updating advertised fee schedules, and automatic channel management (autopilot).
+    LND fully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. In the current state lnd is capable of: creating channels, closing channels, managing all channel states (including the exceptional ones!), maintaining a fully authenticated+validated channel graph, performing path finding within the network, passively forwarding incoming payments, sending outgoing onion-encrypted payments through the network, updating advertised fee schedules, and automatic channel management (autopilot).
 assets:
   license: LICENSE # default = LICENSE.md
   icon: icon.png # default = icon.png - assumes icon.png if this field does not exist
@@ -31,7 +30,7 @@ main:
 health-checks:
   synced:
     name: Synced
-    description: Ensures the node is synced to both the network graph and Bitcoin blockchain.
+    success-message: Synced to chain and graph
     type: docker
     image: main
     entrypoint: "health-check"
@@ -44,7 +43,7 @@ config: # if you dont provide an io format in cases like config where its necess
     image: compat
     system: true
     entrypoint: compat
-    args: 
+    args:
       - config
       - get
       - /root/.lnd
@@ -67,7 +66,7 @@ config: # if you dont provide an io format in cases like config where its necess
     mounts:
       compat: /mnt/assets
       main: /root/.lnd
-    io-format: yaml # necessary in this case 
+    io-format: yaml # necessary in this case
 properties:
   type: docker
   image: main
@@ -114,8 +113,8 @@ interfaces:
     name: Watchtower Interface
     description: Specifies the interfaces to listen on for watchtower client connections.
     tor-config:
-        port-mapping:
-          9911: "9911"
+      port-mapping:
+        9911: "9911"
     ui: false
     protocols:
       - tcp
@@ -124,22 +123,21 @@ interfaces:
     name: Peer Interface
     description: Specifies the interfaces to listen on for p2p connections.
     tor-config:
-        port-mapping:
-          9735: "9735"
+      port-mapping:
+        9735: "9735"
     ui: false
     protocols:
       - tcp
       - http
 dependencies:
   btc-rpc-proxy:
     version: ">=0.3.2.1 <0.4.0"
-    critical: false
     requirement:
       type: "opt-out"
       how: Can alternatively use the internal full archival bitcoind node or configure an external bitcoin node.
     description: Used to fetch validated blocks.
     config:
-      check: 
+      check:
         type: docker
         image: compat
         system: true
@@ -153,7 +151,7 @@ dependencies:
           - /root/.lnd
           - "/mnt/assets/btc-rpc-proxy_config_rules.yaml"
         mounts:
-          compat: /mnt/assets  
+          compat: /mnt/assets
           main: /root/.lnd
         io-format: yaml
       auto-configure:
@@ -176,13 +174,12 @@ dependencies:
         io-format: yaml
   bitcoind:
     version: "^0.21.1.2"
-    critical: true
     requirement:
       type: "opt-out"
       how: Can alternatively configure an external bitcoin node.
     description: Used to subscribe to new block events.
     config:
-      check: 
+      check:
         type: docker
         image: compat
         system: true
@@ -247,4 +244,4 @@ backup:
       BACKUP: /mnt/backup
       main: /root/.lnd
       compat: /mnt/assets
-    io-format: yaml
+    io-format: yaml