link fixes (#67)

* link fixes

updates to various broken links

* remove J2 cli from build and deploy steps

removes J2 cli from build and deploy steps as the image has this baked in now

.github/workflows/build-deploy.yml

@@ -42,9 +42,6 @@ jobs:
             secret/data/pub-metrics-eks/rds/blocks-read-user username | BLOCK_METRICS_USER;
             secret/data/pub-metrics-eks/rds/blocks-read-user password | BLOCK_METRICS_PASSWORD;
 
-      - name: Install J2-CLI
-        run: pip3 install j2cli
-
       - name: Template grafana configs
         run: |
           j2 templates/datasources.yaml.j2 -o helm/pub-metrics-grafana/datasources

.github/workflows/deploy-review.yml

@@ -45,9 +45,6 @@ jobs:
             secret/data/pub-metrics-eks/rds/blocks-read-user username | BLOCK_METRICS_USER;
             secret/data/pub-metrics-eks/rds/blocks-read-user password | BLOCK_METRICS_PASSWORD;
 
-      - name: Install J2-CLI
-        run: pip3 install j2cli
-
       - name: Template grafana configs
         run: |
           j2 templates/datasources.yaml.j2 -o helm/pub-metrics-grafana/datasources

dashboards/blockchain/blockchain-state.json

@@ -984,7 +984,7 @@
         "type": "prometheus",
         "uid": "PB06BBC9CA81C548D"
       },
-      "description": "In a block, there are a number of proofs. Each proof starts out in the \"uncompact\" form, which is quick to generate in real time, but takes longer to validate when syncing. \n\nBlueboxes find uncompact proofs and compact them into a more compact form that is quicker to validate when syncing and broadcasts them to the network so peers can replace them in their database.\n\nCompact Block: A block that has all supported proofs compacted. (There are some proofs that are not currently configured to be compacted by blueboxes)\n\nUncompact Block: A block with at least one proof that is not compacted, but could be compacted by a bluebox (could be partially compacted).\n\nWant to help generate compact proofs? Read about how to run a bluebox timelord here: https://github.com/Chia-Network/chia-blockchain/wiki/Timelords#bluebox-timelords",
+      "description": "In a block, there are a number of proofs. Each proof starts out in the \"uncompact\" form, which is quick to generate in real time, but takes longer to validate when syncing. \n\nBlueboxes find uncompact proofs and compact them into a more compact form that is quicker to validate when syncing and broadcasts them to the network so peers can replace them in their database.\n\nCompact Block: A block that has all supported proofs compacted. (There are some proofs that are not currently configured to be compacted by blueboxes)\n\nUncompact Block: A block with at least one proof that is not compacted, but could be compacted by a bluebox (could be partially compacted).\n\nWant to help generate compact proofs? Read about how to run a bluebox timelord here: https://docs.chia.net/timelord-architecture/",
       "fieldConfig": {
         "defaults": {
           "color": {

dashboards/blockchain/mempool-transactions-fees.json

@@ -59,7 +59,7 @@
         "type": "prometheus",
         "uid": "PB06BBC9CA81C548D"
       },
-      "description": "How many individual spendbundles are currently in the mempool\n\nSpendbundle Docs: https://chialisp.com/docs/coin_lifecycle#spend-bundles",
+      "description": "How many individual spendbundles are currently in the mempool\n\nSpendbundle Docs: https://docs.chia.net/spend-bundles/",
       "fieldConfig": {
         "defaults": {
           "color": {
@@ -153,7 +153,7 @@
         "type": "prometheus",
         "uid": "PB06BBC9CA81C548D"
       },
-      "description": "This shows the current cost of the mempool (how full the mempool is). Once the mempool is full, a fee is required to kick other lower fee transactions out to get your transaction included in the mempool.\n\nOnce a transaction is in the mempool, it will be included in blocks as there is space. Typically the highest \"fee per cost\" are included in blocks first.\n\nCost Info: https://chialisp.com/docs/clvm/lang_reference#costs",
+      "description": "This shows the current cost of the mempool (how full the mempool is). Once the mempool is full, a fee is required to kick other lower fee transactions out to get your transaction included in the mempool.\n\nOnce a transaction is in the mempool, it will be included in blocks as there is space. Typically the highest \"fee per cost\" are included in blocks first.\n\nCost Info: https://chialisp.com/costs/\nMempool Info: https://docs.chia.net/mempool/",
       "fieldConfig": {
         "defaults": {
           "color": {