Make it clearer what is permitted purpose #88
Description
As it stands the the term permitted purpose is mentioned several places in the text, yet there's no section named "Permitted purpose". It would make the text a lot clearer if any such reference to the term permitted purpose could be linked to a section which describes what permitted purpose is.
It seems to me that the project has already accepted that the license text format is Markdown, and not plain-text. We are already at the point where license cannot be read and interpreted correctly without proper Markdown rendering*. This is perfectly acceptable in my opinion but if this is already accepted then I think for sure it is possible to make the licenses even more readable, in particular in relation to the permitted purpose term. In the following I continue along the path of using the Markdown features to make the license more readable.
This is what I propose: Whenever the term 'permitted purpose' is mentioned then hyperlink it to a section of that name. For example, consider this revision, where the term has been hyper-linked and there is now a section named 'permitted purpose', to the current revision. Which one is clearer? (obviously I think my proposal is way more clear)
This is not just me. It seems others are struggling too: By making this clearer you can avoid having questions like this one and this one.
*) By the way, if Markdown is the format, then a project should include the license in the root of the project repo (as is the convention) as a file named LICENSE.md rather than as a file named LICENSE. I think this should be noted on the web site. Naming of the file is important as it signals how the file must be rendered before it is read. This could potentially be important in a legal dispute. If the intention of the Polyform License Project is that the license must be read with Markdown rendering then please state this !!