--- a/taskcluster/docs/actions.rst
+++ b/taskcluster/docs/actions.rst
@@ -16,18 +16,18 @@ At a very high level, the process looks 
    re-trigger a test case.
 
  * The user interface follows the action description to carry out the action.
    In most cases (``action.kind == 'task'``), that entails creating an "action
    task", including the provided information. That action task is responsible
    for carrying out the named action, and may create new sub-tasks if necessary
    (for example, to re-trigger a task).
 
-Action Task Implementation
-==========================
+Defining Action Tasks
+---------------------
 
 There are two options for defining actions: creating a callback action, or
 creating a custom action task.  A callback action automatically defines an
 action task that will invoke a Python function of your devising.
 
 A custom action task is an arbitrary task definition that will be created
 directly.  In cases where the callback would simply call ``queue.createTask``,
 a custom action task can be more efficient.