diff --git a/source/img/Notification.png b/source/img/Notification.png
new file mode 100644
index 0000000..7835a95
Binary files /dev/null and b/source/img/Notification.png differ
diff --git a/source/img/Notification2.png b/source/img/Notification2.png
new file mode 100644
index 0000000..5abdc22
Binary files /dev/null and b/source/img/Notification2.png differ
diff --git a/source/img/NotificationHistory.png b/source/img/NotificationHistory.png
deleted file mode 100644
index e68c3b5..0000000
Binary files a/source/img/NotificationHistory.png and /dev/null differ
diff --git a/source/img/NotificationLowDisk.png b/source/img/NotificationLowDisk.png
deleted file mode 100644
index 74432ce..0000000
Binary files a/source/img/NotificationLowDisk.png and /dev/null differ
diff --git a/source/plattform/notification.rst b/source/plattform/notification.rst
index 952b86d..d7241a0 100644
--- a/source/plattform/notification.rst
+++ b/source/plattform/notification.rst
@@ -1,106 +1,105 @@
 Notification
 ============
 
 Notifications are a way to inform users of your app about events, even if the 
 applications has no focus, is minimized, or is only running in the background.
 
 Examples
 --------
 
-.. figure:: /img/NotificationLowDisk.png
+.. figure:: /img/Notification.png
    :alt: 
    
-   Low disk space notification
+   Update notification 
 
 Guidelines
 ----------
 
 Is this the right control
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Use notifications to inform the user of events that are of interest, even if 
 your app is not in foreground, but don't spam the user with notifications.
 
  - Completion of long running tasks that the user has started manually
  - Incoming communication from other users
  - Hardware related events like low battery, lost network connection, running 
    out of disk space
  
 
 Don't use a notification for:
 
  - Operations that don't require user interaction, such as background processes, 
    syncing, or updates
  - Advertising, rating or feedback requests, or other annoyances
  - If an unexpected or potentially dangerous condition has been reached and the 
    user must make a decision. Use an :doc:`/components/assistance/message` 
    instead.
  - Don't send notifications if an user has never opened your application
 
-.. figure:: /img/NotificationHistory.png
-   :alt: 
-   
-   Notification history
-
-
 Behavior
 ~~~~~~~~
 
 Notifications are provided by the system to the user, and foremost the 
 user settings for notification govern the behavior and appearance of 
 notifications. But there are several options to influence and enrich the 
 behavior of your notifications.
 
 Persistence
 """""""""""
 
 Making a notification persistent will prevent it from closing after a timeout. 
 Your app must revoke the persistent notification, if the reason for the 
 notification no longer applies, like a power adapter was plugged after a 
 "Laptop battery is almost empty" notification.
 
 Urgency
 """""""
 
 It is recommended that a notification carrys an urgency hint:
 
  - 0 – Low, “Matt is now online”, “You just plugged in your AC adapter”
  - 1 – Normal, “You have new mail”
  - 2 – Critical, “Laptop battery is almost empty”
 
 Actions
 """""""
 
 You can add up to three action buttons to the notification to enable the user 
 to react to the event without having to go to the app itself.
 
 Preview
 """""""
 
 You can specify a URL to an image associated with the notification. The image 
 will be displayed as a preview in the notification.
 
+.. figure:: /img/Notification2.png
+   :alt: 
+   
+   Notification with a preview image
+   
 .. Quick Reply
    """""""""""
 
    This enables the user to reply to an email or SMS from within the 
    notification. A “Reply” text field is placed in the notification window 
    whose content is eventually sent back to the application through the 
    notification server.
 
 Code
 ----
 
 .. code-block:: c++
 
     KNotification *notification= new KNotification ( "contactOnline", widget );
     notification->setText( i18n("The contact %1 has gone online", 
     contact->name() );
     notification->setPixmap( contact->pixmap() );
     notification->setActions( QStringList( i18n( "Open chat" ) ) );
     connect(notification, SIGNAL(activated(unsigned int )), contact , 
     SLOT(slotOpenChat()) );
     notification->sendEvent();
 
 Use :knotificationsapi:`<KNotification>` to send notifications to the
 :doc:`Plasma Workspaces </introduction/architecture>`.