Docs: reformat timer driver docs
Change-Id: I96b17e9b4994a101cd5b5552b668db9578b64c50
diff --git a/doc/source/admin/drivers/timer.rst b/doc/source/admin/drivers/timer.rst
index c8afdd7..3b38c99 100644
--- a/doc/source/admin/drivers/timer.rst
+++ b/doc/source/admin/drivers/timer.rst
@@ -11,14 +11,20 @@
--------------------
Timers don't require a special connection or driver. Instead they can
-simply be used by listing **timer** as the trigger.
+simply be used by listing ``timer`` as the trigger.
-This trigger will run based on a cron-style time specification.
-It will enqueue an event into its pipeline for every project
-defined in the configuration. Any job associated with the
-pipeline will run in response to that event.
+This trigger will run based on a cron-style time specification. It
+will enqueue an event into its pipeline for every project defined in
+the configuration. Any job associated with the pipeline will run in
+response to that event.
-**time**
- The time specification in cron syntax. Only the 5 part syntax is
- supported, not the symbolic names. Example: ``0 0 * * *`` runs at
- midnight. The first weekday is Monday.
+.. attr:: pipeline.trigger.timer
+
+ The timer trigger supports the following attributes:
+
+ .. attr:: time
+ :required:
+
+ The time specification in cron syntax. Only the 5 part syntax
+ is supported, not the symbolic names. Example: ``0 0 * * *``
+ runs at midnight. The first weekday is Monday.