More precise language regarding JUCE tiers

timothyschoen · web-flow · commit c9fe03e78b11 · 2025-07-31T12:00:07.000+02:00
diff --git a/README.md b/README.md
@@ -61,4 +61,4 @@ Example:
 
 
 # Licensing note
-After building, the original patch file you used is directly accessible via the “Info” menu in the plugin. This is required to comply with the GPL license (required by both plugdata and the JUCE free tier), as your patch could now legally be considered as "source code" of the generated plugins.
+After building, the original patch file you used is directly accessible via the “Info” menu in the plugin. This is required to comply with the GPL license (required by both plugdata and the JUCE GPL tier), as your patch could now legally be considered as "source code" of the generated plugins.

Original file line number	Diff line number	Diff line change
`@@ -61,4 +61,4 @@ Example:`
`61`	`61`
`62`	`62`
`63`	`63`	`# Licensing note`
`64`		`-After building, the original patch file you used is directly accessible via the “Info” menu in the plugin. This is required to comply with the GPL license (required by both plugdata and the JUCE free tier), as your patch could now legally be considered as "source code" of the generated plugins.`
	`64`	`+After building, the original patch file you used is directly accessible via the “Info” menu in the plugin. This is required to comply with the GPL license (required by both plugdata and the JUCE GPL tier), as your patch could now legally be considered as "source code" of the generated plugins.`