The branch main has been updated by gbe (doc committer): URL: https://cgit.FreeBSD.org/src/commit/?id=d07a5018766e11d7f9d7f0c1aa5e0a9baa5ca6d6
commit d07a5018766e11d7f9d7f0c1aa5e0a9baa5ca6d6 Author: Gordon Bergling <[email protected]> AuthorDate: 2022-09-04 10:47:49 +0000 Commit: Gordon Bergling <[email protected]> CommitDate: 2022-09-04 10:47:49 +0000 tcp_hpts: Correct some typos in source code comments - s/occured/occurred/ - s/the the/the/ MFC after: 3 days --- sys/netinet/tcp_hpts.c | 4 ++-- sys/netinet/tcp_hpts.h | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sys/netinet/tcp_hpts.c b/sys/netinet/tcp_hpts.c index b8d09523113f..828ce16e8dad 100644 --- a/sys/netinet/tcp_hpts.c +++ b/sys/netinet/tcp_hpts.c @@ -1341,7 +1341,7 @@ again: * goes off and sees the mis-match. We * simply correct it here and the CPU will * switch to the new hpts nextime the tcb - * gets added to the the hpts (not this one) + * gets added to the hpts (not this one) * :-) */ tcp_set_hpts(inp); @@ -1376,7 +1376,7 @@ again: * than the previous inp) and there no * assurance that ninp was not pulled while * we were processing inp and freed. If this - * occured it could mean that either: + * occurred it could mean that either: * * a) Its NULL (which is fine we won't go * here) <or> b) Its valid (which is cool we diff --git a/sys/netinet/tcp_hpts.h b/sys/netinet/tcp_hpts.h index c1af23e2d4df..ebee6a01b983 100644 --- a/sys/netinet/tcp_hpts.h +++ b/sys/netinet/tcp_hpts.h @@ -129,7 +129,7 @@ bool tcp_in_hpts(struct inpcb *); * it to be 1 (so you wont call output) it may be transitioning * to 0 (by the hpts). That will be fine since that will just * mean an extra call to tcp_output that most likely will find - * the call you executed (when the mis-match occured) will have + * the call you executed (when the mis-match occurred) will have * put the TCB back on the hpts and it will return. If your * call did not add it back to the hpts then you will either * over-send or the cwnd will block you from sending more.
