We ignore app name anyway, so remove it.

features/kumade_executable.feature

@@ -11,8 +11,8 @@ Feature: Kumade executable
     And I add "jammit" to the Gemfile
     And I bundle
     When I set up a git repo
-    And I create a Heroku remote for "pretend-staging-app" named "pretend-staging"
-    And I create a Heroku remote for "app-two" named "staging"
+    And I create a Heroku remote named "pretend-staging"
+    And I create a Heroku remote named "staging"
     And I create a non-Heroku remote named "bad-remote"
 
   Scenario: Pretend mode with a Heroku remote

features/kumade_without_jammit.feature

@@ -7,7 +7,7 @@ Feature: Kumade without jammit
     And I set up the Gemfile with kumade
     And I bundle
     When I set up a git repo
-    And I create a Heroku remote for "pretend-staging-app" named "pretend-staging"
+    And I create a Heroku remote named "pretend-staging"
 
   Scenario: Jammit packager does not run if Jammit is not installed
     When I run kumade with "pretend-staging"

features/railtie.feature

@@ -7,7 +7,7 @@ Feature: Railtie
   Scenario: Rake tasks are loaded
     Given a new Rails application with Kumade
     When I require the kumade railtie in the Rakefile
-    And I create a Heroku remote for "my-app" named "staging"
+    And I create a Heroku remote named "staging"
     And I create a non-Heroku remote named "bad-remote"
     And I run `bundle exec rake -T`
     Then the output should match /deploy:staging.+Deploy to staging environment/

features/step_definitions/git_steps.rb

@@ -1,4 +1,4 @@
-When /^I create a Heroku remote for "([^"]*)" named "([^"]*)"$/ do |app_name, remote_name|
+When /^I create a Heroku remote named "([^"]*)"$/ do |remote_name|
   add_heroku_remote_named(remote_name)
 end