3768 fnmatch(5) is worded poorly

@@ -7,29 +7,26 @@
 .\" 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 FNMATCH 5 "Mar 28, 1995"
+.TH FNMATCH 5 "Jun 14, 2015"
 .SH NAME
 fnmatch \- file name pattern matching
 .SH DESCRIPTION
-.sp
 .LP
 The pattern matching notation described below  is used to specify patterns for
 matching strings in the shell. Historically, pattern matching notation is
 related to, but slightly different from, the regular expression notation. For
 this reason, the description of the rules for this pattern matching notation is
 based on the description of regular expression notation described on the
 \fBregex\fR(5) manual page.
 .SS "Patterns Matching a Single Character"
-.sp
 .LP
-The following \fIpatterns matching a single character\fR match a single
-character: \fIordinary characters\fR, \fIspecial pattern characters\fR and
-\fIpattern bracket expressions\fR. The pattern bracket expression will also
-match a single collating element.
+The following patterns match a single character: \fIordinary characters\fR,
+\fIspecial pattern characters\fR and \fIpattern bracket expressions\fR. The pattern
+bracket expression will also match a single collating element.
 .sp
 .LP
 An ordinary character is a pattern that matches itself. It can be any character
 in the supported character set except for \fINUL\fR, those special shell
 characters that require quoting, and the following three special pattern

@@ -160,11 +157,10 @@
 characters (sometimes called metacharacters). If used without this protection,
 syntax errors can result or implementation extensions can be triggered. For
 example, the KornShell supports a series of extensions based on parentheses in
 patterns; see  \fBksh\fR(1)
 .SS "Patterns Matching Multiple Characters"
-.sp
 .LP
 The following rules are used to construct \fIpatterns matching multiple
 characters\fR from \fIpatterns matching a single character\fR:
 .RS +4
 .TP

@@ -236,11 +232,10 @@
 matches the strings \fBad\fR, \fBabcd\fR, \fBefabcd\fR, \fBaaaad\fR and
 \fBadddd\fR.
 .RE
 
 .SS "Patterns Used for Filename Expansion"
-.sp
 .LP
 The rules described so far in \fBPatterns\fR \fBMatching\fR \fBMultiple\fR
 \fBCharacters\fR and \fBPatterns\fR \fBMatching\fR \fBa\fR \fBSingle\fR
 \fBCharacter\fR are qualified by the following rules that apply when pattern
 matching notation is used for filename expansion.

@@ -303,8 +298,7 @@
 sequence in effect in the current locale. If the pattern contains an invalid
 bracket expression or does not match any existing filenames or pathnames, the
 pattern string is left unchanged.
 .RE
 .SH SEE ALSO
-.sp
 .LP
 \fBfind\fR(1), \fBksh\fR(1), \fBfnmatch\fR(3C), \fBregex\fR(5)