4344 Minor typos in the 3nsl man pages

*** 5,15 ****
  .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
  .\"  This notice shall appear on any product containing this material.
  .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
  .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
  .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
! .TH T_BIND 3NSL "May 7, 1998"
  .SH NAME
  t_bind \- bind an address to a transport endpoint
  .SH SYNOPSIS
  .LP
  .nf
--- 5,15 ----
  .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
  .\"  This notice shall appear on any product containing this material.
  .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
  .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
  .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
! .TH T_BIND 3NSL "Dec 27, 2013"
  .SH NAME
  t_bind \- bind an address to a transport endpoint
  .SH SYNOPSIS
  .LP
  .nf
*** 26,36 ****
  .LP
  This routine is part of the \fBXTI\fR interfaces that 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
! \fBtiuser.h\fRheader file must be used.  Refer to the  \fBTLI\fR
  \fBCOMPATIBILITY\fR section for a description of differences between the two
  interfaces.
  .sp
  .LP
  This function associates a protocol address with the transport endpoint
--- 26,36 ----
  .LP
  This routine is part of the \fBXTI\fR interfaces that 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
! \fBtiuser.h\fR header file must be used.  Refer to the  \fBTLI\fR
  \fBCOMPATIBILITY\fR section for a description of differences between the two
  interfaces.
  .sp
  .LP
  This function associates a protocol address with the transport endpoint
*** 108,118 ****
  requirement on transport providers; see \fBWARNINGS\fR below. On return, the
  \fIqlen\fR field in \fIret\fR will contain the negotiated value.
  .sp
  .LP
  If \fIfd\fR refers to a connection-mode service, this function allows more than
! one transport endpoint to be bound to the same protocol address.  but it is not
  possible to bind more than one protocol address to the same transport endpoint.
  However, the transport provider must also support this capability. If a user
  binds more than one transport endpoint to the same protocol address, only one
  endpoint can be used to listen for connection indications associated with that
  protocol address. In other words, only one \fBt_bind()\fR for a given protocol
--- 108,118 ----
  requirement on transport providers; see \fBWARNINGS\fR below. On return, the
  \fIqlen\fR field in \fIret\fR will contain the negotiated value.
  .sp
  .LP
  If \fIfd\fR refers to a connection-mode service, this function allows more than
! one transport endpoint to be bound to the same protocol address.  But it is not
  possible to bind more than one protocol address to the same transport endpoint.
  However, the transport provider must also support this capability. If a user
  binds more than one transport endpoint to the same protocol address, only one
  endpoint can be used to listen for connection indications associated with that
  protocol address. In other words, only one \fBt_bind()\fR for a given protocol