DANE documentation typos

Reported-by: Claus Assmann

Reviewed-by: Rich Salz <rsalz@openssl.org>

doc/ssl/SSL_CTX_dane_enable.pod

diff --git a/doc/ssl/SSL_CTX_dane_enable.pod b/doc/ssl/SSL_CTX_dane_enable.pod
index 66eb1b3..c3c203e 100644
--- a/doc/ssl/SSL_CTX_dane_enable.pod
+++ b/doc/ssl/SSL_CTX_dane_enable.pod
@@ -41,7 +41,7 @@
 any SSL handles are created for the context.
 
 The B<mtype> argument specifies a DANE TLSA matching type and the
-the B<md> argument specifies the associated digest algorithm handle.
+B<md> argument specifies the associated digest algorithm handle.
 The B<ord> argument specifies a strength ordinal.  Algorithms with
 a larger strength ordinal are considered more secure.  Strength
 ordinals are used to implement RFC7671 digest algorithm agility.
@@ -181,7 +181,7 @@
     }
 
     ret = SSL_dane_tlsa_add(ssl, usage, selector, mtype, data, len);
-    /* free data as approriate */
+    /* free data as appropriate */
 
     if (ret < 0)
         /* handle SSL library internal error */

doc/ssl/SSL_set1_host.pod

diff --git a/doc/ssl/SSL_set1_host.pod b/doc/ssl/SSL_set1_host.pod
index b008a5f..0ef2448 100644
--- a/doc/ssl/SSL_set1_host.pod
+++ b/doc/ssl/SSL_set1_host.pod
@@ -35,7 +35,7 @@
 SSL_set1_host() or SSL_add1_host() are retained, no change is made
 if B<name> is NULL or empty.  When multiple names are configured,
 the peer is considered verified when any name matches.  This function
-is required for DANE TLA in the presence of service name indirection
+is required for DANE TLSA in the presence of service name indirection
 via CNAME, MX or SRV records as specified in RFC7671, RFC7672 or
 RFC7673.