Resolve conversations from #181 #208

Only did some minor changes (most of them are formatting) and resolving all conversations from #181

There is still one conversation open regarding the wording of the licence decision diagram.

Do you want to allow people to create proprietary (closed-source) projects with your code, or do you expect your project to remain small (e.g. less than 300 lines)?

@n mentioned:

This is a bit confusing since you are asking two different questions and the options are yes and no.

@tok replied with

Since the "or" has a logical meaning (Boolean logic) I think there's no ambiguity.

But I'm happy about suggestions with better wording.

I think that the wording is fine but I still wanted to mention this if there is anyone with a better idea

What about adding an "either"? That's commonly used to turn an A/B question in a boolean A or B question?!

Do you either want to allow people to create proprietary (closed-source) projects with your code, or do you expect your project to remain small (e.g. less than 300 lines)?

What about adding an "either"? That's commonly used to turn an A/B question in a boolean A or B question?!

"either A or B" is usually interpreted as "A XOR B". A excludes B and B excludes A. It means mutual exclusion.
However, in this case it really should be a logical OR: the case matches also when both questions can be answered with yes.

Yes XOR Yes = No
Yes OR Yes = Yes

An alternative suggestion:

Is at least one of the following statements true for your project?
* You want to allow people to create proprietary (closed-source) projects with your code
* You expect your project to remain small (e.g. less than 300 lines)