Release notes cleanup for Pike release

Change-Id: I862fdd1d178445efaf2578949b1c2c00614396b3

5 files changed, 19 insertions, 16 deletions

diff --git a/releasenotes/notes/Collect_NIC_name_given_by_BIOS-657c68c0ae16365b.yaml b/releasenotes/notes/Collect_NIC_name_given_by_BIOS-657c68c0ae16365b.yaml
index 024b248c..0e528cc5 100644
--- a/releasenotes/notes/Collect_NIC_name_given_by_BIOS-657c68c0ae16365b.yaml
+++ b/releasenotes/notes/Collect_NIC_name_given_by_BIOS-657c68c0ae16365b.yaml
@@ -1,11 +1,14 @@
 ---
 features:
-  - Adds an extra field ``biosdevname`` (BIOS given NICs name) to network
-    interface inventory collected by ``default`` collector of
-    ironic-python-agent. Biosdevname utility is used for collecting bios given
-    NICs name.
+  - |
+    Collects the BIOS-given NIC's name and adds ``biosdevname`` field to the
+    network interface inventory collected by the ``default`` collector of IPA.
+    The utility ``biosdevname`` is used for this purpose.
 
+    This feature is not available for Debian-based and CoreOS images as
+    ``biosdevname`` is not packaged for Debian-based distributions.
 issues:
-  - Collecting the 'biosdevname' field on network interfaces is impossible on any
-    Debian-based images due to the missing 'biosdevname' utility. This includes
-    the CoreOS image, as the CoreOS image utilizes a Debian-based chroot.
+  - Collection of the BIOS-given names of network interfaces is not possible on
+    Debian-based images as the utility ``biosdevname`` is not available on
+    them. This applies to any CoreOS images as well, as they utilize a
+    Debian-based chroot.
diff --git a/releasenotes/notes/add-numa-topology-info-8c253fd9e56169f1.yaml b/releasenotes/notes/add-numa-topology-info-8c253fd9e56169f1.yaml
index 7f3b155c..bbd0aacd 100644
--- a/releasenotes/notes/add-numa-topology-info-8c253fd9e56169f1.yaml
+++ b/releasenotes/notes/add-numa-topology-info-8c253fd9e56169f1.yaml
@@ -1,4 +1,4 @@
 ---
 features:
-  - Adds new optional NUMA topology collector named ``numa_topology``.
+  - Adds a new optional NUMA topology collector named ``numa_topology``.
     It collects NUMA specific RAM, CPU and NIC information.
diff --git a/releasenotes/notes/correction-failure-output-when-downloading-image-39f93838d1ed2928.yaml b/releasenotes/notes/correction-failure-output-when-downloading-image-39f93838d1ed2928.yaml
index 5beadaf3..07f1af2f 100644
--- a/releasenotes/notes/correction-failure-output-when-downloading-image-39f93838d1ed2928.yaml
+++ b/releasenotes/notes/correction-failure-output-when-downloading-image-39f93838d1ed2928.yaml
@@ -1,3 +1,3 @@
 ---
 fixes:
-  - Correct message output when failed to download image.
+  - Shows correct output message when IPA fails to download image.
diff --git a/releasenotes/notes/fix-bytes-json-serializable-collected-logs-ad61022b287dc3e2.yaml b/releasenotes/notes/fix-bytes-json-serializable-collected-logs-ad61022b287dc3e2.yaml
index a959ca81..4942f1c4 100644
--- a/releasenotes/notes/fix-bytes-json-serializable-collected-logs-ad61022b287dc3e2.yaml
+++ b/releasenotes/notes/fix-bytes-json-serializable-collected-logs-ad61022b287dc3e2.yaml
@@ -1,6 +1,5 @@
 ---
 fixes:
-  - JSON serialization of logs collected for ironic-python-agent.
-    In python3 logs were encoded as byte strings, which can't be serialized.
-    Make sure that logs are encoded as text for both py2.7 and py3. See
+  - Fixes JSON serialization of logs by encoding them as text instead of byte
+    strings in IPA. This works for py2.7 as well as py3. See
     https://bugs.launchpad.net/ironic-python-agent/+bug/1668533 for details.
diff --git a/releasenotes/notes/multiple-lan-channels-ee32d80150f990bf.yaml b/releasenotes/notes/multiple-lan-channels-ee32d80150f990bf.yaml
index c66b86b3..9d812209 100644
--- a/releasenotes/notes/multiple-lan-channels-ee32d80150f990bf.yaml
+++ b/releasenotes/notes/multiple-lan-channels-ee32d80150f990bf.yaml
@@ -1,7 +1,8 @@
 ---
 fixes:
   - |
-    IPMI interface can be configured to use lan channel different than
-    a default one. In that case querying it will return 0.0.0.0 as an IP
-    address representing an interface lacking configuration. In order to get
-    the real IP address, we need to iterate through all the possible channels.
+    Fixes bug where it was assumed that all BMCs operated on the default LAN
+    channel. IPA now iterates through all the possible LAN channels for the
+    IP address and returns 0.0.0.0 if the IPMI interface is not configured. See
+    https://bugs.launchpad.net/ironic-python-agent/+bug/1702514
+    for more details.