diff --git a/pom.xml b/pom.xml
index b0cad12..3be34c8 100644
--- a/pom.xml
+++ b/pom.xml
@@ -95,6 +95,8 @@
     <!-- Test dependencies -->
     <dependency.jetty.version>9.4.51.v20230217</dependency.jetty.version>
     <ftpserver.version>1.2.0</ftpserver.version>
+    <!-- Doxia 2 -->
+    <maven-site-plugin.version>3.21.0</maven-site-plugin.version>
   </properties>
 
   <dependencyManagement>
diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index beb87ea..c600626 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -1,26 +1,21 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <faqs title="FAQ">
 
-<part id="" >
+<part id="FAQ" >
   <title>FAQ</title>
-  
   <faq id="stage-vs-merge-maven-repos">
     <question>maven-stage-plugin:stage versus wagon-maven-plugin:merge-maven-repos</question>
     <answer>
       <br/>
       Both are used to merge artifacts from one Maven repository to another with following differences;
-      
       <ul>
         <li><i>merge-maven-repos</i> is more generic and therefore supports more protocols. </li>
         <li><i>merge-maven-repos</i> supports both normal upload and "optimize" upload where
-          files are compressed into an archive which are then transferred, uncompressed and 
+          files are compressed into an archive which are then transferred, uncompressed and
           removed remotely. Wagon scp, scpexe, and sftp are known to support remote execution
           and therefore suitable for this type of optimization.</li>
       </ul>
      </answer>
    </faq>
-  
   </part>
-      
-  
 </faqs>