Writing User Stories

I've been doing some reading about Agile Software development and how to implement scrum for a small development team. Mike Cohn is definitely an authority on Agile and scrum and I was catching up on some of his articles and I found this one that explains the benefit of capturing requirements in terms of user stories.
To clarify, user stories are little statements that define the value to a stakeholder that is to be realized in a system. These stories should not make references to technology or interfaces unless absolutely necessary. A user story just describes something that a user has to be able to do.

Advantages of the "As a user, I want" user story template Mike Cohn's Blog - Succeeding With Agile®: "In my user stories book and in all my training and conference sessions on user stories I advocate writing user stories in the form of “As a , I want so that .” While I consider the so-that clause optional, I really like this template"

I've spent a little time re-wording some of our 'enhancement' requests and requirements lists to follow this wording which I've found really helpful in clarifying what the software should do.