Update section reference with "cross" name.

1 files changed, 1 insertions, 1 deletions

diff --git a/dev.html b/dev.html
index 9d02d26..d85dc6a 100755
--- a/dev.html
+++ b/dev.html
@@ -45,7 +45,7 @@
 <p>An obvious boot sequencing tool is <a href="http://svn.savannah.nongnu.org/viewvc/insserv/trunk/?root=sysvinit">"insserv"</a> maintained by Werner Fink and used by Debian and openSUSE.  However, this C program (in compliance with the LSB) assumes the use of runlevels.  This operating system uses the init daemon of BusyBox, which <a href="http://git.busybox.net/busybox/tree/init/init.c?id=3da46c81#n1221">doesn't support runlevels</a>.  Therefore, we'll need to either modify insserv to work without runlevels or write our own tool for installing symbolic links to init scripts.</p>
 <p>Additionally, we need to decide how completely we'll conform, if at all, with the LSB in this area.</p>
 <h3>Multiarch</h3>
-<p>Multiarch refers to the ability to install and use packages built for non-native architectures.  It is currently being <a href="http://wiki.debian.org/Multiarch">documented and implemented</a> in Debian and Ubuntu.  Multiarch is useful for this distribution because it makes cross compiling easy (see "Package Cross Building Tool" and "Multiarch Toolchain Packages" below).</p>
+<p>Multiarch refers to the ability to install and use packages built for non-native architectures.  It is currently being <a href="http://wiki.debian.org/Multiarch">documented and implemented</a> in Debian and Ubuntu.  Multiarch is useful for this distribution because it makes cross compiling easy (see "Package Cross Building Tool" and "Multiarch Cross Toolchain Packages" below).</p>
 <p>Simply speaking, there are six <a href="https://wiki.ubuntu.com/MultiarchSpec#Design">aspects of a multiarch implementation</a>:</p>
 <ul>
 	<li>