git: f251abcdfe15 - stable/12 - rpc(3): Correct a few common typos in source code comments

[Gordon Bergling]

The branch stable/12 has been updated by gbe (doc committer):

URL: https://cgit.FreeBSD.org/src/commit/?id=f251abcdfe15836186c69a2b279255e077a45277

commit f251abcdfe15836186c69a2b279255e077a45277
Author:     Gordon Bergling <gbe at FreeBSD.org>
AuthorDate: 2021-08-22 06:16:09 +0000
Commit:     Gordon Bergling <gbe at FreeBSD.org>
CommitDate: 2021-08-25 06:27:09 +0000

    rpc(3): Correct a few common typos in source code comments
    
    - s/therfore/therefor/
    - s/activte/active/
    
    Obtained from:  NetBSD
    
    (cherry picked from commit 0d55bc8eb2ab9508c43e135616ca887ed719ea9a)
---
 lib/libc/rpc/clnt_dg.c | 4 ++--
 lib/libc/rpc/clnt_vc.c | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/lib/libc/rpc/clnt_dg.c b/lib/libc/rpc/clnt_dg.c
index a1cd7502e2ad..26bf34633623 100644
--- a/lib/libc/rpc/clnt_dg.c
+++ b/lib/libc/rpc/clnt_dg.c
@@ -92,9 +92,9 @@ static void clnt_dg_destroy(CLIENT *);
  *	This machinery implements per-fd locks for MT-safety.  It is not
  *	sufficient to do per-CLIENT handle locks for MT-safety because a
  *	user may create more than one CLIENT handle with the same fd behind
- *	it.  Therfore, we allocate an array of flags (dg_fd_locks), protected
+ *	it.  Therefore, we allocate an array of flags (dg_fd_locks), protected
  *	by the clnt_fd_lock mutex, and an array (dg_cv) of condition variables
- *	similarly protected.  Dg_fd_lock[fd] == 1 => a call is activte on some
+ *	similarly protected.  Dg_fd_lock[fd] == 1 => a call is active on some
  *	CLIENT handle created for that fd.
  *	The current implementation holds locks across the entire RPC and reply,
  *	including retransmissions.  Yes, this is silly, and as soon as this
diff --git a/lib/libc/rpc/clnt_vc.c b/lib/libc/rpc/clnt_vc.c
index dec1791dcc95..ebd4e303916f 100644
--- a/lib/libc/rpc/clnt_vc.c
+++ b/lib/libc/rpc/clnt_vc.c
@@ -123,9 +123,9 @@ struct ct_data {
  *      This machinery implements per-fd locks for MT-safety.  It is not
  *      sufficient to do per-CLIENT handle locks for MT-safety because a
  *      user may create more than one CLIENT handle with the same fd behind
- *      it.  Therfore, we allocate an array of flags (vc_fd_locks), protected
+ *      it.  Therefore, we allocate an array of flags (vc_fd_locks), protected
  *      by the clnt_fd_lock mutex, and an array (vc_cv) of condition variables
- *      similarly protected.  Vc_fd_lock[fd] == 1 => a call is activte on some
+ *      similarly protected.  Vc_fd_lock[fd] == 1 => a call is active on some
  *      CLIENT handle created for that fd.
  *      The current implementation holds locks across the entire RPC and reply.
  *      Yes, this is silly, and as soon as this code is proven to work, this