diff --git a/src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c b/src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c
index 18e21cbb7d..7e25e51099 100644
--- a/src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c
+++ b/src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c
@@ -40,48 +40,47 @@ main(int argc, char *argv[])
     const NMSettInfoSetting *sett_info_settings = nmtst_sett_info_settings();
     NMMetaSettingType        meta_type;
 
-    g_print(
-        "<!--\n"
-        "  This file is generated.\n"
-        "\n"
-        "  This XML contains meta data of NetworkManager connection profiles.\n"
-        "\n"
-        "  NetworkManager's connection profiles are a bunch of settings, and this\n"
-        "  contains the known properties. See also `man nm-settings-{dbus,nmcli,keyfile}`.\n"
-        "\n"
-        "  Note that there are different manifestations of these properties. We have them\n"
-        "  on the D-Bus API (`man nm-settings-dbus`), in keyfile format (`man "
-        "nm-settings-keyfile`)\n"
-        "  in libnm's NMConnection and NMSetting API, and in nmcli (`man nm-settings-nmcli`).\n"
-        "  There are similarities between these, but also subtle differencs. For example,\n"
-        "  a property might not be shown in nmcli, or a property might be named different\n"
-        "  on D-Bus or keyfile. Also, the data types may differ due to the differences of the\n"
-        "  technology.\n"
-        "\n"
-        "  This list of properties is not directly the properties as they are in any of\n"
-        "  those manifestations. Instead, it's a general idea that this property exists in\n"
-        "  NetworkManager. Whether and how it is represented in nmcli or keyfile, may differ.\n"
-        "  The XML however aims to provide information for various backends.\n"
-        "\n"
-        "  <setting> Attributes:\n"
-        "   \"name\": the name of the setting.\n"
-        "   \"gtype\": the typename of the NMSetting class in libnm.\n"
-        "\n"
-        "  <property> Attributes:\n"
-        "   \"name\": the name of the property.\n"
-        "   \"is-deprecated\": whether this property is deprecated.\n"
-        "   \"is-secret\": whether this property is a secret.\n"
-        "   \"is-secret-flags\": whether this property is a secret flags property.\n"
-        "   \"dbus-type\": if this property is exposed on D-Bus. In that case, this\n"
-        "       is the D-Bus type format. Also, \"name\" is the actual name of the field\n"
-        "   \"dbus-deprecated\": if this property is on D-Bus and that representation is\n"
-        "       deprecated. This usually means, that there is a replacement D-Bus property\n"
-        "       that should be used instead.\n"
-        "   \"gprop-type\": if this is a GObject property in the NMSetting class, this\n"
-        "       is the GParamSpec.value_type of the property.\n"
-        "   \"is-setting-option\": whether the property is implemented in libnm's NMSetting\n"
-        "       via the nm_setting_option_*() API.\n"
-        " -->\n");
+    g_print("<!--\n"
+            "  This file is generated.\n"
+            "\n"
+            "  This XML contains meta data of NetworkManager connection profiles.\n"
+            "\n"
+            "  NetworkManager's connection profiles are a bunch of settings, and this\n"
+            "  contains the known properties. See also `man nm-settings-{dbus,nmcli,keyfile}`.\n"
+            "\n"
+            "  Note that there are different manifestations of these properties. We have them\n"
+            "  on the D-Bus API (`man nm-settings-dbus`), in keyfile format (`man "
+            "nm-settings-keyfile`)\n"
+            "  in libnm's NMConnection and NMSetting API, and in nmcli (`man nm-settings-nmcli`).\n"
+            "  There are similarities between these, but also subtle differencs. For example,\n"
+            "  a property might not be shown in nmcli, or a property might be named different\n"
+            "  on D-Bus or keyfile. Also, the data types may differ due to the differences of the\n"
+            "  technology.\n"
+            "\n"
+            "  This list of properties is not directly the properties as they are in any of\n"
+            "  those manifestations. Instead, it's a general idea that this property exists in\n"
+            "  NetworkManager. Whether and how it is represented in nmcli or keyfile, may differ.\n"
+            "  The XML however aims to provide information for various backends.\n"
+            "\n"
+            "  <setting> Attributes:\n"
+            "   \"name\": the name of the setting.\n"
+            "   \"gtype\": the typename of the NMSetting class in libnm.\n"
+            "\n"
+            "  <property> Attributes:\n"
+            "   \"name\": the name of the property.\n"
+            "   \"is-deprecated\": whether this property is deprecated.\n"
+            "   \"is-secret\": whether this property is a secret.\n"
+            "   \"is-secret-flags\": whether this property is a secret flags property.\n"
+            "   \"dbus-type\": if this property is exposed on D-Bus. In that case, this\n"
+            "       is the D-Bus type format. Also, \"name\" is the actual name of the field\n"
+            "   \"dbus-deprecated\": if this property is on D-Bus and that representation is\n"
+            "       deprecated. This usually means, that there is a replacement D-Bus property\n"
+            "       that should be used instead.\n"
+            "   \"gprop-type\": if this is a GObject property in the NMSetting class, this\n"
+            "       is the GParamSpec.value_type of the property.\n"
+            "   \"is-setting-option\": whether the property is implemented in libnm's NMSetting\n"
+            "       via the nm_setting_option_*() API.\n"
+            " -->\n");
     g_print("<nm-setting-docs>\n");
     for (meta_type = 0; meta_type < _NM_META_SETTING_TYPE_NUM; meta_type++) {
         const NMSettInfoSetting                 *sis   = &sett_info_settings[meta_type];