doc: Minor updates

--

Author: dd9jn

doc/DETAILS

@@ -279,10 +279,21 @@ described here.
     latter solves the cases where a key is updated by fingerprint and
     and thus there is no way to know which user ID shall be used.
 
+    The meaning of the integer along with the human readable
+    representation is:
+
+    - 1 (ks)      :: Public keyserver.
+    - 2 (ks-pref) :: Preferred keysrver.
+    - 3 (dane)    :: OpenPGP DANE.
+    - 4 (wkd)     :: Web Key Directory.
+    - 5 (url)     :: Trusted URL.
+    - 6 (file)    :: Trusted file.
+    - 7 (self)    :: Generated by us.
+
 *** Field 21 - Comment
 
     This is currently only used in "rev" and "rvs" records to carry
-    the the comment field of the recocation reason.  The value is
+    the the comment field of the revocation reason.  The value is
     quoted in C style.
 
 ** Special fields

g10/encrypt.c

@@ -1121,7 +1121,7 @@ reencrypt_to_new_recipients (ctrl_t ctrl, int armor, const char *filename,
   if (err)
     goto leave;
 
-  /* The write the old recipients in --add-recipients mode.  */
+  /* Write the old recipients in --add-recipients mode.  */
   for (count=0, el = pkenc_list; el; el = el->next, count++)
     if (!ctrl->clear_recipients)
       {

g10/import.c

@@ -1816,7 +1816,7 @@ insert_key_origin_uid (PKT_user_id *uid, u32 curtime,
       /* We insert origin information on a UID only when we received
        * them via the Web Key Directory or a DANE record.  The key we
        * receive here from the WKD has been filtered to contain only
-       * the user ID as looked up in the WKD.  For a DANE origin we
+       * the user ID as looked up in the WKD.  For a DANE origin
        * this should also be the case.  Thus we will see here only one
        * user id.  */
       uid->keyorg = origin;