summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpvalchev <pvalchev@openbsd.org>2003-06-21 00:32:59 +0000
committerpvalchev <pvalchev@openbsd.org>2003-06-21 00:32:59 +0000
commit268385fbdc42a3f2cf434f5ff0331695b7c9362f (patch)
treeabbe821efc654de7c8e8ab91976490f245850f92
parenttypo (diff)
downloadwireguard-openbsd-268385fbdc42a3f2cf434f5ff0331695b7c9362f.tar.xz
wireguard-openbsd-268385fbdc42a3f2cf434f5ff0331695b7c9362f.zip
minor grammar
-rw-r--r--distrib/notes/mvme68k/install4
1 files changed, 2 insertions, 2 deletions
diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install
index cb6f6c8203b..27c8b6add54 100644
--- a/distrib/notes/mvme68k/install
+++ b/distrib/notes/mvme68k/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.18 2003/01/04 00:18:08 miod Exp $
+dnl $OpenBSD: install,v 1.19 2003/06/21 00:32:59 pvalchev Exp $
OpenBSDInstallPrelude
There are several ways to install OpenBSD onto a disk. The easiest way
@@ -173,7 +173,7 @@ syslog and tcpdump(8) to get visibility of what's happening (or not).
Your MACHINE expects to be able to download a second stage bootstrap
program via TFTP after having acquired its IP address through RevARP when
instructed to boot "over the net". It will look for a filename composed of
-the machine's IP address followed by the machine's architecture, separated
+the machine's IP address, followed by the machine's architecture, separated
by a period. For example, a MACHINE board which has been assigned IP
address 130.115.144.11, will make an TFTP request for `8273900B.MACHINE'.
Normally, this file is a symbolic link to an appropriate second-stage