diff --git a/charts/enterprise/metallb-config/Chart.yaml b/charts/enterprise/metallb-config/Chart.yaml
index 9f1600807dc..92819289f3e 100644
--- a/charts/enterprise/metallb-config/Chart.yaml
+++ b/charts/enterprise/metallb-config/Chart.yaml
@@ -22,7 +22,7 @@ sources:
   - https://github.com/metallb/metallb
   - https://metallb.universe.tf
 type: application
-version: 3.0.0
+version: 3.0.1
 annotations:
   truecharts.org/catagories: |
     - core
diff --git a/charts/enterprise/metallb-config/docs/setup-guide.md b/charts/enterprise/metallb-config/docs/setup-guide.md
index cc848d8cf6c..54a0b202931 100644
--- a/charts/enterprise/metallb-config/docs/setup-guide.md
+++ b/charts/enterprise/metallb-config/docs/setup-guide.md
@@ -4,7 +4,7 @@ The guide walks through a basic configuration of MetalLB for a single address po
 
 :::warning
 
-With MetalLB installed, apps will not be reachable using the integrated loadbalancer. You cannot combine two different loadbalancers in TrueNAS SCALE.
+With MetalLB installed, apps will not be reachable using the integrated LoadBalancer. You cannot combine two different LoadBalancers in TrueNAS SCALE.
 
 :::
 
@@ -14,6 +14,12 @@ With MetalLB installed, apps will not be reachable using the integrated loadbala
 
 ![metallb-addtrains](img/metallb_guide_trains.png)
 
+:::caution
+
+Our customized version of MetalLB is only intended for use with other TrueCharts applications. Other catalogs will likely not support our MetalLB application. MetalLB could technically work with TrueNAS catalog apps if they used the LoadBalancer service, but they don't as they use NodePort instead. These atypical configurations aren't officially supported nor encouraged by TrueCharts.
+
+:::
+
 ## 1. Install MetalLB Operator from Operators Train
 
 ![metallb-apps](img/metallb_guide_apps.png)
@@ -57,21 +63,21 @@ Once installed, `metallb-config` will always show as Stopped.
 
 ![metallb-specifyIP](img/metallb_guide_specifyIP.png)
 
-With MetalLB installed, its is recommended (but optional) to specify IP addresses for your apps.
+With MetalLB installed, it's recommended (but optional) to specify IP addresses for your apps.
 
 For each app, under **Networking and Services**, select `LoadBalancer` Service Type for the Main Service.
 
 In the **LoadBalancer IP** field, specify an IP address that is within the MetalLB address pool that you configured. Apply the same IP address to the **LoadBalancer IP** field on other services within the app.
 
-## 4. Disable SCALE's Default Loadbalancer
+## 4. Disable SCALE's Default LoadBalancer
 
-With MetalLB installed and configured, you must now disable SCALE's default loadbalancer.
+With MetalLB installed and configured, you must now disable SCALE's default LoadBalancer.
 
 In the SCALE UI, under **Apps** > **Settings** > **Advanced Settings**
 
 ![metallb-disable](img/metallb_guide_disableLB.png)
 
-Uncheck `Enable Integrated Loadbalancer`.
+Uncheck `Enable Integrated LoadBalancer`.
 
 **This will trigger a restart of Kubernetes and all apps**. After roughly 5-10 minutes, your apps will redeploy using the MetalLB-assigned IP addresses.