Merge branch 'master' of /home/vorner/pciids

[pciids.git] / help / notifications

diff --git a/help/notifications b/help/notifications
index a87c8a9b92ebb431fb8c1f7f5cb46b73937e153d..a34b75b048c7f24da50630e0084ac2c27d505468 100644 (file)
--- a/help/notifications
+++ b/help/notifications
@@ -1,12 +1,13 @@
 Notifications
 <p>
-If you are interested in any changes in some item, you can set up a notification to get informed.
-Browse to the item and click <a href='$AC_URL$notifications'>notifications</a> link (it is visible only when you are <a href='$HELP_URL$account'>logged in</a>.
-You can set these things:
+If you want to monitor changes of an item, you can set up a notification to get informed
+whenever it changes.
+Browse to the item and click the <a href='$AC_URL$notifications'>notifications</a> link (it is visible only when you are <a href='$HELP_URL$account'>logged in</a>).
+You can set:
 <ul>
-       <li><strong>Effect range</strong> ‒ which IDs are considered by this notification. If the notification is not recursive, only the current ID is taken into account. Recursive notifications work on the given ID and its whole subtree (sub-items, their sub-items, …).
-       <li><strong>Notification level</strong> ‒ how serious even needs to happen to trigger the notification. None means the notification never happens (it does not exist, you can delete it by setting it to it), main comment means whenever admin approves change of a name, sub-item is when someone submits new item with this one as a parent, suggestion is when someone suggests a new name for the item (but is not yet approved) and discussion is whenever someone writes anything.
-       All the more common notifications contain the less common (when you check discussion and an admin approves a name change, it is triggered too, but not the other way around).
+       <li><strong>Effect range</strong> ‒ which ID's are considered for this notification. If the notification is not recursive, only the current ID is taken into account. Recursive notifications work on the given ID and its whole subtree (sub-items, their sub-items, …).
+       <li><strong>Notification level</strong> ‒ how serious an event needs to happen to trigger the notification. <em>None</em> means that the notification never happens (it ceases to exist, you can delete it by setting it to this level), <em>main comment & sub-item</em> means whenever an admin approves a change of the name or when someone submits a new item with this one as a parent, <em>suggestion</em> is when someone suggests a new name for the item (but it is not yet approved) and <em>discussion</em> means whenever anybody writes anything.
+       All the more general notifications contain the less general ones (when you check discussion and an admin approves a name change, it is triggered too, but not the other way around).
        <li><strong>Notification way</strong> ‒ the way the notification gets to you.
 </ul>
 
@@ -17,6 +18,6 @@ You can switch to them by clicking on them.
 
 <h2>See also</h2>
 <p>
-This is all your own configuration. You can <a href='$HELP_URL$account'>get an account</a> so you can set it up.
+The notifications are a part of your personal settings. You need to <a href='$HELP_URL$account'>get an account</a> in order to set them up.
 <p>
-You can set up various things (like address, where the notifications are sent) in your <a href='$HELP_URL$profile'>profile</a>.
+You can configure various things (like the address where the notifications are sent) in your <a href='$HELP_URL$profile'>profile</a>.