From 2e58d19acf484290f8361fc59e8caaf38edc777e Mon Sep 17 00:00:00 2001
From: P. J. McDermott <pehjota>
Date: Tue, 02 Sep 2014 12:35:07 -0400
Subject: doc/pkg/basic-expat: Drop "(1)" from opkbuild

There's no opkbuild(1) manual page yet.
---
(limited to 'doc')

diff --git a/doc/pkg/basic-expat.mdwn b/doc/pkg/basic-expat.mdwn
index e2a1d44..a3791c0 100644
--- a/doc/pkg/basic-expat.mdwn
+++ b/doc/pkg/basic-expat.mdwn
@@ -135,7 +135,7 @@ installing data files to be provided by binary packages".
 Looking Through the Source
 --------------------------
 
-With a "[no-op][no-op]" target in `build`, we can make **opkbuild**(1) prepare a
+With a "[no-op][no-op]" target in `build`, we can make **opkbuild** prepare a
 *[build work area][spf-work-area]* with the unpacked source code and stop.  This
 target isn't required by SPF 2.0, but it seems to facilitate a nice workflow.
 So begin writing `build` as follows:
@@ -155,12 +155,12 @@ The `build` makefile must be executable, so set its file mode:
 
     $ chmod 755 build
 
-We can now make **opkbuild**(1) prepare our build work area.
+We can now make **opkbuild** prepare our build work area.
 
     $ opkbuild -b -c -T nop
 
 The options are explained in the help output of opkbuild, obtained by running
-`opkbuild -h`.  The `-b` option tells **opkbuild**(1) to build only binary
+`opkbuild -h`.  The `-b` option tells **opkbuild** to build only binary
 packages (no source package).  The `-c` option tells it to not clean up the work
 area after building packages.  The `-T` option specifies a target to be built
 instead of the standard `build` and `install` targets.
@@ -437,7 +437,7 @@ With these pathname patterns done, we can add **oh-installfiles**(1) to our
             oh-autoinstall
             oh-installfiles
 
-Now run **opkbuild**(1) again:
+Now run **opkbuild** again:
 
     $ opkbuild -b -c -T install
 
@@ -705,14 +705,14 @@ Building Everything
 Now we can build all of our source and binary packages and verify that
 everything is correct.
 
-**opkbuild**(1) maintains a cache file in the work area; because we've modified
-the metadata in our packaging since the first time we ran **opkbuild**(1), this
+**opkbuild** maintains a cache file in the work area; because we've modified
+the metadata in our packaging since the first time we ran **opkbuild**, this
 cache file is out-of-date.  Also, we should make sure that the entire build
 process still works.  So let's clean up the work area before going any further.
 
     $ rm -Rf tmp/
 
-Now let's run **opkbuild**(1) again, this time completely building all of our
+Now let's run **opkbuild** again, this time completely building all of our
 source and binary packages and cleaning up automatically when we're done.
 
     $ opkbuild
--
cgit v0.9.1