diff --git a/challenges/basejumps.json b/challenges/basejumps.json index 71f3f3dcf8..70e07e0788 100644 --- a/challenges/basejumps.json +++ b/challenges/basejumps.json @@ -56,7 +56,7 @@ "Before you publish to Heroku, you should free up as much memory as possible on Cloud9. In each of the Cloud9 terminal prompt tabs where MongoDB and Grunt are running, press the control + c hotkey to shut down these processes.", "Run the following command in a Cloud9 terminal prompt tab: npm install grunt-contrib-imagemin --save-dev && npm install --save-dev && heroku login. At this point, the terminal will prompt you to log in to Heroku from the command line.", "Now run yo angular-fullstack:heroku. You can choose a name for your Heroku project, or Heroku will create a random one for you. You can choose whether you want to deploy to servers the US or the EU.", - "Set the config flag for your Heroku environment and add MongoLab for your MongoDB instance by running the following command: cd ~/workspace/dist && heroku config:set NODE_ENV=production && heroku addons:add mongolab.", + "Set the config flag for your Heroku environment and add MongoLab for your MongoDB instance by running the following command: cd ~/workspace/dist && heroku config:set NODE_ENV=production && heroku addons:create mongolab.", "As you build your app, you should frequently commit changes to your codebase. Make sure you're in the ~/workspace directory by running cd ~/workspace. Then you can this code to stage the changes to your changes and commit them: git commit -am \"your commit message\". Note that you should replace \"your commit message\" with a short summary of the changes you made to your code, such as \"added a records controller and corresponding routes\".", "You can push these new commits to GitHub by running git push origin master, and to Heroku by running grunt --force && grunt buildcontrol:heroku.", "Now you're ready to move on to your first Basejump. Click the \"I've completed this challenge\" and move on." diff --git a/challenges/basic-bonfires.json b/challenges/basic-bonfires.json index 14d5a40437..b2a49c8ce3 100644 --- a/challenges/basic-bonfires.json +++ b/challenges/basic-bonfires.json @@ -13,16 +13,16 @@ "OK, we're finally ready to start pair programming!", "Pair Programming is where two people code together on the same computer. It is an efficient way to collaborate, and widely practiced at software companies. Pair Programming is one of the core concepts of \"Agile\" Software Development, which you will hear more about later.", "Many people use Skype or Google Hangouts to pair program, but if you talk with professional software engineers, they will tell you that it's not really pair programming unless both people have the ability to use the keyboard and mouse.", - "The most popular tool for pair programming is Screen Hero. You can download Screen Hero for Mac or Windows. Create your new user account from within the app.", - "We have a special chat room for people ready to pair program. Go to our LetsPair chatroom on gitter and type \"Hello Pair Programmers!\"", + "The most popular tool for pair programming is Screenhero. You can download Screenhero for Mac or Windows. Create your new user account from within the app.", + "We have a special chat room for people ready to pair program. Go to our LetsPair chatroom on Gitter and type \"Hello Pair Programmers!\"", "If someone is available, they will be your \"pair\" - the person you pair programming with.", "If no one gets back to you in the first few minutes, don't worry. There will be lots of opportunities to pair program in the future.", - "If someone does get back to you, private message them and ask for the email address they used to register Screen Hero.", - "Add them as a new contact in Screen Hero, then click the monitor-looking button to attempt to share your screen with them.", - "Once the Screen Hero session starts, your screen's margins will glow orange. You are now sharing your screen.", + "If someone does get back to you, private message them and ask for the email address they used to register Screenhero.", + "Add them as a new contact in Screenhero, then click the monitor-looking button to attempt to share your screen with them.", + "Once the Screenhero session starts, your screen's margins will glow orange. You are now sharing your screen.", "Your pair will have their own cursor, and will be able to type text on his or her keyboard.", "Now it's time to tackle our Bonfires. You can begin them by advancing to the next challenge.", - "Once you you finish pair programming, end the session in Screen Hero session.", + "Once you you finish pair programming, end the session in Screenhero session.", "Congratulations! You have completed your first pair programming session.", "Pair program as much as possible with different campers until you've completed all the Bonfire challenges. This is a big time investment, but the JavaScript practice you get will be well worth it!", "Mark this Waypoint complete and move on." diff --git a/challenges/basic-html5-and-css.json b/challenges/basic-html5-and-css.json index 61b29ed4d5..2ab346af11 100644 --- a/challenges/basic-html5-and-css.json +++ b/challenges/basic-html5-and-css.json @@ -195,7 +195,7 @@ "assert($('h1').length > 0, 'Make your h1 element visible on your page by uncommenting it.')", "assert($('h2').length > 0, 'Make your h2 element visible on your page by uncommenting it.')", "assert($('p').length > 0, 'Make your p element visible on your page by uncommenting it.')", - "assert(!new RegExp('-->', 'gi').test(editor), 'Be sure to delete the --> that ends the comment.')" + "assert(!new RegExp('-->', 'gi').test(editor), 'Be sure to delete all trailing comment tags, i.e. -->.')" ], "challengeSeed": [ "