Merge "Several editorial corrections and improvements"

[doctor.git] / docs / requirements / 05-implementation.rst

diff --git a/docs/requirements/05-implementation.rst b/docs/requirements/05-implementation.rst
index c72f209..8497977 100644 (file)
--- a/docs/requirements/05-implementation.rst
+++ b/docs/requirements/05-implementation.rst
@@ -728,7 +728,7 @@ rules and user and project id.
 +------------------------+------------------------+---------------------+---------------------------------------------+---------------------------------------+
 | faultType              | FaultType              | event_type in       | Type of the fault, e.g. “CPU failure” of a  | OpenStack Alarming (Aodh) can use a   |
 |                        |                        | reason_data         | compute resource, in machine interpretable  | fuzzy matching with wildcard string,  |
-|                        |                        |                     | format.                                       "compute.cpu.failure".                |
+|                        |                        |                     | format.                                     | "compute.cpu.failure".                |
 +------------------------+------------------------+---------------------+---------------------------------------------+---------------------------------------+
 | N/A                    | N/A                    | type = "event"      | Type of the notification. For fault         | \-                                    |
 |                        |                        |                     | notifications the type in AODH is “event”.  |                                       |
@@ -762,6 +762,7 @@ Other areas that need alignment is the so called alarm state in NFV. Here we mus
 however consider what can be attributes of the notification vs. what should be a
 property of the alarm instance. This will be analyzed later.
 
+.. _southbound:
 
 Detailed southbound interface specification
 -------------------------------------------