Fix up release notes for 14.0.0

Change-Id: I10286c48ddf3b7fba020db6175d5faa1c0911141

releasenotes/notes/add_retirement_support-23c5fed7ce8f97d4.yaml

@@ -3,7 +3,7 @@ features:
   - |
     Adds support for node retirement by adding a ``retired`` property
     to the node. If set, a node moves upon automatic cleaning to
-    ``manageable`` (rather than ``available``). The new property can also
+    ``manageable`` (rather than ``available``). The new property also
-    block the provide keyword, i.e. nodes cannot move from ``manageable``
+    blocks the ``provide`` keyword, i.e. nodes cannot move from ``manageable``
-    to ``available``. Furthermore, there is an additional optional property
+    to ``available``. Furthermore, there is an additional optional field
     ``retirement_reason`` to store the reason for the node's retirement.

releasenotes/notes/ansible-loops-de0eef0d5b79a9ff.yaml

@@ -1,5 +1,5 @@
 ---
 upgrade:
   - |
-    Changing minimum version of Ansible for use with the ``ansible``
+    Changes the minimum version of Ansible for use with the ``ansible``
     ``deploy_interface`` to version 2.5.

releasenotes/notes/configdrive-vendordata-122049bd7c6e1b67.yaml

@@ -3,6 +3,6 @@ features:
   - |
     Adds support for specifying vendor_data when building config drives.
     Starting with API version 1.59, a JSON based ``configdrive`` parameter to
-    ``/v1/nodes/<node>/states/provision`` can include the key vendor_data.
+    ``/v1/nodes/<node>/states/provision`` can include the key ``vendor_data``.
     This data will be built into the configdrive contents as
-    vendor_data2.json.
+    ``vendor_data2.json``.

releasenotes/notes/fix-commit-to-controller-d26f083ac388a65e.yaml

@@ -4,5 +4,5 @@ fixes:
     for RAID ``delete_configuration`` cleaning step gets created even
     when there are no virtual disks or hotspares/dedicated hotspares
     present on any controller.
-    See bug `2006562 https://storyboard.openstack.org/#!/story/2006562`
+    See bug `2006562 <https://storyboard.openstack.org/#!/story/2006562>`_
     for details.

releasenotes/notes/fix-delete_configuration-with-multiple-controllers-06fc3fca94ba870f.yaml

@@ -5,5 +5,5 @@ fixes:
     realtime mode and some do not. The approach is to use only realtime
     mode if all controllers support realtime. This removes the race
     condition.
-    See bug `2006502 https://storyboard.openstack.org/#!/story/2006502`
+    See bug `2006502 <https://storyboard.openstack.org/#!/story/2006502>`_
-    for details
+    for details.

releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml

@@ -2,7 +2,7 @@
 fixes:
   - |
     Fixes issue where the resource list API returned results with requested
-    fields only until the API MAX_LIMIT. After the API MAX_LIMIT is reached the
+    fields only until the API ``MAX_LIMIT``. After the API ``MAX_LIMIT`` is
-    API started ignoring user requested fields. This fix will make sure that
+    reached the API started ignoring user requested fields. This fix will make
-    the next url generated by the pagination code will include the user
+    sure that the next url generated by the pagination code will include the
-    requested fields as query parameter.
+    user requested fields as query parameter.

releasenotes/notes/fix-path-a3a0cfd2c135ace9.yaml

@@ -1,5 +1,5 @@
 ---
 fixes:
   - |
-    Fix path used to virtual media iso, when served over
+    Fixes virtual media boot when served using a local HTTP server,
-    local HTTP server([redfish]use_swift=false).
+    i.e. ``[redfish]use_swift`` is ``false``.

releasenotes/notes/fix_pending_non_bios_job_execution-4b22e168ac915f4f.yaml

@@ -6,5 +6,5 @@ fixes:
     (E.g. create/delete virtual disk) were not being deleted before
     job execution.
 
-    See bug `2006580 https://storyboard.openstack.org/#!/story/2006580`
+    See bug `2006580 <https://storyboard.openstack.org/#!/story/2006580>`_
-    for details
+    for details.

releasenotes/notes/no-localhost-596adedfe388dfae.yaml

@@ -1,7 +0,0 @@
----
-upgrade:
-  - |
-    Using localhost as the Bare Metal Introspection endpoint will not work
-    when managed boot is used for in-band inspection. Either update the
-    endpoint to a real IP address or use the new configuration option
-    ``[inspector]callback_endpoint_override``.

releasenotes/notes/node-owner-policy-d7168976bba70566.yaml

@@ -1,6 +1,6 @@
 ---
 features:
-  - Adds a ``is_node_owner`` policy rule. This rule can be used with node
+  - Adds an ``is_node_owner`` policy rule. This rule can be used with node
     policy rules in order to expose specific node APIs to a project ID
     specified by a node's ``owner`` field. Default rules are unaffected,
     so default behavior is unchanged.

releasenotes/notes/ramdisk-params-6083bfaa7ffa9dfe.yaml

@@ -1,6 +1,6 @@
 ---
 upgrade:
   - |
-    The operators using custom PXE/iPXE/Grub templates should update them to
+    Operators using custom PXE/iPXE/Grub templates should update them to
     remove an explicit mention of ``ipa-api-url``. This field is now a part
     of ``pxe_append_params`` when required.

releasenotes/notes/sofware_raid_use_rootfs_uuid-f61eb671d696d251.yaml

@@ -9,5 +9,5 @@ upgrade:
     of the deployed image is in the first partition. Instead, it will use
     the UUID passed from the conductor. Operators need hence to make sure
     that the conductor has the correct UUID (which either comes from the
-    'rootfs_uuid' field in the image metadata or from the
+    ``rootfs_uuid`` field in the image metadata or from the
-    'root_uuid_or_disk_id' in the nodes 'internal_driver_info'.)
+    ``root_uuid_or_disk_id`` in the node's ``internal_driver_info``.)