diff --git a/learn/intro/launchpad.md b/learn/intro/launchpad.md
index 6914519..797b237 100644
--- a/learn/intro/launchpad.md
+++ b/learn/intro/launchpad.md
@@ -6,7 +6,7 @@ description: A dapp to securely create Distributed Validators alone or with a gr
 
 In order to activate an Ethereum validator, 32 ETH must be deposited into the official deposit contract. Distributed validators are no different.
 
-The vast majority of users that created validators to date have used the [~~**Eth2**~~** Staking Launchpad**](https://launchpad.ethereum.org/), a public good open-source website built by the Ethereum Foundation alongside participants who later went on to found Obol. This tool has been wildly successful in the safe and educational creation of a significant number of validators on the Ethereum mainnet.
+The vast majority of users that created validators to date have used the [~~**Eth2**~~** Staking Launchpad**](https://launchpad.ethereum.org/), a public good open-source website built by the Ethereum Foundation alongside participants who later went on to found Obol. This tool has been wildly successful in the safe and educational creation of a significant number of validators on the Ethereum mainnet.
 
 To facilitate the generation of distributed validator keys amongst remote users with high-trust, the Obol Network developed and maintains a website that enables a group of users to come together and create these threshold keys: **The DV Launchpad**.
 
diff --git a/run-a-dv/start/obol-monitoring.md b/run-a-dv/start/obol-monitoring.md
index 6ab7b85..d5bfa74 100644
--- a/run-a-dv/start/obol-monitoring.md
+++ b/run-a-dv/start/obol-monitoring.md
@@ -51,4 +51,25 @@ The last step in your DappNode setup is to add your Monitoring Credentials. This
 
     <figure><img src="../../.gitbook/assets/image (86).png" alt=""><figcaption></figcaption></figure>
 {% endtab %}
+{% tab title="DV-Pod" %}
+
+Get a Prometheus monitoring credential from the Obol core team, it will look like:
+
+```log
+obol20tnt8UC...
+```
+
+Then, either add `--set centralMonitoring.enabled=true --set-string centralMonitoring.token='YOUR_TOKEN_HERE'` to your `helm install` command, or if using a Values.yaml file, update `centralMonitoring.enabled` to `true`, and `centralMonitoring.token` to the monitoring credential you have been given, and then install/upgrade the chart.
+
+```yaml
+# -- Central Monitoring
+centralMonitoring:
+  # -- Specifies whether central monitoring should be enabled
+  enabled: true
+  # -- https endpoint to obol central prometheus
+  promEndpoint: "https://vm.monitoring.gcp.obol.tech/write"
+  # -- The authentication token to the central Obol prometheus instance
+  token: "YOUR_TOKEN_HERE"
+```
+{% endtab %}
 {% endtabs %}