Added section about destinations to oipkg docs.

1 files changed, 4 insertions, 2 deletions

diff --git a/docs/usermanual/embeddedkonsole.sgm b/docs/usermanual/embeddedkonsole.sgm
index 4ba0287..838e705 100644
--- a/docs/usermanual/embeddedkonsole.sgm
+++ b/docs/usermanual/embeddedkonsole.sgm
@@ -56,12 +56,14 @@ You can edit or hide this menu from <GUIMenu>Options</GUIMenu>&arrow;
 <para>
 A shell is a program that accepts input from a user, and runs commands.  Each
 "command" in the shell is actually a separate program (unless you are using a
 shell like BusyBox, which makes some of the more common commands part of its own
 program in order to save space).  Shells can actually be very powerful, and many 
 
+
+
 of them allow you to write something called "shell scripts" which are just a
 sequence of commands, sometimes with some flow control statements, saved to a 
 file and run each time the script is run.  For the most part, the average user
 does not need to know about any of this, though.  If you are running Opie on the
 Familiar distribution, it is advisable to install the bash shell (ipkg install
 bash) because it offers things like tab completion, use of the backspace key,
@@ -143,13 +145,13 @@ To delete a file, run the "rm" command, and to delete a directory, run the
 argument.  The rmdir command requires the directory to be empty, so if you want
 to delete a directory that is not empty, along with all its contents, run
 <userinput>rm -r dir</userinput>.
 </para>
 </section>
 
-<section><title>Linking Files</title>
+<section id=symlink><title>Linking Files</title>
 <para>
 In Linux, you can have a special file called a "symbolic link" that acts just
 like a copy of another file, except it takes up less space.  This is convinient
 if two applications are looking for the same file in two separate places, 
 because the file can be in both places at once, without taking up any extra
 space, and any change to one is automatically applied to the other (really, 
@@ -157,7 +159,7 @@ there is only one file, the link is just a file pointing to the original file).
 This is also useful for naming applications independant of their version number.
  For instance, you could have a link called "application" that points to
 "application1.0".  To create a link, use the following command:
 <userinput>ln -s originalfile link</userinput>.
 </para>
 </section>
-</chapter>
\ No newline at end of file
+</chapter>