Better wording for comments in config

Fixes https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/274

conf.d/09-autohint-if-no-hinting.conf

@@ -6,10 +6,10 @@
   <match target="font">
     <test name="fonthashint"><bool>false</bool></test>
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="autohint" mode="append"><bool>true</bool></edit>
   </match>

conf.d/10-autohint.conf

@@ -5,10 +5,10 @@
 <!--  Use the Autohinter --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="autohint" mode="append"><bool>true</bool></edit>
   </match>

conf.d/10-hinting-full.conf

@@ -5,10 +5,10 @@
 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="hintstyle" mode="append"><const>hintfull</const></edit>
   </match>

conf.d/10-hinting-medium.conf

@@ -5,10 +5,10 @@
 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="hintstyle" mode="append"><const>hintmedium</const></edit>
   </match>

conf.d/10-hinting-none.conf

@@ -5,10 +5,10 @@
 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="hintstyle" mode="append"><const>hintnone</const></edit>
   </match>

conf.d/10-hinting-slight.conf

@@ -5,10 +5,10 @@
 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="hintstyle" mode="append"><const>hintslight</const></edit>
   </match>

conf.d/10-no-sub-pixel.conf

@@ -5,10 +5,10 @@
 <!--  Disable sub-pixel rendering --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="rgba" mode="append"><const>none</const></edit>
   </match>

conf.d/10-sub-pixel-bgr.conf

@@ -5,10 +5,10 @@
 <!--  Enable sub-pixel rendering --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="rgba" mode="append"><const>bgr</const></edit>
   </match>

conf.d/10-sub-pixel-rgb.conf

@@ -5,10 +5,10 @@
 <!--  Enable sub-pixel rendering --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="rgba" mode="append"><const>rgb</const></edit>
   </match>

conf.d/10-sub-pixel-vbgr.conf

@@ -5,10 +5,10 @@
 <!--  Enable sub-pixel rendering --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="rgba" mode="append"><const>vbgr</const></edit>
   </match>

conf.d/10-sub-pixel-vrgb.conf

@@ -5,10 +5,10 @@
 <!--  Enable sub-pixel rendering --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="rgba" mode="append"><const>vrgb</const></edit>
   </match>

conf.d/10-unhinted.conf

@@ -5,10 +5,10 @@
 <!--  Disable hinting --> 
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit name="hinting" mode="append"><bool>false</bool></edit>
   </match>

conf.d/11-lcdfilter-default.conf

@@ -5,10 +5,10 @@
 <!--  Use lcddefault as default for LCD filter -->
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit mode="append" name="lcdfilter">
       <const>lcddefault</const>

conf.d/11-lcdfilter-legacy.conf

@@ -5,10 +5,10 @@
 <!--  Use lcdlegacy as default for LCD filter -->
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit mode="append" name="lcdfilter">
       <const>lcdlegacy</const>

conf.d/11-lcdfilter-light.conf

@@ -5,10 +5,10 @@
 <!--  Use lcdlight as default for LCD filter -->
   <match target="pattern">
     <!--
-      This configuration is available on the major desktop environments.
+      This sort of configuration is available on the major desktop environments
-      We shouldn't overwrite it with "assign" unconditionally.
+      and we don't have to break it with "assign" unconditionally. however, we
-      Most clients may picks up the first value only. so using "append"
+      want to set something for others. So we use "append" here to get this working
-      may simply works to avoid it.
+      in both cases so that most clients would takes a look at the first place only.
     -->
     <edit mode="append" name="lcdfilter">
       <const>lcdlight</const>