commit 2ee29d169fae2d49dec6f730d9bfc09054b3767c
author Robert Scholte <rfscholte@apache.org> Fri Aug 03 10:04:31 2018 +0200
committer GitHub <noreply@github.com> Fri Aug 03 10:04:31 2018 +0200
tree 218e722a18f5e462c6a2ee5f1917689d415a0285
parent f38336f2ac0fe96753fca3e46533a0cc91a45616

[MASSEMBLY-893] Typo in FAQ

src/site/fml/faq.fml

diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index cdf39f7..cc9cad2 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -99,7 +99,7 @@
            to be adjusted or have the files they reference moved into the new child module alongside the descriptor itself.
         </p>
         <p>In cases where you absolutely must use module-binaries references, you should create an assembly-child POM mentioned above, then insert
-           <code>&lt;useAllReactorProjects&gt;true&lt;useAllReactorProjects&gt;</code> to each of your <code>moduleSet</code> sections. Then, bind the assembly
+           <code>&lt;useAllReactorProjects&gt;true&lt;/useAllReactorProjects&gt;</code> to each of your <code>moduleSet</code> sections. Then, bind the assembly
            in your assembly-child POM (normally to the <code>package</code> phase) using the <code>single</code> goal. When you execute the build from the top-level POM,
            Maven should generated your assembly in the new child project.
         </p>