update for chanflags-1.6.0.xml



Please find:

<subsection>
<title>Default</title>
<p>
<emphasis type="strong">Syntax:</emphasis>
<command>
/msg ChanServ@services.dal.net XFLAG
<param>#channel</param>
<param>DEFAULT</param>
</command>
</p>
  <p> <emphasis type="strong">Information:</emphasis> This option will 
  reset all eXtended flags to off and 0.</p>
</subsection>
</section>



After the section you add this and translate it please:



<section>
<title>Frequently Asked Questions</title>
<p>In Sunday, the 25th of November 2018, DALnet planned for services training session about the new DALnet Services features!. The session was about XFLAG and others
features that were not released yet. At the end of the session, DALnet did a Frequently Asked Questions session, and in this section you will read some of users questions</p>
<list type="text">
<item>
<title>Q: What works best for JOIN_CONNECT_TIME and is the value in seconds?</title>
<p>
A: /ChanServ XFLAG #channel JOIN_CONNECT_TIME:30 and Yes its in seconds.
</p>
</item>
<item>
<title>Q: Can we change GREETMSG?</title>
<p>A: No, you can only use a default premade greeting with the following command. /ChanServ XFLAG #channel AUTOMSG:ON
</p>
</item>
<item>
<title>Q: Is there a maximum integer value for any of the time settings?</title>
<p>A: Any number between 0 to 2592000 should be fine</p>
</item>
<item>
<title>Q: Does blocking CTCP also block CTCP ACTION (aka a /me command)?</title>
<p>A: Yes, NO_CTCP also blocks actions (/me something)</p>
</item>
<item>
<title>Q: What about the channels that the founders and managers are away. How can the ops set these commands to prevent flooders?</title>
<p>A: A channel must have a founder set, you should be able to send a memo to the founder.
 If you can't reach the founder at all, join #OperHelp and we will try to help you.</p> 
 </item>
 <item>
 <title>Q: Could add a help to show what RECOMMENDED does, assuming it will change</title>
 <p>A: The recommended feature currently enables the following xflags:</p>
 <p>NO_NOTICE:ON, NO_CTCP:ON, NO_PART_MSG:ON, NO_QUIT_MSG:ON, EXEMPT_OPPED:ON, EXEMPT_VOICED:ON, EXEMPT_REGISTERED:ON, EXEMPT_INVITES:ON, HIDE_MODE_LISTS:ON, 
 AUTOMSG:ON, TALK_JOIN_TIME:30</p>
 </item>
 <item>
 <title>Q: What could XFLAG do, that my bot can't?</title>
 <p>A: It adds more tools to help you prevent thousands of drones from thousands of IP addresses from joining your channel, instead of just being limited to 
 things like setting mode +R (registered nicks only).</p>
 </item>
 <item>
 <title>Q: Can I use the RECOMMENDED option for XFLAG and turn off EXEMPT_IDENTD ?</title>
 <p>A: Yes. You can do /ChanServ XFLAG #channel RECOMMENDED and then tweak the options.</p>
 </item>
 <item>
 <title>Q: With the no_ctcp, it blocks someone from user info, is that valid only for as long as that person is in the channel?</title>
 <p>A: No private ctcps. It only prevents /ctcp request to the channel, 
 i.e. /ctcp #channel ping</p>
 </item>
 </list>
 <p><emphasis type="strong">NOTE:</emphasis> Here is the link of the session <url>https://www.dal.net/kb/view.php?kb=430</url>.</p>
 </section>



Rename file to chanflagsXX-1.6.0.xml and send it back to Fredfred :)