Not all reports relate to incidents

Rename the Incident Report Taxonomy section to Report Taxonomy but
leave a reference label behind so we don't obliterate any of the
many old external links to this document.

While tidying this up, also switch the task status reference to use
an internal anchor rather than an explicit URL anchor link.

Change-Id: I49245922e08d702b7ec1c46403a0db84dbad2882

doc/source/vmt-process.rst

@@ -72,14 +72,12 @@ ossa bugtask will be set to *Won't Fix* or *Invalid* (depending on
 the tracker and situation) and the bug state switched from *Private
 Security* to *Public*, optionally adding a *security* bug tag if the
 report concerns a potential security hardening opportunity. The
-specifics are indexed in the `report taxonomy`_ and `task status`_
+specifics are indexed in the `report taxonomy` and :ref:`task status`
 tables.
 
 .. _embargo reminder: #reception-embargo-reminder-private-issues
 .. _incomplete reception: #reception-incomplete-message-unconfirmed-issues
 .. _OSSN: https://wiki.openstack.org/wiki/Security_Notes
-.. _report taxonomy: #incident-report-taxonomy
-.. _task status: #ossa-task-status
 
 Patch development
 ^^^^^^^^^^^^^^^^^
@@ -250,8 +248,10 @@ significant details of the report are disclosed in a public venue,
 the embargo is terminated by a VMT coordinator at that time and
 subsequent process switches to the public report workflow instead.
 
-Incident Report Taxonomy
-------------------------
+.. _incident report taxonomy:
+
+Report Taxonomy
+---------------
 
 The VMT is now using this classification list in order to assist
 vulnerability report triage, especially whenever a bug does not
@@ -297,6 +297,8 @@ warrant an advisory.
 | Class Z  |           | When due process fails                    |
 +----------+-----------+-------------------------------------------+
 
+.. _task status:
+
 OSSA Task status
 ----------------