diff --git a/doc/source/developers.rst b/doc/source/developers.rst
index c043d3c..2e7b269 100644
--- a/doc/source/developers.rst
+++ b/doc/source/developers.rst
@@ -798,15 +798,7 @@ If a change fails tests in Jenkins, please follow the steps below:
    the test. It will include a console log, and in the case of unit
    tests, HTML output from the test runner, or in the case of a
    devstack-gate test, it may contain quite a large number of system
-   logs. For jobs in the post queue, logs are found at
-   ``http://logs.openstack.org/<first two characters of commit SHA>/<commit SHA>``.
-   For example, if a change is committed with the SHA 'deadbeef123456',
-   the logs will be found at ``http://logs.openstack.org/de/deadbeef123456``.
-   Note that in many cases (particularly for higher-churn projects)
-   the commit will be accompanied by a merge commit to stitch it into
-   the branch and it's that merge commit which is the subject of post
-   pipeline jobs, so in that situation you will need to review the Git
-   log and use the SHA of that merge commit instead.
+   logs.
 2. Examine the console log or other relevant log files to determine
    the cause of the error. If it is related to your change, you should
    fix the problem and upload a new patchset. Do not use "recheck".
@@ -874,6 +866,24 @@ following recordings:
  - `Tales From The Gate <https://www.youtube.com/watch?v=sa67J6yMYZ0>`_
  - `Debugging Failures in the OpenStack Gate <https://www.youtube.com/watch?v=fowBDdLGBlU>`_
 
+Post Processing
+---------------
+
+After patches land, jobs can be run in the post queue. Finding build logs for
+these jobs works a bit differently to the results of the pre-merge check and
+gate queues.
+
+For jobs in the post queue, logs are found at
+``http://logs.openstack.org/<first two characters of commit SHA>/<commit SHA>``.
+For example, if a change is committed with the SHA 'deadbeef123456',
+the logs will be found at ``http://logs.openstack.org/de/deadbeef123456``.
+
+.. Note:: In many cases (particularly for higher-churn projects)
+  the commit will be accompanied by a merge commit to stitch it into
+  the branch and it's that merge commit which is the subject of post
+  pipeline jobs. In that situation you will need to review the Git
+  log and use the SHA of that merge commit instead.
+
 Peer Review
 -----------