3.0.0-rc0 inconsistent 'servers' fields

[willdady]

Operation Object has a fixed field called servers which expects a single Server Object as it's value. It's description is a little contradictory.

An alternative server array to service this operation. If an alternative server object is specified at the Path Item Object or Root level, it will be overridden by this value.

Path Item is the same as it also has a fixed field named servers, but is shown as a single object.

Shouldn't both Operation Object and Path Item Object have their servers field denoted as [Server Object]?

Assuming servers are supposed to implicitly inherit from their parent object if not defined I think the descriptions could be made more consistent. Something like:

OpenAPI Object

An optional array of Server Objects which provide connectivity information to a target server.

Path Item Object

An optional array of Server Objects which provide connectivity information to a target server.
If a server array is specified at the OpenAPI Object level, it will be overridden by this value.

Operation Object

An optional array of Server Objects which provide connectivity information to a target server.
If a server array is specified at the Path Item Object or OpenAPI Object level, it will be overridden by this value.

[webron]

Yup, it's just an oversight. Thanks for pointing it out.