Repository Vs Repository Pattern in C#

Is there a difference between a repository and repository pattern in C#?
Is this a good description in your opinion on a repository pattern (from another post)?
The repository pattern is a data access pattern that abstracts away your data access code. Using the repository pattern, your ASP.NET (either webforms or mvc) web application can interact with a data source without knowing the specifics of that data source. Meaning, your web app talks to a repository and that repository is in charge or getting or updating data. The web app doesn't know anything about the data access, the repository is in charge of that. The nice thing about the repository pattern is that it makes it easier to unit test your app, easier to maintain your app since all the data access logic is in it's own object, and lastly it makes it easy to change data access later. If you want to switch from a local DB to a cloud based db, it's easy with the repository pattern.