Update 5._OPC_Alarms_and_Events.md

documentation/1._Introduction_to_OPC/5._OPC_Alarms_and_Events.md

@@ -16,7 +16,7 @@ Simple and tracking-related events represent changes that are not related to mea
 
 The figure illustrates the object hierarchy of an Alarm and Event Server.
 
-# Bild
+![OPC-Classic-SDK](https://github.com/SoftingIndustrial/OPC-Classic-SDK/raw/main/documentation_pics/CMN_Intro_004_1.jpg)
 
 The top-level object is the OPCEventServer object. It provides methods for creating the OPCServerAreaBrowser object and the OPCEventSubscription objects.
 
@@ -26,7 +26,7 @@ OPCEventSubscription objects are used to manage events and to signal them to cli
 
 After the OPCEventSubscription object has been added, the client can filter events.
 
-# Bild
+![OPC-Classic-SDK](https://github.com/SoftingIndustrial/OPC-Classic-SDK/raw/main/documentation_pics/CMN_Intro_004_2.jpg)
 
 The figure shows which mandatory attribute values are returned in the event notification. The parameters present for simple events are also present for condition- and tracking-related events.
 
@@ -44,4 +44,4 @@ The following parameters are present only for condition-related events:
 - AckRequired: this flag indicates that the condition requires acknowledgment of this event.
 - ActiveTime: time that the condition became active or the time of transition into the current subcondition.
 - Cookie: server-defined cookie associated with the event notification and used by the client during acknowledgement.
-- AckId: used only for condition-related events which are acknowledgement notifications. Parameter contains the AcknowledgerId.
+- AckId: used only for condition-related events which are acknowledgement notifications. Parameter contains the AcknowledgerId.