package wrongly documented and used with content parameter

There are some references to the old `content` parameter (from
preseeded_package) that mistakenly weren't replaced with the new
parameter `seedfile_content`. This meant the documentation was wrong and
the `preseeded_package` wrapper was erroring out because of an unknown
parameter.

2 files changed, 6 insertions, 6 deletions

diff --git a/README.md b/README.md
index aac4a8e..944044b 100644
--- a/README.md
+++ b/README.md
@@ -527,12 +527,12 @@ following in your manifest:
 You can change what template is used by setting `seedfile_template` to a
 template path (same as you would pass to the template() function).
 
-You can also specify the content of the seed via the content parameter instead
-of using a template, for example:
+You can also specify the content of the seed via the `seedfile_content`
+parameter instead of using a template, for example:
 
     apt::package { 'apticron':
       use_seed => true,
-      content  => 'apticron apticron/notification string root@example.com',
+      seedfile_content  => 'apticron apticron/notification string root@example.com',
     }
 
 To pin a package to a certain release or version, you need to set the `pin`
diff --git a/manifests/preseeded_package.pp b/manifests/preseeded_package.pp
index 7db740f..e6fcab1 100644
--- a/manifests/preseeded_package.pp
+++ b/manifests/preseeded_package.pp
@@ -5,8 +5,8 @@ define apt::preseeded_package (
 ) {
   warning('apt::preseeded_package is deprecated! you should now use apt::package with parameter use_seed set to true instead.')
   apt::package { $name:
-    ensure   => $ensure,
-    use_seed => true,
-    content  => $content,
+    ensure           => $ensure,
+    use_seed         => true,
+    seedfile_content => $content,
   }
 }