Tweak walkthrough to make clear you need to commit and push the initial step of adding config file

Author: ndintenfass

jekyll/_cci2/project-walkthrough.md

@@ -35,7 +35,7 @@ Finally, we'll deploy the application to Heroku and discuss other deployment opt
 
 ## Upload Your Code
 
-To use CircleCI, your code must be available on GitHub or BitBucket, in either a private or public repository. We'll be using GitHub for this walkthrough.
+To use CircleCI, your code must be available on GitHub or BitBucket, in either a private or public repository. We'll be assuming GitHub for this walkthrough, but the same flow applies to BitBucket as well.
 
 <div class="alert alert-info" role="alert">
 <strong>Tip:</strong> If you're following along and want to use the code, you should fork and clone the <a class="alert-link" href="https://github.com/circleci/cci-demo-walkthrough">cci-demo-walkthrough</a> project. On your local machine, delete the <code>.circleci</code> directory and make a commit. You now have a clean project ready to start configuring for use with CircleCI.
@@ -56,6 +56,8 @@ version: 2
 
 This tells CircleCI to use CircleCI 2.0. Without this, CircleCI will try to build the project on CircleCI 1.0.
 
+Commit and push your changes to get your new `.circleci` folder and the `config.yml` file into GitHub.
+
 ## Add Project and Start Building
 
 Log into CircleCI ([create an account](https://circleci.com/signup/) if you haven't already) and go to the '[Add Projects](https://circleci.com/add-projects)' screen. Locate your project and click the green 'Build Project' button.