Post failures to gitea-releases too, as errors is the generic fallback topic

README.md

@@ -1,8 +1,8 @@
 # ci-notify
 
 One ntfy notification per workflow run. Add it as the last job, needing every
-other job: a failed job posts to `errors` (priority 5), and a run where
-everything passed on `master` posts to `gitea-releases`. Each notification
+other job: a failed job posts to `gitea-releases` at priority 5, and a run
+where everything passed on `master` posts there at priority 3. Each notification
 links to the run. Other branches only report failures, so a feature branch push
 stays quiet.
 
@@ -19,4 +19,4 @@ stays quiet.
 ```
 
 `success_branches` widens what is announced (e.g. `master develop`), and the
-topics and tokens can be overridden.
+topic and token can be overridden.