From: James Jones <jejones3141@gmail.com>
Date: Wed, 29 Nov 2023 22:54:39 +0000 (-0600)
Subject: Typos
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6e4a7bdfd1c5900f9c8ded39214f1baf58a922bb;p=thirdparty%2Ffreeradius-server.git

Typos
---

diff --git a/doc/antora/modules/developers/pages/dbuff.adoc b/doc/antora/modules/developers/pages/dbuff.adoc
index 58f1951a9c0..c17f9fb6b1b 100644
--- a/doc/antora/modules/developers/pages/dbuff.adoc
+++ b/doc/antora/modules/developers/pages/dbuff.adoc
@@ -45,7 +45,7 @@ the use of the buffer.  The functions normally return the number of
 bytes which have been used, so that the caller can adjust the pointer
 and length (adding to the former and subtracting from the latter).
 
-This method works, but there are some limitations
+This method works, but there are some limitations:
 
 * For encoders the buffer cannot be extended, which means the length
   of the buffer must be determined prior to calling the encoder.
@@ -68,7 +68,7 @@ the `fr_dbuff_t` structure in the source. The structure contains:
   operating on the same buffer are members of a singly linked list.
 
 The Encoding and decoding functions are passed pointers to dbuffs.
-Each function does its' work, updates the pointer to the next byte,
+Each function does its work, updates the pointer to the next byte,
 and then returns.  The caller can then just encode / decode multiple
 tokens in a row, with minimal additional overhead.
 
@@ -170,7 +170,7 @@ FR_DBUFF_FOO_RETURN(dbuff, ...);
 instead of
 [source,c]
 ----
-f ((val = fr_dbuff_foo(dbuff, ...) < 0) return val;
+if ((val = fr_dbuff_foo(dbuff, ...) < 0) return val;
 ----
 
 letting one return an error to the caller without cluttering the code.
diff --git a/doc/antora/modules/developers/pages/sbuff-ng.adoc b/doc/antora/modules/developers/pages/sbuff-ng.adoc
index 979d0be3bdb..ea0726e58d6 100644
--- a/doc/antora/modules/developers/pages/sbuff-ng.adoc
+++ b/doc/antora/modules/developers/pages/sbuff-ng.adoc
@@ -13,7 +13,7 @@
 ## Fixes
 ### Marker release
 
-Current sbuffs require markers to be tracked because the marker's pointer needs to be updated is the sbuff is shifted,
+Current sbuffs require markers to be tracked because the marker's pointer needs to be updated as the sbuff is shifted,
 
 Using offsets relative to the start of the current sbuff removes the tracking requirement and means that the markers no longer need to be updated.