Project

General

Profile

Actions

Bug #4213

closed

Missing spaces in man pages

Added by Marcel Telka almost 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
manpage - manual pages
Start date:
2013-10-15
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:

Description

There is missing space before "will" here in mutex_init(3c):

         then   unlock   the   mutex.  All  subsequent  calls  to
         mutex_lock()will then behave  normally.   Only  the  new
         owner  can  make the mutex consistent. If for any reason

Missing space between "the" and "_file" in enable_extended_FILE_stdio(3c):

     Since the_file field has been renamed, attempts to recompile
     this  code will fail.  The application should be changed not
     to use this field in the FILE structure.

Missing space before 'is' in diff3(1):

     ====1
              filename1is different

     ====2
              filename2is different

     ====3
              filename3is different

Missing space between "LOCK_ROBUST" and "above" here in mutex_init(3c):

     These rules do not apply to  LOCK_ROBUST  mutexes.  See  the
     description  for  LOCK_ROBUSTabove.  If default mutex attri-
     butes are used, the macro DEFAULTMUTEX can be used  to  ini-
     tialize mutexes that are statically allocated.

Missing space after "include" in xdr_simple(3nsl):

SYNOPSIS
     #include<rpc/xdr.h>

Missing space after "include" in t_rcvudata(3nsl):

  Interface Header
     The XTI interfaces use the header file,  xti.h.  TLI  inter-
     faces  should  not  use  this  header.   They should use the
     header:
       #include<tiuser.h>

Missing space between "returns" and "FALSE" here in rpc_control(3nsl):

RETURN VALUES
     This routine returns TRUE if the  operation  was  successful
     and returnsFALSE otherwise.

Missing space between "joe" and "and" in kerberos(5) man page:

     The first four cases are user principals. In the  first  two
     cases,  it is assumed that the user joe is in the same realm
     as the client, so no realm is specified.  Note  that  joeand
     joe/admin  are  different  principals, even if the same user
     uses them; joe/admin has different privileges from joe.  The
Actions

Also available in: Atom PDF