10057 Man page misspellings ouput particuliar overriden
Reviewed by: Gergő Mihály Doma <domag02@gmail.com>

*** 21,31 ****
  \fBint\fR \fBlgrp_affinity_set\fR(\fBidtype_t\fR \fIidtype\fR, \fBid_t\fR \fIid\fR, \fBlgrp_id_t\fR \fIlgrp\fR,
       \fBlgrp_affinity_t\fR \fIaffinity\fR);
  .fi
  
  .SH DESCRIPTION
- .sp
  .LP
  The \fBlgrp_affinity_get()\fR function returns the affinity that the LWP or set
  of LWPs specified by the \fIidtype\fR and \fIid\fR arguments have for the given
  lgroup.
  .sp
--- 21,30 ----
*** 60,71 ****
  the strongest affinity that the thread can run on is known as its "home lgroup"
  (see \fBlgrp_home\fR(3LGRP)) and is usually the operating system's first choice
  of where to run the thread and allocate its memory.
  .sp
  .LP
!  There are different levels of affinity that can be specified by a thread for a
! particuliar lgroup.  The levels of affinity are the following from strongest to
  weakest:
  .sp
  .in +2
  .nf
  LGRP_AFF_STRONG         /* strong affinity */
--- 59,70 ----
  the strongest affinity that the thread can run on is known as its "home lgroup"
  (see \fBlgrp_home\fR(3LGRP)) and is usually the operating system's first choice
  of where to run the thread and allocate its memory.
  .sp
  .LP
! There are different levels of affinity that can be specified by a thread for a
! particular lgroup.  The levels of affinity are the following from strongest to
  weakest:
  .sp
  .in +2
  .nf
  LGRP_AFF_STRONG         /* strong affinity */
*** 93,107 ****
  binding and manipulation are examples of events that can cause the operating
  system to change a thread's home lgroup for which it has a weak affinity.
  .sp
  .LP
  The \fBLGRP_AFF_NONE\fR affinity signifies no affinity and can be used to
! remove a thread's affinity for a particuliar lgroup.  Initially, each thread
  has no affinity to any lgroup.  If a thread has no lgroup affinities set, the
  operating system chooses a home lgroup for the thread with no affinity set.
  .SH RETURN VALUES
- .sp
  .LP
  Upon successful completion, \fBlgrp_affinity_get()\fR returns the affinity for
  the given lgroup.
  .sp
  .LP
--- 92,105 ----
  binding and manipulation are examples of events that can cause the operating
  system to change a thread's home lgroup for which it has a weak affinity.
  .sp
  .LP
  The \fBLGRP_AFF_NONE\fR affinity signifies no affinity and can be used to
! remove a thread's affinity for a particular lgroup.  Initially, each thread
  has no affinity to any lgroup.  If a thread has no lgroup affinities set, the
  operating system chooses a home lgroup for the thread with no affinity set.
  .SH RETURN VALUES
  .LP
  Upon successful completion, \fBlgrp_affinity_get()\fR returns the affinity for
  the given lgroup.
  .sp
  .LP
*** 109,119 ****
  .sp
  .LP
  Otherwise, both functions return \(mi1 and set \fBerrno\fR to indicate the
  error.
  .SH ERRORS
- .sp
  .LP
  The \fBlgrp_affinity_get()\fR and \fBlgrp_affinity_set()\fR functions will fail
  if:
  .sp
  .ne 2
--- 107,116 ----
*** 143,153 ****
  .RS 10n
  The specified lgroup or LWP(s) was not found.
  .RE
  
  .SH ATTRIBUTES
- .sp
  .LP
  See \fBattributes\fR(5) for descriptions of the following attributes:
  .sp
  
  .sp
--- 140,149 ----
*** 161,168 ****
  _
  MT-Level        MT-Safe
  .TE
  
  .SH SEE ALSO
- .sp
  .LP
  \fBlgrp_home\fR(3LGRP), \fBliblgrp\fR(3LIB), \fBattributes\fR(5)
--- 157,163 ----