Headline "Requirements" aren't requirements, but features

[bbugh]

I was confused reading the docs where the subheadline of feature pages say "Requirements" but the list under it is a list of use cases, not requirements. Since Feature is already a class name in the tool (and so is Requirements for that matter), what about changing this headline to "Purpose" or "Benefits", "Advantages", "Properties", "Traits", etc. or something like that?

Example:

[Ishadijcks]

You make a good point. The term Requirements has the following rationale.

"I'm going to design a new Feature, it has to fulfill these requirements for it to be useful."

But I can see how it is a bit confusing when you switch from the designer to the user perspective.

What do you think about the term Functionalities?