diff --git a/releasenotes/notes/1500-default-mtu-b0d6e4ab193b62a4.yaml b/releasenotes/notes/1500-default-mtu-b0d6e4ab193b62a4.yaml
index bd7af3edf3d..1629c372c84 100644
--- a/releasenotes/notes/1500-default-mtu-b0d6e4ab193b62a4.yaml
+++ b/releasenotes/notes/1500-default-mtu-b0d6e4ab193b62a4.yaml
@@ -1,6 +1,6 @@
 ---
 prelude: >
-  - The ML2 plug-in supports calculating the MTU for instances
+    The ML2 plug-in supports calculating the MTU for instances
     using overlay networks by subtracting the overlay protocol
     overhead from the value of 'path_mtu', ideally the physical
     (underlying) network MTU, and providing the smaller value to
diff --git a/releasenotes/notes/1500-default-segment-mtu-54e2cf6aea9602d5.yaml b/releasenotes/notes/1500-default-segment-mtu-54e2cf6aea9602d5.yaml
index b8d00ed5974..80026838789 100644
--- a/releasenotes/notes/1500-default-segment-mtu-54e2cf6aea9602d5.yaml
+++ b/releasenotes/notes/1500-default-segment-mtu-54e2cf6aea9602d5.yaml
@@ -1,6 +1,6 @@
 ---
 prelude: >
-  - The ML2 plug-in supports calculating the MTU for networks
+    The ML2 plug-in supports calculating the MTU for networks
     that are realized as flat or VLAN networks, by consulting the
     'segment_mtu' option. Prior to Mitaka, 'segment_mtu' defaults to 0 which
     disables this feature. This creates slightly confusing API results when