[docs] Footnotes

docs/userguide/optimizing.rst

@@ -38,10 +38,6 @@ You should set up alerts, that will notify you as soon as any queue has
 reached an unacceptable size.  This way you can take appropriate action
 like adding new worker nodes, or revoking unnecessary tasks.
 
-.. [*] The chapter is available to read for free here:
-       `The back of the envelope`_.  The book is a classic text. Highly
-       recommended.
-
 .. _`Programming Pearls`: http://www.cs.bell-labs.com/cm/cs/pearls/
 
 .. _`The back of the envelope`:
@@ -163,16 +159,6 @@ If you have a combination of long- and short-running tasks, the best option
 is to use two worker nodes that are configured separately, and route
 the tasks according to the run-time. (see :ref:`guide-routing`).
 
-.. [*] RabbitMQ and other brokers deliver messages round-robin,
-       so this doesn't apply to an active system.  If there is no prefetch
-       limit and you restart the cluster, there will be timing delays between
-       nodes starting. If there are 3 offline nodes and one active node,
-       all messages will be delivered to the active node.
-
-.. [*] This is the concurrency setting; :setting:`worker_concurrency` or the
-       :option:`celery worker -c` option.
-
-
 Reserve one task at a time
 --------------------------
 
@@ -260,3 +246,17 @@ available for work, disabling the prefetch behavior::
     <- T3 complete sent by process B
     <- T1 complete sent by process A
 
+.. rubric:: Footnotes
+
+.. [*] The chapter is available to read for free here:
+       `The back of the envelope`_.  The book is a classic text. Highly
+       recommended.
+
+.. [*] RabbitMQ and other brokers deliver messages round-robin,
+       so this doesn't apply to an active system.  If there is no prefetch
+       limit and you restart the cluster, there will be timing delays between
+       nodes starting. If there are 3 offline nodes and one active node,
+       all messages will be delivered to the active node.
+
+.. [*] This is the concurrency setting; :setting:`worker_concurrency` or the
+       :option:`celery worker -c` option.

docs/userguide/security.rst

@@ -101,8 +101,6 @@ But for the same reasons the `pickle` serializer is inherently insecure [*]_,
 and should be avoided whenever clients are untrusted or
 unauthenticated.
 
-.. [*] http://nadiana.com/python-pickle-insecure
-
 You can disable untrusted content by specifying
 a white-list of accepted content-types in the :setting:`accept_content`
 setting:
@@ -243,3 +241,7 @@ that can be used.
 .. _`AIDE`: http://aide.sourceforge.net/
 .. _`Open Source Tripwire`: http://sourceforge.net/projects/tripwire/
 .. _`ZFS`: https://en.wikipedia.org/wiki/ZFS
+
+.. rubric:: Footnotes
+
+.. [*] http://nadiana.com/python-pickle-insecure