diff --git a/pages/validators/setup-guide.mdx b/pages/validators/setup-guide.mdx
index bf90a6c4..81ab8a02 100644
--- a/pages/validators/setup-guide.mdx
+++ b/pages/validators/setup-guide.mdx
@@ -408,9 +408,10 @@ The GenVM configuration files are located at `third_party/genvm/config/`
 
 This is the configuration file of the LLM module. In this file you can set up and configure various LLM providers, as well as the system prompts of your validator.
 
-You can turn on and off various LLMs by setting the `enabled` field to `false`.
+You should not need to modify this in general.
 
-At this stage, select one LLM and set all other to disabled.
+However, from here you can:
+- turn on and off various LLMs by setting the `enabled` field to `false`: By default they all come enabled for you to use. You will get warnings in the logs for each one that's enabled and not configured. Disabling non used LLM providers will hide those warnings
 
 Note environment variable names for LLM API keys (e.g., `HEURISTKEY`, `COMPUT3KEY`, `IOINTELLIGENCE_API_KEY`). You will need to ensure the appropriate key is correctly set before [running the node](#running-the-node).
 
diff --git a/pages/validators/upgrade.mdx b/pages/validators/upgrade.mdx
index 7f164096..45d2f80f 100644
--- a/pages/validators/upgrade.mdx
+++ b/pages/validators/upgrade.mdx
@@ -11,6 +11,12 @@ import { Callout } from "nextra-theme-docs";
   A fully Zero-downtime upgrade procedure is coming in a future update. 
 </Callout>
 
+## General Procedure
+
+1. **Download the new package and extract into a fresh folder** - Always use a clean directory for the new version.
+2. **Override with your custom config** - Configure the files in the new installation as you did when [setting up your node](/validators/setup-guide). Example: `.env` and `config.yaml`. You can refer to your previous settings. Avoid directly copying these files, as new versions may include updated default configurations.
+3. **Copy the contents of your old data folder** - The `data/` folder is the stateful directory used by the node, containing the database and keystore. This step is not needed if your data folder is located outside of the project directory.
+
 ## v0.3.x → v0.4 (Breaking Change)
 
 `v0.4` switches to a new consensus deployment with staking. For this reason, the validator must be set up from scratch without reusing the old database stored at `data/node/genlayer.db`.