--1 if an error occurred.
-.LP
-The ber_get_next() routine is used to read the next BER element from
-the given Sockbuf, \fIsb\fP. A Sockbuf consists of the descriptor
-(usually socket, but a file descriptor works just as well) from which
-to read, and a BerElement structure used
-to maintain a buffer. On the first call, the \fIsb_ber\fP struct should
-be zeroed. It strips off and returns the
-leading tag byte, strips off and returns the length of the
-entire element in \fIlen\fP,
-and sets up \fIber\fP for subsequent calls to ber_scanf() et al to decode
-the element.
-.LP
-The ber_scanf() routine is used to decode a BER element in much the
-same way that scanf(3) works. It reads from \fIber\fP, a pointer to a
-BerElement such as returned by ber_get_next(), interprets the
-bytes according to the format string \fIfmt\fP, and stores the
+LBER_ERROR if an error occurred.
+.LP
+The
+.BR ber_get_next ()
+routine is used to read the next BER element from the given Sockbuf,
+\fIsb\fP. It strips off and returns the leading tag, strips off and
+returns the length of the entire element in \fIlen\fP, and sets up
+\fIber\fP for subsequent calls to
+.BR ber_scanf ()
+et al to decode the element. See
+.BR lber-sockbuf (3)
+for details of the Sockbuf implementation of the \fIsb\fP parameter.
+.LP
+The
+.BR ber_scanf ()
+routine is used to decode a BER element in much the same way that
+.BR scanf (3)
+works. It reads from \fIber\fP, a pointer to a BerElement
+such as returned by
+.BR ber_get_next (),
+interprets the bytes according to the format string \fIfmt\fP, and stores the