use the same style for all the examples

README.md

@@ -49,10 +49,6 @@ Ubuntu support is lagging behind but not absent either.
 
 ## Upgrade Notice<a name="upgrade-notice"></a>
 
- * The default value of the `$repos` parameter was removed since the logic is
-   now in the `apt::params` class. If you have explicitly set `$repos` to
-   'auto' in your manifests, you should remove this.
-
  * The `disable_update` parameter has been removed. The main apt class
    defaults to *not* run an `apt-get update` on every run anyway so this
    parameter seems useless.
@@ -83,10 +79,9 @@ Ubuntu support is lagging behind but not absent either.
    you will need to remove the variables, and the include and instead do
    the following:
 
-    class {
+    class { 'apt':
-      'apt':
+      debian_url       => 'http://localhost:9999/debian/',
-        debian_url       => 'http://localhost:9999/debian/',
+      use_next_release => true;
-        use_next_release => true;
     }
 
    previously, you could manually set `$lsbdistcodename` which would enable forced
@@ -98,10 +93,9 @@ Ubuntu support is lagging behind but not absent either.
    you to trigger upgrades:
 
     include apt::dist_upgrade
-    class {
+    class { 'apt':
-      'apt':
+      codename => 'wheezy',
-        codename => 'wheezy',
+      notify   => Exec['apt_dist-upgrade'];
-        notify   => Exec['apt_dist-upgrade'];
     }
 
  * the `apticron` class has been moved to a parameterized class.  if you were
@@ -116,8 +110,7 @@ Ubuntu support is lagging behind but not absent either.
    you will need to remove the variables, and the include and instead do the
    following:
 
-    class {
+    class { 'apt::apticron':
-    'apt::apticron':
       email     => 'foo@example.com',
       notifynew => '1';
     }
@@ -134,9 +127,8 @@ Ubuntu support is lagging behind but not absent either.
    you will need to remove the variables, and the include and instead do the
    following:
  
-    class {
+    class { 'apt::listchanges':
-      'apt::listchanges':
+      email => 'foo@example.com';
-        email => 'foo@example.com';
     }
    
  * the `apt::proxy_client` class has been moved to a paramterized class. if you
@@ -151,10 +143,9 @@ Ubuntu support is lagging behind but not absent either.
    you will need to remove the variables, and the include and instead do the
    following:
 
-    class {
+    class { 'apt::proxy_client':
-      'apt::proxy_client':
+      proxy => 'http://proxy.domain',
-        proxy => 'http://proxy.domain',
+      port  => '666';
-        port  => '666';
     }
 
 
@@ -644,33 +635,11 @@ To run pupept rspec tests:
     bundle install --path vendor/bundle
     bundle exec rake spec
 
-Verbose Output:
-
-    bundle exec rake spec SPEC_OPTS='--format documentation'
-
 Using different facter/puppet versions:
 
     FACTER_GEM_VERSION=1.6.10 PUPPET_GEM_VERSION=2.7.23 bundle install --path vendor/bundle
     bundle exec rake spec
 
-## Acceptance Tests<a name="acceptance-tests"></a>
-
-At the moment, we use [beaker together with docker](https://github.com/puppetlabs/beaker/blob/master/docs/Docker-Support.md)
-to do acceptance testing.
-Be sure to have a recent docker version installed.
-
-List configured nodesets:
-
-    bundle exec rake beaker_nodes
-
-Run tests on default node (Debian Jessie):
-
-    bundle exec rake beaker
-
-Run different nodeset:
-
-    BEAKER_set="debian-8-x86_64-docker" bundle exec rspec spec/acceptance/*_spec.rb
-
 
 # Licensing<a name="licensing"></a>
 
@@ -681,3 +650,4 @@ The GPL version 3 license text can be found in the "LICENSE" file accompanying
 this puppet module, or at the following URL:
 
 http://www.gnu.org/licenses/gpl-3.0.html
+