Clarify the License FAQ regarding permissive licenses

cc slint-ui#184
task-jp · Mar 4, 2021 · aa4101c · aa4101c
1 parent f4059ab
commit aa4101c
Showing 1 changed file with 3 additions and 4 deletions.
diff --git a/FAQ.md b/FAQ.md
@@ -74,7 +74,6 @@ developing needs to be accounted for. However, support for bug fixes requires a
 
 ## I want to develop a free software product using SixtyFPS, but I don't like the GPL and prefer to use a non-copyleft license.
 
-You can still release your own source code under a permissisive license such as BSD, MIT, or Apache license. 
-Only binary distribution needs to comply to the terms of the GPL. It is up to those who want to distribute a
-non-free version of the application to acquire a commercial license.
-
+You can still publish your own source code under a permissisive license compatible with the GPL, such as BSD, MIT, or Apache license.
+The distribution of a binary or a package containing SixtyFPS still needs to be licensed under the GPL.
+It is up to those who want to distribute a non-free version of the application to acquire a commercial license.