diff --git a/docs/howto/performance.rst b/docs/howto/performance.rst
index f87e405c0..57bac2131 100644
--- a/docs/howto/performance.rst
+++ b/docs/howto/performance.rst
@@ -31,7 +31,7 @@ Without a persistent cache, Wagtail will recreate all compressable assets at eac
 Sending emails in the background using Celery
 ---------------------------------------------
 
-Various actions in the Wagtail admin backend can trigger notification emails - for example, submitting a page for moderation. In Wagtail's default configuration, these are sent as part of the page request/response cycle, which means that web server threads can get tied up for long periods if a large number of emails is being sent. To avoid this, Wagtail can be configured to do this as a background task, using `Celery <http://www.celeryproject.org/>`_ as a task queue. To install Celery, add ``django-celery`` to your requirements.txt. A sample configuration, using Redis as the queue backend, would look like::
+Various actions in the Wagtail admin backend can trigger notification emails - for example, submitting a page for moderation. In Wagtail's default configuration, these are sent as part of the page request/response cycle, which means that web server threads can get tied up for long periods if many emails are being sent. To avoid this, Wagtail can be configured to do this as a background task, using `Celery <http://www.celeryproject.org/>`_ as a task queue. To install Celery, add ``django-celery`` to your requirements.txt. A sample configuration, using Redis as the queue backend, would look like::
 
     import djcelery