fix xml errors in EN msecgui.xml

1 files changed, 93 insertions, 81 deletions

diff --git a/docs/mcc-help/en/msecgui.xml b/docs/mcc-help/en/msecgui.xml
index 2a4b14ba..4c201016 100644
--- a/docs/mcc-help/en/msecgui.xml
+++ b/docs/mcc-help/en/msecgui.xml
@@ -7,7 +7,6 @@
 
   <!-- written by Lebarhon 2014/01/03 To be checked-->
 
-  <para/>
 
   <mediaobject>
     <imageobject>
@@ -15,13 +14,14 @@
     </imageobject>
   </mediaobject>
 
-  <para/>
 
   <section>
     <title>Presentation</title>
 
-    <para>msecgui is a graphic user interface for msec that allows to
-    configure your system security according to two approaches:</para>
+    <para>msecgui<footnote><para>You can start this tool from the command 
+    line, by typing <emphasis role="bold">msecgui</emphasis> as root.</para>
+    </footnote> is a graphic user interface for msec that allows to configure 
+    your system security according to two approaches:</para>
 
     <itemizedlist>
       <listitem>
@@ -29,8 +29,10 @@
         system to make it more secure.</para>
       </listitem>
 
-      <listitem>It carries on periodic checks automatically on the system in
-      order to warn you if something seems dangerous.</listitem>
+      <listitem>
+	 <para>It carries on periodic checks automatically on the system in
+		 order to warn you if something seems dangerous.</para>
+      </listitem>
     </itemizedlist>
 
     <para>msec uses the concept of "security levels" which are intended to
@@ -93,7 +95,6 @@
       </imageobject>
     </mediaobject>
 
-    <para/>
 
     <section>
       <title>Basic security tab</title>
@@ -117,12 +118,14 @@
           doing, as it would leave your system vulnerable to attack.</para>
         </listitem>
 
-        <listitem>Level <emphasis role="bold">standard</emphasis>. This is the
+	<listitem>
+	  <para>Level <emphasis role="bold">standard</emphasis>. This is the
         default configuration when installed and is intended for casual users.
         It constrains several system settings and executes daily security
         checks which detect changes in system files, system accounts, and
         vulnerable directory permissions. (This level is similar to levels 2
-        and 3 from past msec versions).</listitem>
+	and 3 from past msec versions).</para>
+        </listitem>
 
         <listitem>
           <para>Level <emphasis role="bold">secure</emphasis>. This level is
@@ -133,13 +136,21 @@
           versions).</para>
         </listitem>
 
-        <listitem>Besides those levels, different task-oriented security are
-        also provided, such as the <emphasis role="bold">fileserver</emphasis>, <emphasis role="bold">webserver</emphasis> and <emphasis role="bold">netbook</emphasis> levels. Such levels attempt to
-        pre-configure system security according to the most common use
-        cases.</listitem>
+	<listitem>
+	  <para>Besides those levels, different task-oriented security are
+          also provided, such as the <emphasis role="bold">fileserver
+	  </emphasis>, <emphasis role="bold">webserver</emphasis> and 
+	  <emphasis role="bold">netbook</emphasis> levels. Such levels 
+	  attempt to pre-configure system security according to the most common
+	  use cases.</para>
+        </listitem>
 
-        <listitem>The last two levels called <emphasis role="bold">audit_daily</emphasis> and <emphasis role="bold">audit_weekly</emphasis> are not really security levels but
-        rather tools for periodic checks only.</listitem>
+	<listitem>
+          <para>The last two levels called <emphasis role="bold">audit_daily
+          </emphasis> and <emphasis role="bold">audit_weekly</emphasis> are 
+	  not really security levels but rather tools for periodic checks 
+	  only.</para>
+        </listitem>
       </orderedlist>
 
       <para>These levels are saved in
@@ -150,8 +161,10 @@
       intended for power users which require a customised or more secure
       system configuration.</para>
 
