Glossary

Branch
A branch is an offshoot of mainline development typically used to isolate long running changes or manage multiple versions or releases of an application codeline.
Changeset
Some SCM systems have a very explicit notion of 'change sets'. In SVN, a revision (or, typically, a range of revisions) is a change set, since it represents changes from one branch of development that may be applied to (merged with) other branches of development.
Head
The head revision, or latest version, of a resource.
Pristine copy
SVN stores a pristine copy of the base revision (i.e., the unmodified checked-out revision) of each file in the working copy. These pristine copies are known as "text bases" and are used for performing offline diffs, and for transmitting deltas back to the server when committing.
Repository
In this context, the SVN version-controlled container for all of your project resources.
'svn' command line
The "reference" implementation of the SVN client is the command line
Tag
A tag is a snapshot of an application codeline at a specific point in time and are typically used to label a specific revision of the repository code.
Trunk
The trunk of a development is the project folder where the mainline development takes place. It is a naming convention only; no feature or function is implicit in this term.
Unified Diff
A standard representation for the differences between two files where removed lines are prefaced with a - and added lines are prefaced with a +.
Working copy
A local, version controlled copy of a repository's files and directories.