10067 Miscellaneous man page typos
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: Andy Fiddaman <andy@omniosce.org>
Reviewed by: Volker A. Brandt <vab@bb-c.de>

*** 57,67 ****
  
  \fBint\fR \fBt_sndudata\fR(\fBint\fR \fIfd\fR, \fBconst struct t_unitdata *\fR\fIunitdata\fR);
  .fi
  
  .SH DESCRIPTION
- .sp
  .LP
  This routine is part of the \fBXTI\fR interfaces which evolved from the
  \fBTLI\fR interfaces. \fBXTI\fR represents the future evolution of these
  interfaces. However, \fBTLI\fR interfaces are supported for compatibility. When
  using a \fBTLI\fR routine that has the same name as an \fBXTI\fR routine, the
--- 57,66 ----
*** 115,142 ****
  activated its transport endpoint (see \fBt_bind\fR(3NSL)), the data unit may be
  discarded.
  .sp
  .LP
  If it is not possible for the transport provider to immediately detect the
! conditions that cause the errors \fBTBADDADDR\fR and \fBTBADOPT\fR, these
  errors will alternatively be returned by \fIt_rcvuderr.\fR Therefore, an
  application must be prepared to receive these errors in both of these ways.
  .sp
  .LP
  If the call is interrupted, \fBt_sndudata()\fR will return \fBEINTR\fR and the
  datagram will not be sent.
  .SH RETURN VALUES
- .sp
  .LP
  Upon successful completion, a value of  \fB0\fR is returned.  Otherwise, a
  value of  -1 is returned and \fBt_errno\fR is set to indicate an error.
  .SH VALID STATES
- .sp
  .LP
  \fBT_IDLE\fR.
  .SH ERRORS
- .sp
  .LP
  On failure, \fBt_errno\fR is set to one of the following:
  .sp
  .ne 2
  .na
--- 114,138 ----
  activated its transport endpoint (see \fBt_bind\fR(3NSL)), the data unit may be
  discarded.
  .sp
  .LP
  If it is not possible for the transport provider to immediately detect the
! conditions that cause the errors \fBTBADADDR\fR and \fBTBADOPT\fR, these
  errors will alternatively be returned by \fIt_rcvuderr.\fR Therefore, an
  application must be prepared to receive these errors in both of these ways.
  .sp
  .LP
  If the call is interrupted, \fBt_sndudata()\fR will return \fBEINTR\fR and the
  datagram will not be sent.
  .SH RETURN VALUES
  .LP
  Upon successful completion, a value of  \fB0\fR is returned.  Otherwise, a
  value of  -1 is returned and \fBt_errno\fR is set to indicate an error.
  .SH VALID STATES
  .LP
  \fBT_IDLE\fR.
  .SH ERRORS
  .LP
  On failure, \fBt_errno\fR is set to one of the following:
  .sp
  .ne 2
  .na
*** 234,259 ****
  .RS 15n
  A system error has occurred during execution of this function.
  .RE
  
  .SH TLI COMPATIBILITY
- .sp
  .LP
  The \fBXTI\fR and \fBTLI\fR interface definitions have common names but use
  different header files. This, and other semantic differences between the two
  interfaces are described in the subsections below.
  .SS "Interface Header"
- .sp
  .LP
  The \fBXTI\fR interfaces use the header file, \fBxti.h.\fR \fBTLI\fR interfaces
  should \fInot\fR use this header.  They should use the header:
  .br
  .in +2
  #include <tiuser.h>
  .in -2
  .SS "Error Description Values"
- .sp
  .LP
  The \fBt_errno\fR values that can be set by the \fBXTI\fR interface and cannot
  be set by the \fBTLI\fR interface are:
  .br
  .in +2
--- 230,252 ----
*** 274,295 ****
  .br
  .in +2
  \fBTOUTSTATE\fR
  .in -2
  .SS "Notes"
- .sp
  .LP
  Whenever this function fails with \fBt_error\fR set to \fBTFLOW,\fR
  \fBO_NONBLOCK\fR must have been set.
  .SS "Option Buffers"
- .sp
  .LP
  The format of the options in an \fBopt\fR buffer is dictated by the transport
  provider. Unlike the \fBXTI\fR interface, the \fBTLI\fR interface does not fix
  the buffer format.
  .SH ATTRIBUTES
- .sp
  .LP
  See \fBattributes\fR(5)  for descriptions of the following attributes:
  .sp
  
  .sp
--- 267,285 ----
*** 301,310 ****
  _
  MT Level        Safe
  .TE
  
  .SH SEE ALSO
- .sp
  .LP
  \fBfcntl\fR(2), \fBt_alloc\fR(3NSL), \fBt_bind\fR(3NSL), \fBt_error\fR(3NSL),
  \fBt_getinfo\fR(3NSL), \fBt_look\fR(3NSL), \fBt_open\fR(3NSL),
  \fBt_rcvudata\fR(3NSL), \fBt_rcvuderr\fR(3NSL), \fBattributes\fR(5)
--- 291,299 ----