-      <caution>Keep in mind that user-modified parameters take precedence over
-      default level settings.</caution>
+      <caution>
+	<para>Keep in mind that user-modified parameters take precedence over
+        default level settings.</para>
+      </caution>
 
       <para>
         <emphasis role="underline">Security alerts:</emphasis>
@@ -165,13 +178,14 @@
       last, you can receive the security alerts directly on your desktop.
       Check the relevant box to enable it.</para>
 
-      <important>It is strongly advisable to enable the security alerts option
+      <important>
+	<para>It is strongly advisable to enable the security alerts option
       in order to immediately inform the security administrator of possible
       security problems. If not, the administrator will have to regularly
       check the logs files available in
-      <filename>/var/log/security.</filename></important>
+      <filename>/var/log/security.</filename></para></important>
 
-      <emphasis role="underline">Security options:</emphasis>
+      <para><emphasis role="underline">Security options:</emphasis></para>
 
       <para>Creating a customised level is not the only way to customise the
       computer security, it is also possible to use the tabs presented here
@@ -200,34 +214,24 @@
       the new value can be selected. Click on the <guibutton>OK</guibutton>
       button to validate the choice.</para>
 
-      <para>
-        <figure>
-          <screenshot>
-            <mediaobject>
-              <imageobject>
-                <imagedata fileref="msecgui11.png"/>
-              </imageobject>
-            </mediaobject>
-          </screenshot>
-        </figure>
-      </para>
+      <mediaobject>
+        <imageobject>
+          <imagedata fileref="msecgui11.png"/>
+        </imageobject>
+      </mediaobject>
 
-      <caution>Do not forget when leaving msecgui to save definitively your
+      <caution>
+      <para>Do not forget when leaving msecgui to save definitively your
       configuration using the menu <guimenu>File -> Save the
       configuration</guimenu>. If you have changed the settings, msecgui
-      allows you to preview the changes before saving them.</caution>
+      allows you to preview the changes before saving them.</para>
+      </caution>
 
-      <para>
-        <figure>
-          <screenshot>
-            <mediaobject>
-              <imageobject>
-                <imagedata fileref="msecgui10.png"/>
-              </imageobject>
-            </mediaobject>
-          </screenshot>
-        </figure>
-      </para>
+      <mediaobject>
+        <imageobject>
+          <imagedata fileref="msecgui10.png"/>
+        </imageobject>
+      </mediaobject>
     </section>
 
     <section>
@@ -295,66 +299,74 @@
       clicK.</para>
     </section>
 
-    <section><title>Permissions</title><para>This tab is intended for file and
-    directory permissions checking and enforcement.</para><para>Like for the
-    security, msec owns different permissions levels (standard, secure, ..),
-    they are enabled accordingly with the chosen security level. You can
-    create your own customised permissions levels, saving them into specific
-    files called <filename>perm.&lt;levelname></filename> placed into the
-    folder <filename>etc/security/msec/</filename>. This function is intended
-    for power users which require a customised configuration. It is also
-    possible to use the tab presented here after to change any permission you
-    want. Current configuration is stored in
+    <section>
+    <title>Permissions</title>
+    <para>This tab is intended for file and directory permissions checking and
+    enforcement.</para>
+    <para>Like for the security, msec owns different permissions levels
+    (standard, secure, ..), they are enabled accordingly with the chosen
+    security level. You can create your own customised permissions levels,
+    saving them into specific files called <filename>perm.&lt;levelname>
+    </filename> placed into the folder <filename>etc/security/msec/</filename>
+    . This function is intended for power users which require a customised
+    configuration. It is also possible to use the tab presented here after to
+    change any permission you want. Current configuration is stored in
     <filename>/etc/security/msec/perms.conf.</filename> This file contains the
-    list of all the modifications done to the permissions.</para><mediaobject>
+    list of all the modifications done to the permissions.</para>
+      <mediaobject>
         <imageobject>
           <imagedata fileref="msecgui8.png"/>
         </imageobject>
-      </mediaobject><para>Default permissions are visible as a list of rules
+	</mediaobject>
+    <para>Default permissions are visible as a list of rules
     (a rule per line). You can see on the left side, the file or folder
     concerned by the rule, then the owner, then the group and then the
