Bug 1381622: order the actions docs more naturally; r=jonasfj

MozReview-Commit-ID: GaMlrhkEdnk

--HG--
rename : taskcluster/docs/action-details.rst => taskcluster/docs/action-implementation.rst
extra : rebase_source : 510f74c16dda00f0a309d39945654754cf94924b

taskcluster/docs/actions.rst

@@ -6,12 +6,13 @@ supported user interfaces like Treeherder.
 
 At a very high level, the process looks like this:
 
- * The decision task produces an artifact indicating what actions are
-   available.
+ * The decision task produces an artifact, ``public/actions.json``, indicating
+   what actions are available.
 
- * The user interface consults that artifact and presents appropriate choices
-   to the user, possibly involving gathering additional data from the user,
-   such as the number of times to re-trigger a test case.
+ * A user interface (for example, Treeherder or the Taskcluster tools) consults
+   ``actions.json`` and presents appropriate choices to the user, if necessary
+   gathering additional data from the user, such as the number of times to
+   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
@@ -19,10 +20,8 @@ At a very high level, the process looks like this:
    for carrying out the named action, and may create new sub-tasks if necessary
    (for example, to re-trigger a task).
 
-For details on interface between in-tree logic and external user interfaces,
-see :doc:`the specification for actions.json <action-spec>`.
 
 .. toctree::
 
-    action-details
     action-spec
+    action-implementation