https://en.wikipedia.org/wiki/Open_source#%22Open%22_versus_...
In my view using the proper vs common version of "open source" places this into a disingenuous attempt to be associated with open source as defined by the OSI.
It is also goes against the site comment's guideline (as well as general sane rule) of: Assume good faith.
I saw "Open Source" and assumed, as I suspect many people did, that it was talking about the Open Source Initiative definition of Open Source. Intended or not, those two words carry a connotation for a lot of people. I'd rather not see that connotation watered-down, either.
Anyway, it's stupid to argue over this. The FAQ on the Commons Clause site itself, reflecting the intention and thinking of the drafter and the initiatiors, specifically states the license is "source-available", not "open source". When talking about open source as a form of licensing as opposed to e.g. software development culture/methodology, the distinction here is quite widely accepted and non-contentious.
For instance, at a previous company we were forbidden to use React until Facebook changed over to the MIT license. Facebook had a poison pill buried into their original "open source" license.
OTOH, this is likely to never make it into distro repos anywhere. I also wonder if the author is driving to make a business out of it.
So I'd make three points:
1) It does affect distribution
2) It otherwise doesn't materially affect how I would use it
3) It seems a little like asking for contributions to a proprietary project.
Many enterprises prefer a paid service, as such contracts usually come with somebody assuming liability for data on the system and being around to resolve problems you'd otherwise need to distract an in-house team with.