My apologies. In retrospect, what I wrote sounds harsher than I would have liked. I should have instead explained what was involved rather than bite. Call it a bad day, I'm not usually like this:-)
To make amends, I'll attempt to give an overview of what SVN is:
SVN is a what is known as a version control or source control management (SCM) tool. It's a way to maintain and track changes in source code. The concept is simillar to a library in that you have to check code in and out. You check in changes to what is stored in the code base (the repository) and the SCM maintains a log of these changes.
This means you can, for example, see what has changed, get the latest version of the code or even a specific version, and always have something to go back to if something goes wrong.
The first thing you need to do when using SVN is a checkout.When you do a SVN checkout, it gets out the latest version of the code.
Now that you have a fresh checkout, you can do a SVN update.
When you do a SVN update, what it does is updates the code that you have checked out to what is in the repository. If the code in the repository has changed, you get the latest version.
There's a lot more to it but I hope that gives you a head start in understanding SVN.