Misleading / incomplete definition of a soft fork

[NORICVM]

In Soft Forks vs. Hard Forks, we say the following about soft forks:

They only tighten or add rules to the existing protocol

This misleads the reader to think that a soft fork can not have inflationary (relaxing) effect on the protocol, which it can (e.g. segwit).

I propose adopting a more complete definition of a soft fork along these lines:

Changes to the protocol introduced by a soft fork are designed to prevent old nodes from being able to detect them. Once miners adopt a new soft fork, it is accepted by validating nodes by default. Rejection requires organized mobilization by validation node operators.