Correct FAQ.

docs/index.html

@@ -473,5 +473,5 @@ <h4 class="modal-title" id="keyboardModalLabel">Keyboard Shortcuts</h4>
 
 <!--
 MkDocs version : 1.5.3
-Build Date UTC : 2024-10-28 11:19:09.766663+00:00
+Build Date UTC : 2024-11-04 20:43:41.995386+00:00
 -->

docs/manual/faq/index.html

@@ -473,8 +473,8 @@ <h2 id="pattern-matching-and-lists">Pattern matching and lists</h2>
 </code></pre>
 <p>Please note that pattern matching is not limited to parallel composition, the other composition operators <code>(&lt;: : :&gt; ~)</code> can be used too.</p>
 <h2 id="what-is-the-situation-about-faust-compiler-licence-and-the-deployed-code">What is the situation about Faust compiler licence and the deployed code?</h2>
-<p><em>Q: Does the Faust license (GPL) apply somehow to the code exports that it produces as well? Or can the license of the exported code be freely chosen such that one could develop commercial software (e.g. VST plug-ins) using Faust?</em></p>
-<p>A: You can freely use Faust to develop commercial software. The GPL license of the compiler <em>doesn't</em> apply to the code generated by the compiler. </p>
+<p><em>Q: Does the Faust license (LGPL) apply somehow to the code exports that it produces as well? Or can the license of the exported code be freely chosen such that one could develop commercial software (e.g. VST plug-ins) using Faust?</em></p>
+<p>A: You can freely use Faust to develop commercial software. The LGPL license of the compiler <em>doesn't</em> apply to the code generated by the compiler. </p>
 <p>The license of the code generated by the Faust compiler depends only on the licenses of the input files. You should therefore check the licenses of the Faust libraries used and the architecture files. On the whole, when used unmodified, Faust libraries and architecture files are compatible with commercial, non-open source use.</p>
 <h2 id="surprising-effects-of-vgrouphgroup-on-how-controls-and-parameters-work">Surprising effects of vgroup/hgroup on how controls and parameters work</h2>
 <p>User interface widget primitives like <code>button</code>, <code>vslider/hslider</code>, <code>vbargraph/hbargraph</code> allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hierarchical manner using <code>vgroup/hgroup/tgroup</code> primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.</p>

src/manual/faq.md

@@ -150,9 +150,9 @@ Please note that pattern matching is not limited to parallel composition, the ot
 
 ## What is the situation about Faust compiler licence and the deployed code?
 
-*Q: Does the Faust license (GPL) apply somehow to the code exports that it produces as well? Or can the license of the exported code be freely chosen such that one could develop commercial software (e.g. VST plug-ins) using Faust?*
+*Q: Does the Faust license (LGPL) apply somehow to the code exports that it produces as well? Or can the license of the exported code be freely chosen such that one could develop commercial software (e.g. VST plug-ins) using Faust?*
 
-A: You can freely use Faust to develop commercial software. The GPL license of the compiler *doesn't* apply to the code generated by the compiler. 
+A: You can freely use Faust to develop commercial software. The LGPL license of the compiler *doesn't* apply to the code generated by the compiler. 
 
 The license of the code generated by the Faust compiler depends only on the licenses of the input files. You should therefore check the licenses of the Faust libraries used and the architecture files. On the whole, when used unmodified, Faust libraries and architecture files are compatible with commercial, non-open source use.