[git] gnupg-doc - branch, master, updated. ac719e3219e70a6f1817837536007e21c721fae9

by Neal H. Walfield cvs at cvs.gnupg.org
Sun Sep 13 20:10:53 CEST 2015

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GnuPG website and other docs".

The branch, master has been updated
       via  ac719e3219e70a6f1817837536007e21c721fae9 (commit)
      from  283853c25ac6995b72810e8bfc31cf5f59d3349e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ac719e3219e70a6f1817837536007e21c721fae9
Author: Neal H. Walfield <neal at gnu.org>
Date:   Sun Sep 13 20:10:48 2015 +0200

    blog: Fix a few working errors in "News for the Summer"

diff --git a/misc/blog.gnupg.org/20150911-gnupg-this-summer.org b/misc/blog.gnupg.org/20150911-gnupg-this-summer.org
index fd85856..3245b3b 100644
--- a/misc/blog.gnupg.org/20150911-gnupg-this-summer.org
+++ b/misc/blog.gnupg.org/20150911-gnupg-this-summer.org
@@ -28,7 +28,7 @@ about current activities both within GnuPG (some new features and the
 recent fund raising campaign) as well as some activities related to
 GnuPG (in particular, the rechartering of the OpenPGP working group).
 Finally, he discussed his vision for the future.  In particular, he
-wants GnuPG be easier to use for the masses.  This means, for
+wants GnuPG to be easier to use for the masses.  This means, for
 instance, using TOFU as a trust model instead of the web of trust,
 which requires [[http://wiki.gnupg.org/WebOfTrust][too much curating]] for nearly all users---including most
 technical users---to be effective.  Nevertheless, the goal isn't to
@@ -38,7 +38,7 @@ configuration options.  The primary focus, however, is making
 GnuPG easier to use and more secure for casual use by default.
 Also at DebConf, dkg presented "[[https://summit.debconf.org/debconf15/meeting/195/gnupg-in-debian-report/][GnuPG in Debian Report]]" on behalf of
-the GnuPG packing team ([[https://dkg.fifthhorseman.net/gnupg-in-debian-debconf15.pdf][slides]]).  He reported the status of GnuPG in
+the GnuPG packaging team ([[https://dkg.fifthhorseman.net/gnupg-in-debian-debconf15.pdf][slides]]).  He reported the status of GnuPG in
 Debian and what the team has planned.  He began by relating the
 current status of GnuPG in Debian.  First, everything has been moved
 over to git.  The packaging team has also adopted not only GnuPG, but
@@ -158,7 +158,7 @@ cards]].  Niibe and Werner argued that only a single application should
 use the smartcard at a time.  There are two main arguments:
 performance and security.  From a performance perspective, GnuPG (or
 rather, scadaemon) can cache the status of the card.  Having to
-refresh information (among initialization procedures) can introduce a
+refresh information (and rerun the initialization procedure) can introduce a
 several second delay.  From a security perspective, we want to make
 sure that another application does not get access to the card without
 having to enter the PIN.
@@ -190,7 +190,7 @@ is available to those most engaged in OpenPGP.
 Robert J. Hansen has begun [[https://lists.gnupg.org/pipermail/gnupg-users/2015-August/054172.html][overhauling the FAQ]].  He is planning on
 removing references to GnuPG 1.4 as much as possible.  He also
-feedback about some proposed clarifications.
+sought feedback about some proposed clarifications.
 ** About this news posting


Summary of changes:
 misc/blog.gnupg.org/20150911-gnupg-this-summer.org | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

The GnuPG website and other docs

More information about the Gnupg-commits mailing list