diff options
| author | Tom Ryder <tom@sanctum.geek.nz> | 2017-10-14 02:12:49 +1300 |
|---|---|---|
| committer | Tom Ryder <tom@sanctum.geek.nz> | 2017-10-14 02:12:49 +1300 |
| commit | 3cfb392aca451dc604444d87b72fa48fd7ad823a (patch) | |
| tree | b38b3ab9795a3e0073c3d3210a14b1698558f5ff /lib | |
| parent | Mention that signing is optional (diff) | |
| download | Mail-Run-Crypt-3cfb392aca451dc604444d87b72fa48fd7ad823a.tar.gz Mail-Run-Crypt-3cfb392aca451dc604444d87b72fa48fd7ad823a.zip | |
Add a missing word to docs
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/Mail/Run/Crypt.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Mail/Run/Crypt.pm b/lib/Mail/Run/Crypt.pm index d1d56e0..4075bf7 100644 --- a/lib/Mail/Run/Crypt.pm +++ b/lib/Mail/Run/Crypt.pm @@ -146,8 +146,8 @@ address. The idea is to allow you to view the output of automated commands while having the content encrypted as it passes through to your mailserver, and (optionally) have some assurance that the content was actually generated by the server -concerned. C<cron(8)> scripts are the ideal use case, but this would also with -C<at(1)> or anything else that might non-interactively run jobs for which +concerned. C<cron(8)> scripts are the ideal use case, but this would also work +with C<at(1)> or anything else that might non-interactively run jobs for which output is significant. You probably want to call this with the C<runcrypt(1)> program installed by |