diff --git a/docs/externalmetrics.md b/docs/externalmetrics.md
index 461b8788..05e67073 100644
--- a/docs/externalmetrics.md
+++ b/docs/externalmetrics.md
@@ -6,7 +6,7 @@ It's possible to configure [Autoscaling on metrics not related to Kubernetes obj
 The configuration for `external` metrics rules is almost identical to the normal `rules`:
 
 ```yaml
-external:
+externalRules:
 - seriesQuery: '{__name__="queue_consumer_lag",name!=""}'
   metricsQuery: sum(<<.Series>>{<<.LabelMatchers>>}) by (name)
   resources:
@@ -38,7 +38,7 @@ This is done by setting `namespaced: false` in the `resources` section of the `e
 ```yaml
 # rules: ...
 
-external:
+externalRules:
 - seriesQuery: '{__name__="queue_depth",name!=""}'
   metricsQuery: sum(<<.Series>>{<<.LabelMatchers>>}) by (name)
   resources:
diff --git a/docs/sample-config.yaml b/docs/sample-config.yaml
index 61c9dda6..0508c6c4 100644
--- a/docs/sample-config.yaml
+++ b/docs/sample-config.yaml
@@ -67,7 +67,7 @@ rules:
 
 # external rules are not tied to a Kubernetes resource and can reference any metric
 # https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#autoscaling-on-metrics-not-related-to-kubernetes-objects
-external:
+externalRules:
 - seriesQuery: '{__name__="queue_consumer_lag",name!=""}'
   metricsQuery: sum(<<.Series>>{<<.LabelMatchers>>}) by (name)
 - seriesQuery: '{__name__="queue_depth",topic!=""}'