diff --git a/network_data.yaml b/network_data.yaml
index 7d96eec532..ed859cc12a 100644
--- a/network_data.yaml
+++ b/network_data.yaml
@@ -31,8 +31,8 @@
 #   allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}]
 #   gateway_ip: '10.0.2.254'
 #
-# To support backward compatility, two versions of the network definitions will
-# be created, network/<network>.yaml and network/<network>_v6.yaml. Only
+# To support backward compatibility, two versions of the network definitions
+# will be created, network/<network>.yaml and network/<network>_v6.yaml. Only
 # one of these files may be used in the deployment at a time, since the
 # parameters used for configuration are the same in both files. In the
 # future, this behavior may be changed to create only one file for custom
diff --git a/network_data_ganesha.yaml b/network_data_ganesha.yaml
index df30f52355..37593ad49e 100644
--- a/network_data_ganesha.yaml
+++ b/network_data_ganesha.yaml
@@ -31,8 +31,8 @@
 #   allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}]
 #   gateway_ip: '10.0.2.254'
 #
-# To support backward compatility, two versions of the network definitions will
-# be created, network/<network>.yaml and network/<network>_v6.yaml. Only
+# To support backward compatibility, two versions of the network definitions
+# will be created, network/<network>.yaml and network/<network>_v6.yaml. Only
 # one of these files may be used in the deployment at a time, since the
 # parameters used for configuration are the same in both files. In the
 # future, this behavior may be changed to create only one file for custom