moving docs to README

manifests/common.pp

@@ -1,8 +1,5 @@
 # Common configuration for acme_vault
 # 
-# This class needs to be included before acme_vault::request or
-# acme_vault::deploy and contains configurations common to both.  The user,
-# vault, vault vars, and cron mailto are needed for both request and deploy
 
 class acme_vault::common (
     $user               = $::acme_vault::params::user,

manifests/deploy.pp

@@ -1,11 +1,5 @@
 # Configuration for deploying certs in vault to the filesystem
 #
-# This class handles taking a cert/key out of vault, and placing it in a
-# configured path on the filesystem.  It will also accept a restart command to
-# restart any appropriate services to take advantage of the new cert.
-#
-# It employs a script, check_cert.sh, to validate the cert in vault is
-# appropriate to replace the existing one
 
 class acme_vault::deploy(
     $user                  = $::acme_vault::common::user,

manifests/request.pp

@@ -1,12 +1,5 @@
 # Configuration for requesting a cert from letsencrypt, and storing it in vault.
 #
-# This class uses acme.sh, and pulls down the git repo for it.  It uses the
-# lexicon provider in acme.sh to do the dns updating for the dns-01 challenge.
-# It configures a cron job to periodically check if a cert needs renewal.
-# 
-# Note: it does not automatically trigger requesting certs, but relies on cron
-# coordination to eventually reach the desired end state.  Since certificate
-# renewal has a large time window, this is acceptable.
 
 class acme_vault::request (
     $user               = $::acme_vault::common::user,