Reordered bus notification section (FlexRay)

docs/4_4_3_flexray.adoc

@@ -288,7 +288,7 @@ The following applies for this operation: `Length = 9`.
 h|Behavior
 3+|The specified operation shall be produced by the Bus Simulation and consumed by Network FMUs.
 The Bus Simulation provides the <<low-cut-flexray-confirm-operation, `Confirm`>> operation for the Network FMU, which has previously provided the <<low-cut-flexray-transmit-operation, `Transmit`>> operation to be confirmed.
-If the configuration parameter <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> of a FlexRay Bus Terminal is set to `false`, the Network FMU must not wait for <<low-cut-flexray-confirm-operation, `Confirm`>> operations.
+If the configuration parameter <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> of a FlexRay Bus Terminal is set to `false` or omitted, the Network FMU must not wait for <<low-cut-flexray-confirm-operation, `Confirm`>> operations.
 
 |====
 
@@ -343,7 +343,7 @@ h|Behavior
 3+|The specified operation shall be produced by the Bus Simulation and consumed by Network FMUs.
 It represents a direct feedback corresponding to a specified <<low-cut-flexray-transmit-operation, `Transmit`>> operation.
 Depending on the type of <<low-cut-flexray-bus-error-operation, `Bus Error`>>, either only the <<low-cut-flexray-transmit-operation, `Transmit`>> producing or all Network FMUs must be notified via <<low-cut-flexray-bus-error-operation, `Bus Error`>> operation (see description column of <<table-flexray-error-code-values>>).
-If the configuration parameter <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> of a FlexRay Bus Terminal is set to `false`, the Network FMU does not wait for any responses from a Bus Simulation, i.e., potentially received <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations are discarded by the Network FMU.
+If the configuration parameter <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> of a FlexRay Bus Terminal is set to `false` or omitted, the Network FMU does not wait for any responses from a Bus Simulation, i.e., potentially received <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations are discarded by the Network FMU.
 
 |====
 
@@ -667,13 +667,12 @@ For a detailed simulation, a Network FMU needs information about whether the mes
 A Bus Simulation can simulate these effects by sending bus notifications in terms of <<low-cut-flexray-confirm-operation, `Confirm-`>> and <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations to the Network FMUs.
 
 However, in scenarios where Network FMUs are connected directly to each other, or where the Bus Simulation does not simulate such effects, it must be possible to configure the Network FMU such that it does not wait for any response after a <<low-cut-flexray-transmit-operation, `Transmit`>> operation.
-Therefore, the <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> configuration parameter is introduced for each FlexRay Bus Terminal.
+If a Network FMU is not supporting bus notifications at all, the configuration parameter shall be omitted.
+If a Network FMU supports bus notifications, the configuration parameter shall be defined with a default value set to `false` to allow the Network FMU to be run natively in each simulation scenario.
 If the value of the configuration parameter is set to `false`, the Network FMU must not wait for any response after a <<low-cut-flexray-transmit-operation, `Transmit`>> operation ("fire-and-forget").
+If the Network FMU shall be configured to handle responses in the form of <<low-cut-flexray-confirm-operation, `Confirm-`>> and <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations, the <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> configuration parameter shall be set to `true`.
 A Network FMU must always be able to handle the case that the Bus Simulation does not provide <<low-cut-flexray-confirm-operation, `Confirm-`>> or <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations.
-The default value shall be `false` to allow the Network FMU to be run natively in each simulation scenario.
-If a Network FMU is not supporting bus notifications, the configuration parameter shall be omitted.
-A Network FMU that does not support <<low-cut-flexray-confirm-operation, `Confirm-`>> or <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations must silently ignore them.
-If the Network FMU shall be configured to handle responses in the form of <<low-cut-flexray-confirm-operation, `Confirm-`>> and <<low-cut-flexray-bus-error-operation, `Bus Error`>> operations, the <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> parameter shall be set to `true`.
+Since a Bus Simulation is allowed to provide bus notification regardless of the <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> configuration parameter, Network FMUs must silently ignore such notifications if the value of <<low-cut-flexray-bus-notification-parameter, `BusNotifications`>> is set to `false` or the parameter is omitted.
 
 .Configuration parameter to configure bus notifications within a FlexRay Bus Terminal of Network FMUs.
 [[figure-fmu-flexray-bus-notifications-parameter]]