You want to minimize the number of transactions per address.  For one thing, the transaction fee is a function of the number of bytes in a transaction.  So keep it simple.  
This principle applies to funding the cold storage addresses you create in your brain wallet or paper wallet, and even more so to the spending of it -- because you don't want to make a mistake with the change.
For savings (long term cold storage) make as many addresses as you want, but fund each address only once.  And when you spend, the best policy is to spend the entire amount in the address so you avoid problems with change going astray.
Put simply, for each address:  fund once, spend once.

Revisiting this thread just to say I made a small test transaction.  It works as advertised.  The instructions are well written.  Just follow them meticulously, and your transactions should go through.
Just a couple of minor points I would like to mention.  In step 4 of the second section on how to spend, OP states
"Retreive transaction history for your savings address by replacing [YOUR_ADDRESS] in the following URL with your actual public key"
You don't need to paste the public key.  Just the address.  (If it matters to you, the address is a hash of the public key; you never really need to use the public key.)
Step 6 says type in the private key from your paper wallet.  Not to worry, if you make a typo it won't cause a problem.   The keys are generated with checksums, so changing a character or two is supposed result in an invalid key, and the transaction should not execute.  I'm not sure if there is some small possibility of a mistyped key actually turning out to be valid out of sheer chance.  But if it did, you wouldn't lose any coin, you would merely be subject to the inconvenience of redoing the transaction with the correct key.
BEWARE
The real danger is that you might make a mistake with the "change."  Be super-duper careful about the amounts sent to the destination address(es) and sent as fees.  If you don't understand how this works, don't attempt to use raw transactions.

Thanks for the replies.  It's still kind of a mystery to me how and why someone fabricates an address with that special suffix.  Has something to do with the Securities Investor Protection Act.  But what's the story there, and what is bitcoin.sipa.be?
https://blockchain.info/address/14TYdpodQQDKVgvUUcpaMzjJwhQ4KYsipa

A very important question indeed.
And not always just a momentary fright -- some people have actually lost large amounts of bitcoin as a result of not understanding "change" addresses.

Bugs me it's kind of hard to get basic facts about bitcoin.
Example:  I recently saw a mention of "sipa" addresses, which I've never heard of.
This was in a thread explaining how to use Mycelium.
The writer didn't explain sipa addresses.

Developers, and really anybody who writes about bitcoin in the context of explaining it to newcomers and making it more widely available, need to keep in mind:
most people do not come to bitcoin knowing these things

I did quite a bit of searching forums and googling, trying to research sipa, to little avail.
On my own, I ferreted out some basic facts about addresses, to show that I did some work, and make this post more legitimate.  Because I wasn't able to get very far, persons with more knowledge than I are invited to continue the thread by explaining sipa addresses in a way that beginners can understand.

A bitcoin address has 160 bits.
The commonest, uncompressed address format uses base58 and comprises 34 characters, the first of which is always 1, which leaves 33 characters to convey information.  I believe this is "WIF," but correct me if I'm wrong.
Base58 requires 28 characters to hold 160 bits.  This leaves five characters for a checksum, or some sort of error prevention, which is why, in this format, you don't have to worry about a typo resulting in btc going to the wrong address.

A sipa address looks like this
14TYdpodQQDKVgvUUcpaMzjJwhQ4KYsipa
You can paste that into the search box at blockchain.info; it is a valid address.
Like WIF, sipa has 34 characters, and the first character always 1; but the last four characters are always sipa.  This leaves 29 characters to hold 160 bits of information -- only one extra character above the 28 required.
I went to blockchain.info to see what would happen if a sipa address was entered with a typo.  It didn't accept it.

That's as far as I got, trying to find out what sipa means.
Ok guys, start at the beginning, and please keep it simple.

Shut up.

I have searched the btc-e faq and searched this forum.
What steps do I need to take to confirm my email on btc-e?
I responded to the confirmation email but got an error message saying my ip address was wrong.
Edit:  got my email confirmed.  I would have deleted this but you can't delete your own thread.