correcting typo seperate-->separate

Author: Paul Cobbaut

modules/init/030_init_theory.xml

@@ -74,7 +74,7 @@ l3:3:wait:/etc/rc.d/rc 3
 l4:4:wait:/etc/rc.d/rc 4
 l5:5:wait:/etc/rc.d/rc 5
 l6:6:wait:/etc/rc.d/rc 6</screen>
-		<para>In both cases, this means that <command>init</command> will start the rc script with the runlevel as the only parameter. Actually <command>/etc/inittab</command><indexterm><primary>/etc/inittab</primary></indexterm> has fields seperated by colons. The second field determines the runlevel in which this line should be executed. So in both cases, only one line of the seven will be executed, depending on the runlevel set by <command>initdefault</command>.</para>
+		<para>In both cases, this means that <command>init</command> will start the rc script with the runlevel as the only parameter. Actually <command>/etc/inittab</command><indexterm><primary>/etc/inittab</primary></indexterm> has fields separated by colons. The second field determines the runlevel in which this line should be executed. So in both cases, only one line of the seven will be executed, depending on the runlevel set by <command>initdefault</command>.</para>
 	</section>
 	<section><title>rc directories</title>
 		<para>When you take a look any of the <command>/etc/rcX.d/</command><indexterm><primary>/etc/rcX.d/</primary></indexterm> directories, then you will see a lot of (links to) scripts who's name start with either uppercase K or uppercase S.</para>

modules/samba_domain_controller/040_samba_domain_controller_practice.xml

@@ -6,7 +6,7 @@
 	<para>4. Setup and verify the proper working of roaming profiles.</para>
 	<para>5. Find information about home directories for users, set them up and verify that users receive their home directory mapped under the H:-drive in MS Windows Explorer.</para>
 	<para>6. Use a couple of samba domain groups with members to set acls on ntfs. Verify that it works!</para>
-	<para>7. Knowing that the &#037;m variable contains the computername, create a seperate log file for every computer(account).</para>
+	<para>7. Knowing that the &#037;m variable contains the computername, create a separate log file for every computer(account).</para>
 	<para>8. Knowing that &#037;s contains the client operating system, include a smb.&#037;s.conf file that contains a share. (The share will only be visible to clients with that OS).</para>
 	<para>9. If time permits (or if you are waiting for other students to finish this practice), then combine "valid users" and "invalid users" with groups and usernames with "hosts allow" and "hosts deny" and make a table of which get priority over which.</para>
 </section>

modules/samba_securing_shares/030_samba_securing_shares_theory.xml

@@ -37,7 +37,7 @@
 </section>
 <section><title>security based on ip-address</title>
 	<section><title>hosts allow</title>
-		<para>The <command>hosts allow</command><indexterm><primary>hosts allow (Samba)</primary></indexterm> or <command>allow hosts</command><indexterm><primary>allow hosts (Samba)</primary></indexterm> parameter is one of the key advantages of Samba. It allows access control of shares on the ip-address level. To allow only specific hosts to access a share, list the hosts, seperated by comma's.</para>
+		<para>The <command>hosts allow</command><indexterm><primary>hosts allow (Samba)</primary></indexterm> or <command>allow hosts</command><indexterm><primary>allow hosts (Samba)</primary></indexterm> parameter is one of the key advantages of Samba. It allows access control of shares on the ip-address level. To allow only specific hosts to access a share, list the hosts, separated by comma's.</para>
 		<screen>allow hosts = 192.168.1.5, 192.168.1.40</screen>
 		<para>Allowing entire subnets is done by ending the range with a dot.</para>
 		<screen>allow hosts = 192.168.1.</screen>