Fix some comments referencing sockets which are not used by the ber api. The

api uses read and write buffers (byte streams) that are utilized by calling
applications which may or may not use sockets.

ok claudio@

buffer byte streams that applications then use for

1 files changed, 5 insertions, 5 deletions

diff --git a/usr.bin/ldap/ber.c b/usr.bin/ldap/ber.c
index 47f0880407a..54c31212106 100644
--- a/usr.bin/ldap/ber.c
+++ b/usr.bin/ldap/ber.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: ber.c,v 1.13 2018/07/13 08:30:10 rob Exp $ */
+/*	$OpenBSD: ber.c,v 1.14 2018/07/13 08:50:38 rob Exp $ */
 
 /*
  * Copyright (c) 2007, 2012 Reyk Floeter <reyk@openbsd.org>
@@ -757,10 +757,10 @@ ber_scanf_elements(struct ber_element *ber, char *fmt, ...)
 }
 
 /*
- * write ber elements to the socket
+ * write ber elements to the write buffer
  *
  * params:
- *	ber	holds the socket
+ *	ber	holds the destination write buffer byte stream
  *	root	fully populated element tree
  *
  * returns:
@@ -796,10 +796,10 @@ ber_write_elements(struct ber *ber, struct ber_element *root)
 }
 
 /*
- * read ber elements from the socket
+ * read ber elements from the read buffer
  *
  * params:
- *	ber	holds the socket and lot more
+ *	ber	holds a fully populated read buffer byte stream
  *	root	if NULL, build up an element tree from what we receive on
  *		the wire. If not null, use the specified encoding for the
  *		elements received.