features/commands/update.feature in berkshelf-3.0.0.beta4 vs features/commands/update.feature in berkshelf-3.0.0.beta5

@@ -6,11 +6,10 @@
       | fake | 0.2.0 |
       | fake | 1.0.0 |
       | ekaf | 1.0.0 |
       | ekaf | 1.0.1 |
 
-
   Scenario: Without a cookbook specified
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'fake', '~> 0.1'
       cookbook 'ekaf', '~> 1.0.0'
@@ -21,11 +20,10 @@
     When I successfully run `berks update`
     Then the Lockfile should have:
       | fake | 0.2.0 |
       | ekaf | 1.0.1 |
 
-
   Scenario: With a single cookbook specified
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'fake', '~> 0.1'
       cookbook 'ekaf', '~> 1.0.0'
@@ -35,10 +33,9 @@
       | ekaf | 1.0.0 |
     When I successfully run `berks update fake`
     Then the Lockfile should have:
       | fake | 0.2.0 |
       | ekaf | 1.0.0 |
-
 
   Scenario: With a cookbook that does not exist
     Given I have a Berksfile pointing at the local Berkshelf API
     When I run `berks update not_real`
     Then the output should contain: