1 files changed, 11 insertions, 11 deletions

diff --git a/plugins/org.eclipse.etrice.doc/featuremodel/etrice.roomlanguage.featurizer b/plugins/org.eclipse.etrice.doc/featuremodel/etrice.roomlanguage.featurizer
index 40f574e03..38606a7f2 100644
--- a/plugins/org.eclipse.etrice.doc/featuremodel/etrice.roomlanguage.featurizer
+++ b/plugins/org.eclipse.etrice.doc/featuremodel/etrice.roomlanguage.featurizer
@@ -663,7 +663,7 @@ Feature CommunicationType
 			// explicit: eventdriven ProtocolClass EventdrivenProtocolClass {
 			incoming {
 				Message msg1() ["message without data"]
-				Message msg2(data: int32) ["message with data"]
+				Message msg2(int32) ["message with data"]
 			}
 			outgoing {
 				Message msg4()  ["eventdriven ProtocolClass can have message into two directions"]
@@ -672,7 +672,7 @@ Feature CommunicationType
 		
 		datadriven ProtocolClass DatadrivenProtocolClass {
 			incoming {
-				Message signal1 (data: int32) ["a datadriven message needs data"]
+				Message signal1 (int32) ["a datadriven message needs data"]
 			}
 			// datadriven ProtocolClass can only have incoming messages (signals)
 		}
@@ -697,11 +697,11 @@ Feature ProtocolClass
 		```room
 		ProtocolClass SimpleProtocolClass {
 			incoming {
-				Message msg1(data: int32}
+				Message msg1(int32}
 				Message msg2()
 			}
 			outgoing {
-				Message msg3(data: DataClass1}
+				Message msg3(DataClass1}
 				Message msg4()
 			}
 		}
@@ -717,13 +717,13 @@ Feature ProtocolClass
 			incoming {
 				// incoming means incoming for a regular port and outgoing for a conjugated port
 				Message message1() // message without data
-				Message message2(data: int32) // message with simple data
-				Message message3(data: DMessageData) // message with complex data (DataClass)
+				Message message2(int32) // message with simple data
+				Message message3(DMessageData) // message with complex data (DataClass)
 		
 			}
 			outgoing {
 			// outgoing means outgoing for a regular port and incoming for a conjugated port
-				Message message1(data: int32) // incoming and outgoing Messages can have the same name to enable symmetric protocols
+				Message message1(int32) // incoming and outgoing Messages can have the same name to enable symmetric protocols
 			}
 		}
 		
@@ -737,9 +737,9 @@ Feature ProtocolClass
 		datadriven ProtocolClass ProtocolClassData {
 			incoming {
 				// incoming means incoming for a regular port and outgoing for a conjugated port
-				Message value1(value: int32) // a datadriven message (signal) always needs data
-				Message value2(value: int16) // datadriven message with simple data
-				Message value3(value: DMessageData) // datadriven message with complex data (DataClass)
+				Message value1(int32) // a datadriven message (signal) always needs data
+				Message value2(int16) // datadriven message with simple data
+				Message value3(DMessageData) // datadriven message with complex data (DataClass)
 		
 			}
 			// no outgoing messages for datadriven ports allowed 
@@ -755,7 +755,7 @@ Feature ProtocolClass
 			usercode3 ''' '''
 			incoming {
 				Message messageName()
-				Message messageName(data: int32)
+				Message messageName(int32)
 			}
 			outgoing {
 				Message ...