--- wikisrc/ports/sandpoint/instqnap.mdwn	2013/10/31 21:05:10	1.1
+++ wikisrc/ports/sandpoint/instqnap.mdwn	2015/09/04 22:22:18	1.2
@@ -4,7 +4,7 @@ Introduction
 <table>
 <tbody>
 <tr class="odd">
-<td align="left"><p>This document describes in depth how to prepare your QNAP Turbo Station for installing OS/sandpoint. The following models are supported:</p>
+<td align="left"><p>This document describes in depth how to prepare your QNAP Turbo Station for installing NetBSD/sandpoint. The following models are supported:</p>
 <ul>
 <li>TS-100 (32MB, 200MHz, Intel GBit Ethernet, V1.02 board)</li>
 <li>TS-100 (32MB, 200MHz, Realtek GBit Ethernet, V200 board)</li>
@@ -12,7 +12,7 @@ Introduction
 <li>TS-101 (64MB, 266MHz, Realtek GBit Ethernet, V200 board)</li>
 <li>TS-201 (128MB, 266MHz, Realtek GBit Ethernet)</li>
 </ul>
-<p>To install OS/sandpoint you will have to open the case, to get access to the serial console, and connect a serial converter from TTL to RS232 signal levels.</p></td>
+<p>To install NetBSD/sandpoint you will have to open the case, to get access to the serial console, and connect a serial converter from TTL to RS232 signal levels.</p></td>
 <td align="left"><img src="../../images/ports/sandpoint/qnap_front.jpg" alt="TS-101 front view" /></td>
 </tr>
 </tbody>
@@ -100,7 +100,7 @@ using [U-Boot](http://www.denx.de/wiki/U
 Loader.
 
 Now you can connect with any terminal program to the Turbo Station's
-serial console. The easiest approach may be to use OS's `tip(1)` command
+serial console. The easiest approach may be to use NetBSD's `tip(1)` command
 to make a direct console connection at 115200bps.
 
     # tip -115200 console
@@ -129,7 +129,7 @@ altboot
 -------
 
 The `altboot(8)` utility functions as a bridge between the QNAP firmware
-and the OS kernel startup environment. NAS firmware often provides no
+and the NetBSD kernel startup environment. NAS firmware often provides no
 means to boot a kernel from disk or from the network and doesn't
 initialize all hardware correctly. We will also use it to pass a
 bootinfo list to the kernel.
@@ -183,7 +183,7 @@ Boot the INSTALL kernel with altboot
 ------------------------------------
 
 Now you can use `altboot` to launch the `netbsd-INSTALL` kernel for
-installing OS. You may choose to load it via TFTP or from NFS. For TFTP
+installing NetBSD. You may choose to load it via TFTP or from NFS. For TFTP
 you have to enable `tftpd(8)` in `/etc/inetd.conf`, and for NFS there is
 a documentation at [The Network File
 System](http://www.NetBSD.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs).
@@ -200,7 +200,7 @@ appropriate `dhcpd.conf` entry could loo
 
 The `root-path` option is only needed when using NFS and should match
 your exported NFS directory. Uncompress `netbsd-INSTALL.gz` from the
-OS/sandpoint distribution and copy it into the NFS or TFTP directory.
+NetBSD/sandpoint distribution and copy it into the NFS or TFTP directory.
 Then start the DHCP, NFS or TFTP server and boot the installation kernel
 from the firmware either with
 
@@ -289,7 +289,7 @@ the kernel via network and launches it:
     erase ^H, werase ^W, kill ^U, intr ^C, status ^T
     Terminal type? [vt100]
 
-Just follow the usual procedure to install a OS system.
+Just follow the usual procedure to install a NetBSD system.
 
 Sandpoint installation window
 Post installation steps
@@ -335,4 +335,4 @@ reboot:
 The `\` is important for `setenv` not to misinterpret the `;` as the end
 of the command.
 
-Have fun with your mini OS server!
+Have fun with your mini NetBSD server!