Helpful instructions for creating new repo lead to push failure for https users (BB-12650)

I kept having a really annoying problem when I would try to create a new repository from code I was already working on locally (rather than create the empty repo first and clone it). I'd follow your really helpful instructions and have my first push fail.

One of my co-workers figured it out: the instructions assume I'm using SSH not HTTPS:

If I double-clutch and go to the clone instructions, grab the https commandline from there and just edit it locally to be 'remote add origin' rather than 'clone', I'm set up right (for me) and my push works great.

I know that SSH is technically preferable but, frankly, is a pain for Windows users and unlikely to be how they are set up when they first come to BitBucket and create their first repository. The problem didn't drive me away because I am an established, happy user. But if it happens to a new user the first time they try the service, they may just go to GitHub and not come back. Which would be a shame because, while I use both, I think BitBucket is highly preferable for my proprietary repos.