Remove Configuration to not confuse it with Configuration Operation

docs/4_4_1_can.adoc

@@ -627,7 +627,7 @@ Only Network FMUs with the corresponding optionally exposed <<low-cut-can-bus-no
 _[This does not necessarily mean the FMU must fully support CAN error handling or sophisticated arbitration mechanisms._
 _A simple Network FMU might also choose to treat Bus Error or Arbitration operations in a simplified manner, e.g., by treating them as a positive confirmation.]_
 
-.Configuration parameter to configure bus notifications within a CAN Bus Terminal of Network FMUs.
+.Parameter to configure bus notifications within a CAN Bus Terminal of Network FMUs.
 [[figure-fmu--can-bus-notifications-parameter]]
 ----
  memberName:    BusNotifications
@@ -639,7 +639,7 @@ _A simple Network FMU might also choose to treat Bus Error or Arbitration operat
 
 CAN Bus Terminals of a Bus Simulation (FMU) might include this configuration parameter, by using a `calculatedParameter` or `constant output` to participate in an importer parameter propagation feature.
 
-.Configuration parameter to configure bus notifications within a CAN Bus Terminal of the Bus Simulation.
+.Parameter to configure bus notifications within a CAN Bus Terminal of the Bus Simulation.
 [[figure-fmu-can-bus-notifications-parameter-in-bus-simulation]]
 ----
  memberName:    BusNotifications
@@ -671,7 +671,7 @@ The <<low-cut-can-transmit-operation, `Transmit`>> operation represents the send
 With appropriate options, relevant functionalities can be configured and used on a network abstraction level (e.g., Virtual CAN network ID for CAN XL or Bit Rate Switch for CAN FD).
 In the real world, flawlessly transmitted CAN frames will be acknowledged by at least one receiver CAN node.
 To simulate this behavior, the <<low-cut-can-confirm-operation, `Confirm`>> operations are introduced.
-In addition, the configuration parameter <<low-cut-can-bus-notification-parameter, `BusNotifications`>> of a CAN Bus Terminal is defined to support lightweight bus simulations and <<common-concepts-direct-communication, directly connected Network FMUs>>.
+In addition, the parameter <<low-cut-can-bus-notification-parameter, `BusNotifications`>> of a CAN Bus Terminal is defined to support lightweight bus simulations and <<common-concepts-direct-communication, directly connected Network FMUs>>.
 
 If <<low-cut-can-bus-notification-parameter, `BusNotifications`>> is set to `false` (default), then Network FMUs must not rely on receiving <<low-cut-can-confirm-operation, `Confirm`>> operations for the specified Bus Terminal.
 In this case, the bus simulation is idealized and takes place in a "fire-and-forget" manner.