The manual module is a work in progress. Contributors commit changes to it on a regular basis. Some time after your initial checkout, your local copy will be out of sync with the repository at SourceForge. Of course it would be a waste of bandwidth if you had to check out the entire module time and again, only to update those few files that have changed. Moreover, doing so would overwrite any changes you may have made yourself. That's why CVS has an update command. With update, only the changes are downloaded from the server, and your own local changes are preserved. (In the event that another contributor has changed a file in the same spot as you, a conflict is signaled and you must edit the file in question to solve it.)

Updating is dead easy. If you use command line CVS, go to the manual directory and type:

This command is the same whether you checked out anonymously or with your SF login and password. CVS knows which server to contact and how to authenticate you because this information is saved in the manual/CVS subdirectory, which was created automatically when you first checked out the module. The only difference is that if you checked out with login and pass, you will also be prompted for your password when you run update.

If you use another CVS tool, look for its update command or menu option.