diff --git a/04-day2.md b/04-day2.md
index 2952d96c6e74e9f25797a22af7e089a6a7618e10..8cc0fbe1f04ce16d87cf404547351940ee6a5061 100644
--- a/04-day2.md
+++ b/04-day2.md
@@ -133,28 +133,53 @@ vnfd:
 
 ### Adding scaling operations
 
-Scaling operations happen at a VDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger.
+Scaling operations happen at a VDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger. At a KDU level, manual scaling operations are available for juju bundle deployments.
 
-In both cases, a `scaling-aspect` section must be added to the VNF Deployment Flavour. The following example enables VDU scaling based on a manual trigger (OSM API or CLI).
+In both cases, a `scaling-aspect` section must be added to the VNF Deployment Flavour. The following example enables VDU and KDU scaling based on a manual trigger (OSM API or CLI).
 
 ```yaml
+# VDU level
 vnfd:
   df:
   - ...
     scaling-aspect:
     - aspect-delta-details:
         deltas:
-        - id: vdu_autoscale-delta
+        - id: vdu_manualscale-delta
           vdu-delta:
-          - id: hackfest_basic_metrics-VM
+          - id: basic-VM
             number-of-instances: "1"
-      id: vdu_autoscale
+      id: vdu_manualscale
       max-scale-level: 1
-      name: vdu_autoscale
+      name: vdu_manualscale
       scaling-policy:
       - cooldown-time: 120
-        name: cpu_util_above_threshold
+        name: vdu_manual_scale
+        scaling-type: manual
+
+# KDU level
+vnfd:
+  df:
+  - ...
+    kdu-resource-profile:
+    - id: nginx-scale
+      kdu-name: native-kdu
+      resource-name: nginx  # Application name in the KDU instance. This name is stored in the juju bundle's yaml file
+    scaling-aspect:
+    - aspect-delta-details:
+        deltas:
+        - id: kdu_manualscale-delta
+          kdu-resource-delta:
+          - id: nginx-scale  # Points the kdu-resource-profile:id which has the resource-name information 
+            number-of-instances: "1"
+      id: kdu_manualscale
+      max-scale-level: 1
+      name: kdu_manualscale
+      scaling-policy:
+      - cooldown-time: 120
+        name: kdu_manual_scale
         scaling-type: manual
+
 ```
 
 The following example defines a closed-loop scaling operation based on a specific monitoring parameter threshold.