Features
One page per piece of the product: what it solves, who can use it and where it stops. The limits are written down too.
One page per piece
Every module has its own: the problem it solves, who can switch it on given their plan and their profile, and the steps it really takes when you use it. They are written from the code that runs them, not from a competitor's feature list.
They serve two different moments: deciding before you buy, and checking afterwards, when you are already inside and want to know whether something is possible without opening a support chat.
The limits are written down too
Each page says where the piece stops: which formats a network accepts, what cannot be edited once it is published, what needs a permission you may not have. A limit you discover on a Tuesday afternoon costs far more than a limit you read before you paid.