6205 onbld manuals should be declared as 1onbld
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

@@ -1,6 +1,5 @@
-.\" ident       "%Z%%M% %I%     %E% SMI"
 .\" Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
 .\" Use is subject to license terms.
 .\"
 .\" CDDL HEADER START
 .\"

@@ -19,11 +18,11 @@
 .\" fields enclosed by brackets "[]" replaced with your own identifying
 .\" information: Portions Copyright [yyyy] [name of copyright owner]
 .\"
 .\" CDDL HEADER END
 .\"
-.TH jstyle 1 "22 November 2005"
+.TH jstyle 1ONBLD "22 November 2005"
 .SH NAME
 .I jstyle
 \- check for some common stylistic errors in Java source files
 .SH SYNOPSIS
 \fBjstyle [-chptvC] [file...]\fP

@@ -32,18 +31,18 @@
 .IX "OS-Net build tools" "jstyle" "" "\fBjstyle\fP"
 .LP
 .B jstyle
 inspects Java source files (*.java) for common stylistic errors.  It
 is similar to
-.BR cstyle (1)
+.BR cstyle (1ONBLD)
 in that it attempts to check for the style
 documented in \fI/shared/ON/general_docs/cstyle.ms.pdf\fP, although by
 necessity is modified to work with Java-specific constructs.  Note that
 there is much in that document that
 .I cannot
 be checked for; just because your code is
-.BR jstyle (1)
+.BR jstyle (1ONBLD)
 clean does not
 mean that you've followed Sun's Java style.  \fICaveat emptor\fP.
 .LP
 .SH OPTIONS
 .LP

@@ -103,11 +102,11 @@
 If the old file gave no errors for one of the invocations, the new file
 must also give no errors.  This way, files cannot become unclean.
 .LP
 .SH BUGS
 .LP
-.BR jstyle (1)
+.BR jstyle (1ONBLD)
 cannot disambiguate Java generic type parameters or
 arguments that span multiple lines from relational operators.  For example:
 .RS 4
 .HP 4
 private class Foo<A extends Bar,