diff --git a/events/2024.11.Munich/Readme.md b/events/2024.11.Munich/Readme.md
index ae1ed38d..5a2771d1 100644
--- a/events/2024.11.Munich/Readme.md
+++ b/events/2024.11.Munich/Readme.md
@@ -1,7 +1,10 @@
 # WoT Week at Munich
 
 The logistics can be found at https://www.w3.org/WoT/IG/wiki/Wiki_for_WoT_Week_2024_planning.
-In this folder, technical information is found such as test plans of features.
+In this folder, technical information is found, such as test plans for features.
+
+The main goal of this plugfest is to test the feasibility of existing and new features of WoT standards.
+As a secondary goal, these tests will be put into user scenarios that are understandable by visitors.
 
 ## WIP - User Scenarios
 
@@ -16,7 +19,7 @@ Some ideas:
 
 ### Existing Features
 
-We should make sure that the existing features that the implementers have questions about are specified correctly.
+We should make sure that the existing features that the implementers have questions about are specified correctly. All these points are prioritized over new features.
 
 * Additional Responses
   * Error Handling on the application level (Scripting API is connected here)
@@ -25,15 +28,15 @@ We should make sure that the existing features that the implementers have questi
 * Linking between TDs
 * Specifying multiple `@type`s to TDs: This is confusing to people. We need more guidance.
 * Complex actions: Async and sync
-* Meta Operations (top-level form operations): Are they implemented correctly
+* Meta Operations (top-level form operations): Are they implemented correctly. This will be prioritized and idenfied gaps can be addressed as new meta operations.
 
 ### New Features
 
 We should experiment on the new features we are planning and collect implementation experience.
   
 * Initial connection
-* Data mapping
-* "Normative" Consumer Behavior: Degradation, Expected behavior. Writing what a Consumer is expected to do for a TD.
+* [Data Mapping:](https://github.com/w3c/wot/blob/main/planning/ThingDescription/td-next-work-items/usability-and-design.md#data-schema-mapping) This topic will be prioritized. It also related to additional responses existing feature mentioned above.
+* "Normative" Consumer Behavior: Degradation, Expected behavior. Writing what a Consumer is expected to do for a TD. This will be prioritized and its results will be used for the Interoperability Test Suite topic below.
 * Interoperability Test Suite: Given a TD, can a Consumer application fully interact with it? Strongly relates to normative consumption above.
 * New meta operations
 
@@ -41,3 +44,12 @@ We should experiment on the new features we are planning and collect implementat
 
 * Top-level operation for observing changes to TD (needs further discussion)
 * Discovery interface of Scripting API
+
+## WIP - Setups
+
+### WoT WG/IG Setups
+
+### External Setups
+
+If you want to showcase your use cases, you can do so. You can join the Plugfest activity (Monday and Tuesday) to test your setup together with others.
+