diff --git a/public-site/docs/docs/topic-releases/index.md b/public-site/docs/docs/topic-releases/index.md
index 3227ff0b..d826c744 100644
--- a/public-site/docs/docs/topic-releases/index.md
+++ b/public-site/docs/docs/topic-releases/index.md
@@ -6,6 +6,34 @@ title: What's new
 
 ## 2024
 
+### 2024-06-06 Support for advanced horizontal scaling (KEDA)
+We have released initial support for KEDA Triggers, to enable scaling of pods based on messages in a Azure Service Bus, or based on a CRON Schedule, as well as resource metrics as before (CPU/Memory). If you are using a non-resource trigger, we also support scaling to 0 replicas!
+See  [radixconfig.yaml](/radix-config/index.md#horizontalscaling) for more details.
+
+:::tip
+We recommend scaling most environments to 0 when not in use, this will save on cost and the environment 🌳💸
+:::
+
+#### Example:
+- Scales to 0 at night
+- Scales to minimum 1 at day time
+- Scales up to maximum 5 at heavy load (the trigger with the highest number of target replicas will win)
+```yaml
+horizontalScaling:
+  maxReplicas: 5
+  minReplicas: 0
+  triggers:
+    - name: cpu
+      cpu:
+        value: 50 
+    - name: cron
+      cron:
+        timezone: Europe/Oslo
+        start: 08:00
+        stop: 16:00
+        desiredReplicas: 1
+
+```
 
 ### 2024-06-04 Strict validation of RadixConfig.yaml in Radix CLI
 
@@ -128,36 +156,6 @@ Use with github action
 ````
 
 
-### 2024-06-06 Support for advanced horizontal scaling (KEDA)
-We have released initial support for KEDA Triggers, to enable scaling of pods based on messages in a Azure Service Bus, or based on a CRON Schedule, as well as resource metrics as before (CPU/Memory). If you are using a non-resource trigger, we also support scaling to 0 replicas!
-See  [radixconfig.yaml](/radix-config/index.md#horizontalscaling) for more details.
-
-:::tip
-We reccomend scaling most environments to 0 when not in use, this will save on cost and the environment 🌳💸
-:::
-
-#### Example:
-- Scales to 0 at night
-- Scales to minimum 1 at day time
-- Scales up to maximum 5 at heavy load (the trigger with the highest number of target replicas will win)
-```yaml
-horizontalScaling:
-  maxReplicas: 5
-  minReplicas: 0
-  triggers:
-    - name: cpu
-      cpu:
-        value: 50 
-    - name: cron
-      cron:
-        timezone: Europe/Oslo
-        start: 08:00
-        stop: 16:00
-        desiredReplicas: 1
-
-```
-
-
 ## 2023
 ### 2023-12-05 Support for using images from private repositories
 
diff --git a/public-site/docs/radix-config/index.md b/public-site/docs/radix-config/index.md
index 5f50cba9..d5f3c8b9 100644
--- a/public-site/docs/radix-config/index.md
+++ b/public-site/docs/radix-config/index.md
@@ -425,9 +425,10 @@ If overriding `portName` it will have to match one of the defined ports in the c
 
 Scale your components replicas up and down based on resources or external metrics like CRON or Azure Service Bus.
 
-More triggers are available at https://keda.sh/docs/latest/scalers/, and open a feature request on https://github.com/equinor/radix
+If you need any other trigger types, find the list of available triggers at https://keda.sh/docs/latest/scalers/ and open a feature request on https://github.com/equinor/radix
 
-You can override horizontalScaling in your environments and we will merge `minReplicas`, `maxReplicas`, `pollingInterval` and `CooldownPeriod`, if more any triggers is defined in the environment, the will override all triggers defined on the component level.
+You can override horizontalScaling in your environments and we will merge `minReplicas`, `maxReplicas`, `pollingInterval` and `cooldownPeriod`. If any triggers are defined in the environment, they will replace all triggers on the component level.
+Read more about polling intervall and cooldown period in KEDAs documentation [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pollinginterval)
 
 ```yaml
 spec:
@@ -437,7 +438,7 @@ spec:
         minReplicas: 0 # defaults to 1 if not set
         maxReplicas: 6
         # pollingInterval: 30 # Default
-        # CooldownPeriod: 300 # Default
+        # cooldownPeriod: 300 # Default
         triggers:
           # Cpu/Memory triggers will scale up/down so the average usage
           # is 85% of requested Cpu across all pods,