wrong description of ascending/descending

dunst-project · Oct 3, 2023 · bc45361 · bc45361
1 parent 1a444c1
commit bc45361
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/dunst.5.pod b/docs/dunst.5.pod
@@ -291,12 +291,12 @@ Any other value is interpreted as a color, see COLORS
 =item B<sort> (values: [true/false/id/urgency_ascending/urgency_descending/update], default: true)
 
 If set to true or urgency_descending, display notifications with higher urgency above the others.
-low first, then normal, then critical.
+critical first, then normal, then low.
 
 If set to false or id, sort notifications by id.
 
 If set to urgency_ascending, notifications are sorted by urgency, 
-critical first, then normal, then low.
+low first, then normal, then critical.
 
 If set to update, notifications are sorted by their update_time. 
 So the most recent is always at the top. This means that if you set sort to update,