Properly format Changelog

Changelog

@@ -9,28 +9,36 @@ Change history
 
 * Add traceback to result value on failure.
 	**NOTE** If you use the database backend you have to re-create the
-	database table ``celery_taskmeta``. Contact the mailinglist or IRC channel
-	listed in README for help doing this.
+	database table ``celery_taskmeta``.
+	
+	Contact the mailinglist or IRC channel listed in README for help
+	doing this.
 
 * Celery now depends on ``carrot`` version 0.5.2.
 
 **IMPORTANT CHANGES**
 
 * Celery can now be used in pure Python (outside of a Django project).
-	This means celery is now no longer Django-specific. For more information
-	see the FAQ entry `Can I use celery without Django?`_.
+	This means celery is no longer Django specific.
+	
+	For more information see the FAQ entry
+	`Can I use celery without Django?`_.
 
 .. _`Can I use celery without Django?`:
 	http://ask.github.com/celery/faq.html#can-i-use-celery-without-django
 
-* Celery now supports task retries. See `Cookbook: Retrying Tasks`_ for more
-	information.
+* Celery now supports task retries.
+
+	See `Cookbook: Retrying Tasks`_ for more information.
 
 .. _`Cookbook: Retrying Tasks`:
 	http://ask.github.com/celery/cookbook/task-retries.html
 
-* We now have an AMQP result store backend, which uses messages to publish
-	task return value and status. And it's incredibly fast!
+* We now have an AMQP result store backend.
+
+	It uses messages to publish task return value and status. And it's
+	incredibly fast!
+
 	See http://github.com/ask/celery/issues/closed#issue/6 for more info!
 
 * AMQP QoS (prefetch count) implemented:
@@ -38,27 +46,31 @@ Change history
 
 * Now redirects stdout/stderr to the celeryd logfile when detached 
 
-* Now uses ``inspect.getargspec`` to only pass on the default arguments the
-	task supports.
+* Now uses ``inspect.getargspec`` to only pass default arguments
+	the task supports.
 
 * Add Task.on_success, .on_retry, .on_failure handlers
 	See :meth:`celery.task.base.Task.on_success`,
 	    :meth:`celery.task.base.Task.on_retry`,
-	    :meth:`celery.task.base.Task.on_failure`,
+	    	:meth:`celery.task.base.Task.on_failure`,
 
 * ``celery.utils.gen_unique_id``: Workaround for
-	http://bugs.python.org/issue4607
+  http://bugs.python.org/issue4607
 
 * You can now customize what happens at worker start, at process init, etc
-	by creating your own loaders. (see ``celery.loaders.*``)
+	by creating your own loaders. (see :mod:`celery.loaders.default`,
+	:mod:`celery.loaders.djangoapp`, :mod:`celery.loaders`.)
+
+* Support for multiple AMQP exchanges and queues.
 
-* Support for multiple AMQP exchanges and queues, this feature
-	misses documentation and tests, so anyone interested in this feature
-	is encouraged to improve on this situation.
+	This feature misses documentation and tests, so anyone interested 
+	is encouraged to improve this situation.
 
 * celeryd now survives a restart of the AMQP server!
-	Automatically re-establish AMQP broker connection if it's lost.
-	New settings:
+
+  Automatically re-establish AMQP broker connection if it's lost.
+
+  New settings:
 
     * AMQP_CONNECTION_RETRY
         Set to ``True`` to enable connection retries.
@@ -66,11 +78,6 @@ Change history
     * AMQP_CONNECTION_MAX_RETRIES.
         Maximum number of restarts before we give up. Default: ``100``.
 
-* celeryd now survives a restart of the AMQP server!
-	Automatically re-establish AMQP broker connection i
-    AMQP_CONNECTION_RETRY + AMQP_CONNECTION_MAX_RETRIES. This requires the master
-    branch of carrot.
-
 **NEWS**
 
 * New signals introduced: ``task_prerun`` and ``task_postrun``, see
@@ -88,7 +95,7 @@ Change history
 * Exceptions has been moved to ``celery.exceptions``, but are still
 	available in the previous module.
 
-* jail() refactored into celery.execute.ExecuteWrapper
+* jail() refactored into :class:`celery.execute.ExecuteWrapper`.
 
 * ``views.apply`` now correctly sets mimetype to "application/json"