texlive[45769] Master/texmf-dist/scripts/texlive/tlmgr.pl: doc

[commits+karl at tug.org]

Revision: 45769
          http://tug.org/svn/texlive?view=revision&revision=45769
Author:   karl
Date:     2017-11-13 02:10:48 +0100 (Mon, 13 Nov 2017)
Log Message:
-----------
doc

Modified Paths:
--------------
    trunk/Master/texmf-dist/scripts/texlive/tlmgr.pl

Modified: trunk/Master/texmf-dist/scripts/texlive/tlmgr.pl
===================================================================
--- trunk/Master/texmf-dist/scripts/texlive/tlmgr.pl	2017-11-12 23:30:50 UTC (rev 45768)
+++ trunk/Master/texmf-dist/scripts/texlive/tlmgr.pl	2017-11-13 01:10:48 UTC (rev 45769)
@@ -7702,7 +7702,7 @@
 If the option C<--data> is given, its argument must be a comma separated
 list of field names from: C<name>, C<category>, C<localrev>, C<remoterev>,
 C<shortdesc>, C<longdesc>, C<installed>, C<size>, C<relocatable>, C<depends>,
-C<cat-version>, C<cat-date>, or C<cat-licence>. In this case the requested
+C<cat-version>, C<cat-date>, or C<cat-license>. In this case the requested
 packages' information is listed in CSV format one package per line, and the
 column information is given by the C<itemN>. The C<depends> column contains
 the name of all dependencies separated by C<:>.
@@ -8601,19 +8601,19 @@
 C<(not verified)>.  Either way, by default the installation and/or
 updates proceed normally.
 
-If a program C<gpg> is available (that is, it is found in the C<PATH>),
-cryptographic signatures will be checked. In this case we require that
-the main repository is signed. This is not required for additional r
-repositories. If C<gpg> is not available, signatures are not checked
-and no verification is carried out, but C<tlmgr> proceeds normally.
-This is the behavior of C<tlmgr> up to TeX Live 2016.
+If a program named C<gpg> is available (that is, it is found in the
+C<PATH>), cryptographic signatures will be checked. In this case we
+require that the main repository is signed, but signing is not required
+for additional repositories. If C<gpg> is not available, signatures are
+not checked and no verification is carried out, but C<tlmgr> proceeds
+normally.
 
 The attempted verification can be suppressed by specifying
 C<--no-verify-downloads> on the command line, or the entry
-C<verify-downloads = 0> in a C<tlmgr> config file (described in
-L<CONFIGURATION FILE FOR TLMGR>).  On the other hand, it is possible to
+C<verify-downloads=0> in a C<tlmgr> config file (described in
+L<CONFIGURATION FILE FOR TLMGR>).  On the other hand, you can
 I<require> verification by specifying C<--require-verification> on the
-command line, or C<require-verification = 1> in a C<tlmgr> config file;
+command line, or C<require-verification=1> in a C<tlmgr> config file;
 in this case, if verification is not possible, the program quits.
 Note that as mentioned above, if C<gpg> is available, the main repository
 is always required to have a signature. Using the C<--require-verification>