diff --git a/website/site/content/docs/webapp/processing.md b/website/site/content/docs/webapp/processing.md
index e20ad5ba..06cf9740 100644
--- a/website/site/content/docs/webapp/processing.md
+++ b/website/site/content/docs/webapp/processing.md
@@ -7,13 +7,13 @@ mktoc = true
 
 
 The page *Processing Queue* shows the current state of document
-processing for your uploads.
+processing for your uploads. The page currently only shows at most the
+80 newest jobs. There is a maximum of 40 done jobs (successful,
+cancelled or failed) and 40 not done jobs.
 
-At the top of the page a list of running jobs is shown. Below that,
-the left column shows jobs that wait to be picked up by the job
-executor. On the right are finished jobs. The number of finished jobs
-is cut to some maximum and is also restricted by a date range. The
-page refreshes itself automatically to show the progress.
+The sidebar lets you filter for a specific job state. The *Currently
+Running* tab shows all jobs that are currently executing and their log
+output. The page refreshes automatically to show the progress.
 
 Example screenshot:
 
@@ -32,8 +32,9 @@ Since job executors are shared among all collectives, it may happen
 that a job is some time waiting until it is picked up by a job
 executor. You can always start more job executors to help out.
 
-If a job fails, it is retried after some time. Only if it fails too
-often (can be configured), it then is finished with *failed* state.
+If a job fails it first enters "stuck" state and is retried after some
+time. Only if it fails too often (can be configured), it then is
+finished with *failed* state.
 
 For the document-processing task, if processing finally fails or a job
 is cancelled, the item is still created, just without suggestions.