In a software delivery world where 'my' implementation of Agile differs from 'your' implementation of Agile, we often find ourselves sharing terminology without thinking about it. We might even borrow our favorite Agile terms and reinvent them in our non-Agile methodologies (I'm not going to say Waterfall because ... damn, I fell into my own pitfall).
The point is this - borrow what you need, use what works but don't forget to be faithful to the original. This is a great, clear description of a User Story and should be read even by those who consider themselves on the periphery of delivery.
Each user story is expected to yield, once implemented, a contribution to the value of the overall product