-    permissions given by the rule. If, for a given rule:</para><itemizedlist>
+    permissions given by the rule. If, for a given rule:</para>
+   <itemizedlist>
         <listitem>
           <para>the box <guilabel>Enforce</guilabel> is not checked, msec only
           checks if the defined permissions for this rule are respected and
           sends an alert message if not, but does not change anything.</para>
         </listitem>
 
-        <listitem>the box <guilabel>Enforce</guilabel> is checked, then msec
+	<listitem>
+	  <para>the box <guilabel>Enforce</guilabel> is checked, then msec
         will rule the permissions respect at the first periodic check and
-        overwrite the permissions.</listitem>
-      </itemizedlist><important>For this to work, the option CHECK_PERMS in
+	overwrite the permissions.</para></listitem>
+   </itemizedlist>
+   <important><para>For this to work, the option CHECK_PERMS in
     the <emphasis role="bold">Periodic check tab</emphasis> must be configured
-    accordingly.</important>To create a new rule, click on the<guibutton> Add
-    a rule</guibutton> button and fill the fields as shown in the example
-    below. The joker * is allowed in the <guilabel>File</guilabel> field.
-    “current” means no modification.<mediaobject>
+    accordingly.</para></important><para>To create a new rule, click on the
+    <guibutton> Add a rule</guibutton> button and fill the fields as shown in
+    the example below. The joker * is allowed in the <guilabel>File</guilabel>
+    field. “current” means no modification.</para>
+     <mediaobject>
         <imageobject>
           <imagedata fileref="msecgui9.png"/>
         </imageobject>
-      </mediaobject><para>Click on the <guibutton>OK</guibutton> button to
+	</mediaobject>
+    <para>Click on the <guibutton>OK</guibutton> button to
     validate the choice and do not forget when leaving to save definitively
     your configuration using the menu <guimenu>File -> Save the
     configuration</guimenu>. If you have changed the settings, msecgui allows
-    you to preview the changes before saving them. </para><note>It is also
-    possible to create or modify the rules by editing the configuration file
-    <filename>/etc/security/msec/perms.conf</filename>.
-    </note><caution>Changes in the <emphasis role="bold">Permission
+    you to preview the changes before saving them. </para>
+    <note><para>It is also possible to create or modify the rules by editing
+    the configuration file <filename>/etc/security/msec/perms.conf</filename>.
+    </para></note>
+    <caution><para>Changes in the <emphasis role="bold">Permission
     tab</emphasis> (or directly in the configuration file) are taken into
     account at the first periodic check (see the option CHECK_PERMS in the
     <emphasis role="bold">Periodic checks tab</emphasis>). If you want them to
     be taken immediately into account, use the msecperms command in a console
     with root rights. You can use before, the msecperms -p command to know the
-    permissions that will be changed by msecperms.</caution><caution>Do not
-    forget that if you modify the permissions in a console or in a file
-    manager, for a file where the box <guilabel>Enforce</guilabel> is checked
-    in the <emphasis role="bold">Permissions tab</emphasis>, msecgui will
-    write the old permissions back after a while, accordingly to the
-    configuration of the options CHECK_PERMS and CHECK_PERMS_ENFORCE in the
-    <emphasis role="bold">Periodic Checks tab</emphasis>.</caution></section>
+    permissions that will be changed by msecperms.</para></caution>
+    <caution><para>Do not forget that if you modify the permissions in a
+    console or in a file manager, for a file where the box <guilabel>Enforce
+    </guilabel> is checked in the <emphasis role="bold">Permissions tab
+    </emphasis>, msecgui will write the old permissions back after a while,
+    accordingly to the configuration of the options CHECK_PERMS and
+    CHECK_PERMS_ENFORCE in the <emphasis role="bold">Periodic Checks tab
+    </emphasis>.</para></caution>
+   </section>
   </section>
-
-  <para>You can start this tool from the command line, by typing <emphasis role="bold">msecgui</emphasis> as root.</para>
-
-  <para/>
-</section>
\ No newline at end of file
+</section>