Added optional pulseaudio configuration, ammended the status of dos2unix, various touch-ups.

Slint.md

@@ -9,7 +9,9 @@ Where some of the root commands will be, you can precede the command with the wo
 Also, it is assumed that your Slint system is fully upgraded, if it isn't, do that now, as it will be very important that nothing should need to be upgraded for one of the steps to follow.
 
     # slapt-get -u
-
+followed by the Enter key.
+    # slapt-get -upgrade
+followed by the Enter key.
 
 Also, you may want to attach a monitor to your pc if it's a desktop as even though you may not need to see graphics the X windowing system will very likely expect one and will work better with one then without.
 
@@ -17,6 +19,48 @@ Also, you may want to attach a monitor to your pc if it's a desktop as even thou
 **CAUTION! CAUTION! CAUTION!**
 Some of these instructions will involve editing files, which I must strongly recommend that you back up before editing, in case you make a mistake.
 
+##Optional Pulseaudio Configuration
+
+Okay, this already sounds scary, but don't worry, it's really not, and you may like things the way they are by default, so I'll briefly describe my test box's setup.
+It's got two sound cards, one built-in audio, and a usb headset. 
+Speech for the regular text console goes through the built-in sound card, and everything else goes through the usb headset, including the output of the Orca screen reader, and every other sound too, music, games and even things sent through speech-dispatcher that are not screen reader related.
+This is not the default behavior of Slint, as I said before, you may have reason to do something differently, or leaving things as they are so you could skip this step, but I've found this handy because it seems to speed up game play a bit, and all the speech, game sounds etc, come from one place.
+This modification is really easy to do, only one line in one file need be changed.
+This means you'll be using a text editor, whichever one you like and your magical superuser powers.
+So unless you're skipping this step, let's begin.
+
+So in your console, or even your gui terminal if you like that, we'll be in the home directory.
+Mine would be /home/testo, which of course I'll refer to later in the guide, yours of course will be different.
+We'll go through some of these steps again later, so it will be pretty familiar by the time we're done.
+As we must be the superuser here, we're going to open a file in the /etc/speech-dispatcher directory called speechd.conf, which we're going to quickly back up before we edit.
+We'll use the cp command to copy the speechd.conf file to another file with a different name, so in case something goes wrong, you'll be able to restore the original.
+So now type
+    $ sudo cp /etc/speech-dispatcher/speechd.conf /etc/speech-dispatcher/speechd.conf.backup
+followed by the Enter key.
+You'll likely be asked for your password, which is the root user password.
+Go ahead and type that followed by the Enter key, and you'll be returned to your prompt.
+Now we can edit the file safely.
+next we open the text editor of choice, for my test box it's Nano so the command would look like this:
+    $sudo nano /etc/speech-dispatcher/speechd.conf
+followed by the Enter key.
+You may have a different editor so do the next step however your editor works.
+You want to search for the line that says:
+    AudioOutputMethod "libao"
+All you need to do here is to replace what's between the quotes, "libao" with the word "pulse"
+and then save the file.
+If you have a graphical terminal running when you do this, you'll lose speech when you do thefollowing command, but it will come back. If you've done this in a console, and don't have a graphical user interface running yet, your speech will be fine.
+What we need to do is to kill any currently running instances of speech-dispatcher so that when it gets called again, most likely by Orca, it will direct speech output through Pulseaudio.
+so here, we type the following command.
+    $ sudo killall speech-dispatcher
+followed by the Enter key.
+If you get the responce:
+    No process found.
+That's okay. 
+In the regular text console your speech would only stop if you're using a speech method that depends upon speech-dispatcher, such as speechd-up for example.
+If you're using espeakup, you're using alsa, which will not be affected by this change.
+The speech in your graphical terminal will stop upon pressing the Enter key. Simply press the Enter key in your graphical terminal and speech will restart, as Orca is now sending speech through Pulseaudio in the second sound device.
+Now all your game output as well as any speech in the graphical user interface will all come from the same place.
+So now on to the next step... Way to go you command line ninjas!
 
 ## Getting audiogame-manager
 
@@ -126,11 +170,12 @@ followed by the Enter key.
 We now know that the file is executable, so we'll run it, and then silence the speech with Keypad Enter.
 
     # ./alien-multilib-rsync.sh
-followed by the Enter key, then silence the speech with the Keypad Enter key.
+followed by the Enter key, then silence the speech with the Keypad Enter key for example, if using espeakup.
+You can temporarily disable speech in your graphcal terminal too, by using the key combination insert plus letter s. but you'll have to use that combination again to turn speech back on.
 
 
-On a decent connection this can take anywhare from a half hour, or perhaps a bit longer, on older system it could be an hour or so.
-You can check to see if things are still processing by typing the Control key, and if it's still busy, just type the Keypad Enter key and speech will go silent until the next key press.
+On a decent connection this can take anywhare from a half hour, or perhaps a bit longer, on older systems it could be an hour or so.
+You can check to see if things are still processing by typing the Control key, and if it's still busy, just type the Keypad Enter key and speech will go silent until the next key press, or using the insert plus letter s combination in your gui terminal.
 When it's finally done, and you're returned to the command prompt, you'll now be multi-lib capable, so next it's time to go get WINE and anything else we need.
 Having made sure the system is fully upgraded before beginning to do anything in this guide, we're now ready to procede to the next step, which is to blacklist the packages that make the system multi-lib, so future system upgrades will not over-write them and undo all your hard work.
 As we're still logged in as the super user, the next thing we're going to do is to go to a directory outside the home directory of your normal user, with the following command.
@@ -252,22 +297,16 @@ There'll probably be a dialog box asking if you'd like to hear the latest news,
 Once the news plays, audiogame-manager then checks to see what programs it needs and will tell you what's missing that you'll need to install.
 I've been running a test box while doing this article, and discovered that after WINE installed, audiogame-manager reported two packages that were not installed.
 They happened to be cabextract and dos2unix and they are rereally easy to install.
-
+As it happens, dos2unix is no longer required as of the revision of this documentation.
 
 So, letsget back to the good ol' superuser mode.
-We can even do it from here in the audiogame-manager directory. Since you now have the instruction on how to do that, we won't rehash that, so once you're superuser again, lets install some packages.
+We can even do it from here in the audiogame-manager directory. Since you now have the instruction on how to do that, we won't rehash that, so once you're superuser again, lets install that package.
 We'll install cabextract, like this.
 
     # slapt-get -i cabextract
 followed by the Enter key.
 
 
-When that finishes, we next will install dos2unix in the same way.
-
-    # slapt-get -i dos2unix
-Again followed by the Enter key.
-
-
 Now we can exit superuser mode by typing
 
     # exit