Update doc/manuals/orion-api.md

Co-authored-by: mapedraza <[email protected]>

doc/manuals/orion-api.md

@@ -2539,7 +2539,7 @@ In order to overcome this problem, the `evalPriority` metadata can be used to de
 
 * `evalPriority` metadata is a number from 1 (first evaluation) to 100000 (last evaluation)
 * Expressions are evaluated in incresing order of priority
-* In case of ties, Orion does not guarantee a particular evaluation order. Thus, expressions in the same priority level must be considered independent or bad things would happen
+* In case of ties, Orion does not guarantee a particular evaluation order. Thus, expressions in the same priority level must be considered independent, and expressions using other attributes with the same or lower priority would result in unexpected values.
 * If no `evalPriority` is set, default 100000 is used
 * `evalPriority` only has a meaning in `notification.httpCustom.ngsi` in subscriptions. As metadata in regular entities (e.g. an entity created with `POST /v2/entities`) Orion doesn't implements any semantic for it