From de8e8b3d9e83ea4607cbf6937ec071eab86a14d8 Mon Sep 17 00:00:00 2001
From: Christopher Anderson <cba@fedoraproject.org>
Date: Tue, 15 Jan 2013 18:05:18 -0800
Subject: [PATCH] Corrected a few speling errrors.


Signed-off-by: Christopher Anderson <cba@fedoraproject.org>
---
 JBossEAP5/eap5-ocil.xml                            |  10 +-
 RHEL6/README                                       |   2 +-
 RHEL6/input/auxiliary/nist_support.xml             |   2 +-
 RHEL6/input/auxiliary/transition_notes.xml         |  18 ++--
 .../input/checks/audit_rules_dac_modification.xml  |   2 +-
 .../file_permissions_httpd_server_conf_files.xml   |   2 +-
 .../checks/file_permissions_ldap_server_files.xml  |   2 +-
 .../checks/gconf_gnome_screensaver_idle_delay.xml  |   2 +-
 .../ldap_server_config_bdb_file_security.xml       |   2 +-
 .../ldap_server_config_directory_file_security.xml |   2 +-
 RHEL6/input/checks/mount_option_dev_shm_noexec.xml |   2 +-
 RHEL6/input/checks/mount_option_dev_shm_nosuid.xml |   2 +-
 RHEL6/input/checks/mount_option_tmp_noexec.xml     |   2 +-
 RHEL6/input/checks/mount_option_tmp_nosuid.xml     |   2 +-
 ...mail_relay_smtp_auth_for_untrusted_networks.xml |   2 +-
 RHEL6/input/checks/rpm_verify_hashes.xml           |   2 +-
 RHEL6/input/checks/sshd_idle_timeout.xml           |   2 +-
 RHEL6/input/profiles/nist-CL-IL-AL.xml             |   6 +-
 RHEL6/input/services/ldap.xml                      |   2 +-
 RHEL6/input/system/permissions/files.xml           |   4 +-
 RHEL6/input/system/permissions/partitions.xml      |  10 +-
 RHEL6/input/system/software/updating.xml           |   2 +-
 RHEL6/references/cce-rhel5.xml                     |  18 ++--
 RHEL6/references/disa-cci-list.xml                 | 114 ++++++++++-----------
 RHEL6/references/disa-os-srg-v1r1.xml              |   4 +-
 RHEL6/references/disa-stig-rhel5-v1r0.6-oval.xml   |  14 +--
 .../disa-stig-rhel5-v1r0.6-xccdf-manual.xml        |  26 ++---
 RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf.xml  |   6 +-
 RHEL6/references/usgcb-rhel5desktop-oval.xml       |  16 +--
 RHEL6/references/usgcb-rhel5desktop-xccdf.xml      |  26 ++---
 30 files changed, 153 insertions(+), 153 deletions(-)

diff --git a/JBossEAP5/eap5-ocil.xml b/JBossEAP5/eap5-ocil.xml
index 52440df..07790ae 100644
--- a/JBossEAP5/eap5-ocil.xml
+++ b/JBossEAP5/eap5-ocil.xml
@@ -2234,7 +2234,7 @@
 			</instructions>
 		</boolean_question>
 		<boolean_question id="ocil:com.redhat.eap5.scap:question:11170101">
-			<question_text>Are miscellanous features being used by deployed applications?     [Please reference Rule ID #111701 in /docs/JBossEAP5_Guide.html for more information]</question_text>
+			<question_text>Are miscellaneous features being used by deployed applications?     [Please reference Rule ID #111701 in /docs/JBossEAP5_Guide.html for more information]</question_text>
 			<instructions><title>Instructions</title>
 				<step><description>Interview JBoss administrators and/or platform administrators. If the feature or service is not used, validate its removal.</description></step>
 			</instructions>
@@ -2336,7 +2336,7 @@
 			</instructions>
 		</boolean_question>
 		<boolean_question id="ocil:com.redhat.eap5.scap:question:11170102">
-			<question_text>Have the miscellanous features disabled or deleted?     [Please reference Rule ID #111701 in /docs/JBossEAP5_Guide.html for more information]</question_text>
+			<question_text>Have the miscellaneous features disabled or deleted?     [Please reference Rule ID #111701 in /docs/JBossEAP5_Guide.html for more information]</question_text>
 			<instructions><title>Instructions</title>
 				<step><description>Due to space and formatting limitations under the OCIL specification, see the /docs/JBossEAP5_Guide.html for details.</description></step>
 			</instructions>
@@ -2465,7 +2465,7 @@
 		<boolean_question id="ocil:com.redhat.eap5.scap:question:21600101">
 			<question_text>Does a password file exist for the JBoss keystore that is accessible only to JBoss and JBoss administrators??     [Please reference Rule ID #216001 in /docs/JBossEAP5_Guide.html for more information]</question_text>
 			<instructions><title>Instructions</title>
-				<step><description>Review the JBoss security policy file to locate the JBoss keystore password file.  Validate the existance of the file.</description></step>
+				<step><description>Review the JBoss security policy file to locate the JBoss keystore password file.  Validate the existence of the file.</description></step>
 				<step><description>Ensure only the JBoss process owner account and JBoss administrators have READ access to the file.</description></step>
 				<step><description>Ensure the correct password for the JBoss keystore is in the file.</description></step>
 			</instructions>
@@ -2477,7 +2477,7 @@
 			</instructions>
 		</boolean_question>
 		<boolean_question id="ocil:com.redhat.eap5.scap:question:11000101">
-			<question_text>Do deployed production appliations utilize SecurityDomains to protect resources?     [Please reference Rule ID #110001 in /docs/JBossEAP5_Guide.html for more information]</question_text>
+			<question_text>Do deployed production applications utilize SecurityDomains to protect resources?     [Please reference Rule ID #110001 in /docs/JBossEAP5_Guide.html for more information]</question_text>
 			<instructions><title>Instructions</title>
 				<step><description>Due to space and formatting limitations under the OCIL specification, see the /docs/JBossEAP5_Guide.html for details.</description></step>
 			</instructions>
@@ -2598,7 +2598,7 @@
 			</instructions>
 		</boolean_question>
 		<boolean_question id="ocil:com.redhat.eap5.scap:question:40010101">
-			<question_text>Do JBoss installations in a produciton environment reside on dedicated operating systems?    [Please reference Rule ID #400101 in /docs/JBossEAP5_Guide.html for more information]</question_text>
+			<question_text>Do JBoss installations in a production environment reside on dedicated operating systems?    [Please reference Rule ID #400101 in /docs/JBossEAP5_Guide.html for more information]</question_text>
 			<instructions><title>Instructions</title>
 				<step><description>Interview JBoss administrators, review system documentation and architecture diagrams. Review applications hosted by the same operating system as JBoss.</description></step>
 				<step><description>Determine if production environments host JBoss Enterprise Application Platform installations on dedicated operating systems.  JBoss installations should not be hosted by the same operating system that may be hosting other organization resources such as name resolution servers, directory servers, or database servers.</description></step>
diff --git a/RHEL6/README b/RHEL6/README
index 5a5c218..c3c94db 100644
--- a/RHEL6/README
+++ b/RHEL6/README
@@ -25,6 +25,6 @@ The utils directory contains helper scripts and other items that are useful to
 developers but are not essential to producing the project's output.
 
 The dist directory contains final outputs, which could be shipped in an RPM for
-comsumption by end-users.  Updating the Makefile to copy an item from the
+consumption by end-users.  Updating the Makefile to copy an item from the
 outputs directory to the dist directory indicates that an item is considered a
 final output.
diff --git a/RHEL6/input/auxiliary/nist_support.xml b/RHEL6/input/auxiliary/nist_support.xml
index cb293e0..2497c7d 100644
--- a/RHEL6/input/auxiliary/nist_support.xml
+++ b/RHEL6/input/auxiliary/nist_support.xml
@@ -20,7 +20,7 @@ through automated means.</description>
 <Rule id="nist_not_OS_applicable">
 <title>Not Applicable to Operating System</title>
 <rationale>This requirement is not applicable to an operating system.</rational>
-<description>While this requirement is applicable at an information system level, implimentation
+<description>While this requirement is applicable at an information system level, implementation
 is not performed within the Operating System.</rational>
 <ref nist="PM-11,PM-10,PM-9,PM-8,PM-7,PM-6,PM-5,PM-4,PM-3,PM-2,PM-1,AC-17(3),AC-18(a),AC-18(b),AC-18(5),AC-21(1),CP-10(2)" \>
 </Rule>
diff --git a/RHEL6/input/auxiliary/transition_notes.xml b/RHEL6/input/auxiliary/transition_notes.xml
index b4283f3..5eadaa2 100644
--- a/RHEL6/input/auxiliary/transition_notes.xml
+++ b/RHEL6/input/auxiliary/transition_notes.xml
@@ -284,11 +284,11 @@ This is not covered in the RHEL 6 content.
 </note>
 
 <note ref="22374" auth="VP">
-This is covered in the RHEL 6 content in a slightly different mannger.  RHEL 6 admin_space_left_action = ACTION
+This is covered in the RHEL 6 content in a slightly different manner.  RHEL 6 admin_space_left_action = ACTION
 </note>
 
 <note ref="22375" auth="VP">
-This is covered in the RHEL 6 content in a slightly different mannger.  RHEL 6 admin_space_left_action = ACTION
+This is covered in the RHEL 6 content in a slightly different manner.  RHEL 6 admin_space_left_action = ACTION
 </note>
 
 <note ref="22376" auth="VP">
@@ -791,7 +791,7 @@ We are manually inspecting the well-formedness of certain configuration files? W
 </note>
 
 <note ref="793,787,901,902,903,904,905,906,750,924,925,11982" auth="JB">
-This will be superceded by a new section describing expectations for permissions
+This will be superseded by a new section describing expectations for permissions
 contained in certain important directories.
 </note>
 
@@ -801,7 +801,7 @@ depends on the implementation of the underlying device driver.
 </note>
 
 <note ref="22370,22371,22372,22365" auth="JB">
-This is superceded by the system-wide check for improper permissions provided
+This is superseded by the system-wide check for improper permissions provided
 by the package manager. Automating this check became possible with OVAL 5.8.
 </note>
 
@@ -812,7 +812,7 @@ by the package manager. Automating this check became possible with OVAL 5.8.
 22294,22295,22296,22323,22324,22325,22327,22328,22329,22332,22333,22335,
 22336,22337,22342,22343,22392,22394,22396,22398,22406,22423,22425,
 22427,22435,22438,22444,22451,22453,22451,22492,22496,22559,22560,22561" auth="WS">
-This is superceded by the system-wide check for improper permissions provided
+This is superseded by the system-wide check for improper permissions provided
 by the package manager. Automating this check became possible with OVAL 5.8.
 </note>
 
@@ -927,7 +927,7 @@ Also, need to add in architecture specific details e.g. s390x
 Current mapping does not meet requirement as it works for passwords, not keys
 Per Steve Grubb there is a patch coming to enable this through PAM, so we can map to met_inherently in RHEL 6.4
 Put more mappings
-Where reqirement says "must provide.." that is a yes/no. We can map to met_inherently.
+Where requirement says "must provide.." that is a yes/no. We can map to met_inherently.
 Poor CCI that can be restructured -- consider removing
 Perhaps move this to OCIL as interview question
 </note>
@@ -937,7 +937,7 @@ Valid requirement but not applicable to STIG-server.
 </note>
 
 <note ref="765" auth="1augDCM">
-Change check proceedure to check audit logs, not lastlog
+Change check procedure to check audit logs, not lastlog
 </note>
 
 <note ref="769" auth="1augDCM">
@@ -1100,7 +1100,7 @@ Has no cce associated
 </note>
 
 <note ref="850" auth="JB">
-This is superceded by a stronger requirement to not permit remote X sessions.
+This is superseded by a stronger requirement to not permit remote X sessions.
 Also, the RHEL 5 STIG text is wrong anyway.
 </note>
 
@@ -1149,7 +1149,7 @@ rule=null manual=no
 Check does not exist in the RHEL6 prose, it can be automated and the OVAL for
 it does not appear to already exist. 
 rule=null manual=no
-This check should be superceeded by the system-wide check for improper 
+This check should be superseded by the system-wide check for improper 
 permissions provided by the package manager. Automating this check became 
 possible with OVAL 5.8
 </note>
diff --git a/RHEL6/input/checks/audit_rules_dac_modification.xml b/RHEL6/input/checks/audit_rules_dac_modification.xml
index f28bdde..919eaff 100644
--- a/RHEL6/input/checks/audit_rules_dac_modification.xml
+++ b/RHEL6/input/checks/audit_rules_dac_modification.xml
@@ -5,7 +5,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>The changing of file permissios and attributes should be audited.</description>
+      <description>The changing of file permissions and attributes should be audited.</description>
     </metadata>
     <criteria operator="AND">
       <!-- <criterion comment="dac modification chmod" test_ref="test_audit_rules_dac_modification_chmod" /> -->
diff --git a/RHEL6/input/checks/file_permissions_httpd_server_conf_files.xml b/RHEL6/input/checks/file_permissions_httpd_server_conf_files.xml
index ccc6a85..fb74501 100644
--- a/RHEL6/input/checks/file_permissions_httpd_server_conf_files.xml
+++ b/RHEL6/input/checks/file_permissions_httpd_server_conf_files.xml
@@ -6,7 +6,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>The /etc/httpd/conf/* files should have the apropriate permissions.</description>
+      <description>The /etc/httpd/conf/* files should have the appropriate permissions.</description>
     </metadata>
     <criteria>
       <criterion test_ref="test_file_permissions_httpd_server_conf_files" />
diff --git a/RHEL6/input/checks/file_permissions_ldap_server_files.xml b/RHEL6/input/checks/file_permissions_ldap_server_files.xml
index 4f7e863..73423e1 100644
--- a/RHEL6/input/checks/file_permissions_ldap_server_files.xml
+++ b/RHEL6/input/checks/file_permissions_ldap_server_files.xml
@@ -6,7 +6,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>The /var/lib/ldap/* files should have the apropriate permissions.</description>
+      <description>The /var/lib/ldap/* files should have the appropriate permissions.</description>
     </metadata>
     <criteria>
       <criterion test_ref="test_file_permissions_ldap_server_files" />
diff --git a/RHEL6/input/checks/gconf_gnome_screensaver_idle_delay.xml b/RHEL6/input/checks/gconf_gnome_screensaver_idle_delay.xml
index fce7766..4a675a9 100644
--- a/RHEL6/input/checks/gconf_gnome_screensaver_idle_delay.xml
+++ b/RHEL6/input/checks/gconf_gnome_screensaver_idle_delay.xml
@@ -22,5 +22,5 @@
   <ind:xmlfilecontent_state comment="idle timeout" id="state_gnome_screensaver_idle_delay" version="1">
     <ind:value_of datatype="string" operation="equals" var_check="all" var_ref="inactivity_timeout_value" />
   </ind:xmlfilecontent_state>
-  <external_variable comment="inactivity timout variable" datatype="string" id="inactivity_timeout_value" version="1" />
+  <external_variable comment="inactivity timeout variable" datatype="string" id="inactivity_timeout_value" version="1" />
 </def-group>
diff --git a/RHEL6/input/checks/ldap_server_config_bdb_file_security.xml b/RHEL6/input/checks/ldap_server_config_bdb_file_security.xml
index c1d680e..240c57c 100644
--- a/RHEL6/input/checks/ldap_server_config_bdb_file_security.xml
+++ b/RHEL6/input/checks/ldap_server_config_bdb_file_security.xml
@@ -6,7 +6,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>Configuration files should be secured such that anauthorized
+      <description>Configuration files should be secured such that unauthorized
       users cannot access or change them.</description>
     </metadata>
     <criteria comment="Test file user/group ownership and permissions"
diff --git a/RHEL6/input/checks/ldap_server_config_directory_file_security.xml b/RHEL6/input/checks/ldap_server_config_directory_file_security.xml
index e9d86d8..c5b6e8f 100644
--- a/RHEL6/input/checks/ldap_server_config_directory_file_security.xml
+++ b/RHEL6/input/checks/ldap_server_config_directory_file_security.xml
@@ -6,7 +6,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>Directory files should be secured such that anauthorized
+      <description>Directory files should be secured such that unauthorized
       users cannot access or change them.</description>
     </metadata>
     <criteria comment="Test file user/group ownership and permissions"
diff --git a/RHEL6/input/checks/mount_option_dev_shm_noexec.xml b/RHEL6/input/checks/mount_option_dev_shm_noexec.xml
index a28d35c..25ac4fb 100644
--- a/RHEL6/input/checks/mount_option_dev_shm_noexec.xml
+++ b/RHEL6/input/checks/mount_option_dev_shm_noexec.xml
@@ -6,7 +6,7 @@
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
       <description>It can be dangerous to allow the execution of binaries
-      from world-writeable temporary storage directories such as /dev/shm.
+      from world-writable temporary storage directories such as /dev/shm.
       The noexec mount option prevents binaries from being executed out of /dev/shm.</description>
     </metadata>
     <criteria>
diff --git a/RHEL6/input/checks/mount_option_dev_shm_nosuid.xml b/RHEL6/input/checks/mount_option_dev_shm_nosuid.xml
index 0cf8171..e7c517d 100644
--- a/RHEL6/input/checks/mount_option_dev_shm_nosuid.xml
+++ b/RHEL6/input/checks/mount_option_dev_shm_nosuid.xml
@@ -7,7 +7,7 @@
       </affected>
       <description>The nosuid mount option should be set for temporary
       storage partitions such as /dev/shm. The suid/sgid permissions
-      should not be required in these world-writeable directories.</description>
+      should not be required in these world-writable directories.</description>
     </metadata>
     <criteria>
       <criterion comment="nosuid on /dev/shm" test_ref="test_nosuid_dev_shm" />
diff --git a/RHEL6/input/checks/mount_option_tmp_noexec.xml b/RHEL6/input/checks/mount_option_tmp_noexec.xml
index c2c1da0..d0593f8 100644
--- a/RHEL6/input/checks/mount_option_tmp_noexec.xml
+++ b/RHEL6/input/checks/mount_option_tmp_noexec.xml
@@ -6,7 +6,7 @@
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
       <description>It can be dangerous to allow the execution of binaries
-      from world-writeable temporary storage directories such as /tmp.
+      from world-writable temporary storage directories such as /tmp.
       The noexec mount option prevents binaries from being executed out of /tmp.</description>
     </metadata>
     <criteria>
diff --git a/RHEL6/input/checks/mount_option_tmp_nosuid.xml b/RHEL6/input/checks/mount_option_tmp_nosuid.xml
index 37c1f3d..6477a21 100644
--- a/RHEL6/input/checks/mount_option_tmp_nosuid.xml
+++ b/RHEL6/input/checks/mount_option_tmp_nosuid.xml
@@ -7,7 +7,7 @@
       </affected>
       <description>The nosuid mount option should be set for temporary
       storage partitions such as /tmp. The suid/sgid permissions
-      should not be required in these world-writeable directories.</description>
+      should not be required in these world-writable directories.</description>
     </metadata>
     <criteria>
       <criterion comment="nosuid on /tmp" test_ref="test_nosuid_tmp" />
diff --git a/RHEL6/input/checks/postfix_server_mail_relay_smtp_auth_for_untrusted_networks.xml b/RHEL6/input/checks/postfix_server_mail_relay_smtp_auth_for_untrusted_networks.xml
index d3c48e3..bbfeed6 100644
--- a/RHEL6/input/checks/postfix_server_mail_relay_smtp_auth_for_untrusted_networks.xml
+++ b/RHEL6/input/checks/postfix_server_mail_relay_smtp_auth_for_untrusted_networks.xml
@@ -41,7 +41,7 @@
   </ind:textfilecontent54_object>
 
   <ind:textfilecontent54_test check="all" check_existence="all_exist" 
-  comment="Require untrested nets to authenticate for relay" 
+  comment="Require untrusted nets to authenticate for relay" 
   id="test_postfix_server_mail_relay_smtp_auth_for_untrusted_networks_permit_sasl" version="1">
     <ind:object object_ref="obj_postfix_server_mail_relay_smtp_auth_for_untrusted_networks_permit_sasl" />
   </ind:textfilecontent54_test>
diff --git a/RHEL6/input/checks/rpm_verify_hashes.xml b/RHEL6/input/checks/rpm_verify_hashes.xml
index d5c319b..aad9459 100644
--- a/RHEL6/input/checks/rpm_verify_hashes.xml
+++ b/RHEL6/input/checks/rpm_verify_hashes.xml
@@ -15,7 +15,7 @@
   <!-- "bin/" in the path. This essentially narrows our focus down to system executables in directories -->
   <!-- such as /sbin, /usr/bin, and such. After testing I decided that doing it this way was most -->
   <!-- effective at reducing the false positives. If you look at the state below you will notice that I -->
-  <!-- commented out several attributes. The current rpmverify object has methods to distinquish between -->
+  <!-- commented out several attributes. The current rpmverify object has methods to distinguish between -->
   <!-- configuration files, documentation files, etc. Using these discriminators in the state reduced -->
   <!-- the number of false positives, but it did not eliminate them. I left them commented out to serve -->
   <!-- as an example of what they look like. -->
diff --git a/RHEL6/input/checks/sshd_idle_timeout.xml b/RHEL6/input/checks/sshd_idle_timeout.xml
index eef4fb6..984c630 100644
--- a/RHEL6/input/checks/sshd_idle_timeout.xml
+++ b/RHEL6/input/checks/sshd_idle_timeout.xml
@@ -5,7 +5,7 @@
       <affected family="unix">
         <platform>Red Hat Enterprise Linux 6</platform>
       </affected>
-      <description>The SSH idle timout interval should be set to an
+      <description>The SSH idle timeout interval should be set to an
       appropriate value.</description>
     </metadata>
     <criteria comment="sshd service disabled or timeout set" operator="OR">
diff --git a/RHEL6/input/profiles/nist-CL-IL-AL.xml b/RHEL6/input/profiles/nist-CL-IL-AL.xml
index 41476dc..3c5c465 100644
--- a/RHEL6/input/profiles/nist-CL-IL-AL.xml
+++ b/RHEL6/input/profiles/nist-CL-IL-AL.xml
@@ -57,7 +57,7 @@ assurance."</description>
      	organization-defined time period]; locks the account/node until released by an
      	administrator; delays next login prompt according to [Assignment: organization-
      	defined delay algorithm]] when the maximum number of unsuccessful attempts is
-     	exceeded. The control applies regardless of whether the login occures via a
+     	exceeded. The control applies regardless of whether the login occurs via a
      	local or network connection
 
 	The accepted behavior is to issue an "account lock" for an organization-defined
@@ -70,7 +70,7 @@ assurance."</description>
 	                - 100000000	(3.1 years) -->
 <refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="900" \>
 
-<!--	AC-11(a): Prevents furtuer access to the system by initiating a session lock
+<!--	AC-11(a): Prevents further access to the system by initiating a session lock
      	after [Assignment: organization-defined time period] of inactivity or upon
      	receiving a request from a user;
 
@@ -349,7 +349,7 @@ assurance."</description>
 <select idref="disable_dhcp_client" selected="true" \>
 <select idref="disable_avahi" selected="true" \>
 <select idref="enable_cron" selected="true" \>
-<select idref="disable_anacron" seleted="true" \>
+<select idref="disable_anacron" selected="true" \>
 <select idref="disable_at" selected="true" \>
 <select idref="disable_dns_server" selected="true" \>
 <select idref="uninstall_bind" selected="true" \>
diff --git a/RHEL6/input/services/ldap.xml b/RHEL6/input/services/ldap.xml
index a9eadf1..27a0885 100644
--- a/RHEL6/input/services/ldap.xml
+++ b/RHEL6/input/services/ldap.xml
@@ -384,7 +384,7 @@ by connecting to the primary port and issuing the STARTTLS command.
 <title>Configure Logging for LDAP</title>
 <description>
 <ol>
-<li>Add or correct the fillowing line within <tt>/etc/rsyslog.conf</tt>:
+<li>Add or correct the following line within <tt>/etc/rsyslog.conf</tt>:
 <pre>local4.*</pre>
 </li>
 <li>Create the log file with safe permissions:
diff --git a/RHEL6/input/system/permissions/files.xml b/RHEL6/input/system/permissions/files.xml
index 2d05ef2..dede520 100644
--- a/RHEL6/input/system/permissions/files.xml
+++ b/RHEL6/input/system/permissions/files.xml
@@ -195,7 +195,7 @@ by default:
 Kernel modules, which can be added to the kernel during runtime, are
 stored in <tt>/lib/modules</tt>. All files in these directories
 should not be group-writable or world-writable. If any file in these
-directories is found to be group-writable or world-writeable, correct
+directories is found to be group-writable or world-writable, correct
 its permission with the following command:
 <pre># chmod go-w <i>FILE</i></pre>
 </description>
@@ -254,7 +254,7 @@ System executables are stored in the following directories by default:
 /usr/local/sbin</pre>
 All files in these directories should not be group-writable or world-writable.
 If any file <i>FILE</i> in these directories is found
-to be group-writable or world-writeable, correct its permission with the
+to be group-writable or world-writable, correct its permission with the
 following command:
 <pre># chmod go-w <i>FILE</i></pre>
 </description>
diff --git a/RHEL6/input/system/permissions/partitions.xml b/RHEL6/input/system/permissions/partitions.xml
index c686c0c..6b476cd 100644
--- a/RHEL6/input/system/permissions/partitions.xml
+++ b/RHEL6/input/system/permissions/partitions.xml
@@ -114,7 +114,7 @@ located on the root partition. The only exception to this is chroot jails.</rati
 from being executed out of <tt>/tmp</tt>.
 <mount-desc-macro option="noexec" part="/tmp" />
 </description>
-<rationale>Allowing users to execute binaries from world-writeable directories
+<rationale>Allowing users to execute binaries from world-writable directories
 such as <tt>/tmp</tt> should never be necessary in normal operation and
 can expose the system to potential compromise.</rationale>
 <ident cce="26720-3" />
@@ -126,7 +126,7 @@ can expose the system to potential compromise.</rationale>
 <title>Add nosuid Option to /tmp</title>
 <description>The <tt>nosuid</tt> mount option can be used to prevent
 execution of setuid programs in <tt>/tmp</tt>. The suid/sgid permissions
-should not be required in these world-writeable directories.
+should not be required in these world-writable directories.
 <mount-desc-macro option="nosuid" part="/tmp" />
 </description>
 <rationale>The presence of suid and sgid executables should be tightly controlled. Users
@@ -156,10 +156,10 @@ located on the root partition. The only exception to this is chroot jails.</rati
 <description>The <tt>noexec</tt> mount option can be used to prevent binaries
 from being executed out of <tt>/dev/shm</tt>.
 It can be dangerous to allow the execution of binaries
-from world-writeable temporary storage directories such as <tt>/dev/shm</tt>.
+from world-writable temporary storage directories such as <tt>/dev/shm</tt>.
 <mount-desc-macro option="noexec" part="/dev/shm" />
 </description>
-<rationale>Allowing users to execute binaries from world-writeable directories
+<rationale>Allowing users to execute binaries from world-writable directories
 such as /dev/shm can expose the system to potential compromise.</rationale>
 <ident cce="26622-1" />
 <oval id="mount_option_dev_shm_noexec" />
@@ -170,7 +170,7 @@ such as /dev/shm can expose the system to potential compromise.</rationale>
 <title>Add nosuid Option to /dev/shm</title>
 <description>The <tt>nosuid</tt> mount option can be used to prevent execution
 of setuid programs in <tt>/dev/shm</tt>.  The suid/sgid permissions should not
-be required in these world-writeable directories.
+be required in these world-writable directories.
 <mount-desc-macro option="nosuid" part="/dev/shm" />
 </description>
 <rationale>The presence of suid and sgid executables should be tightly controlled. Users
diff --git a/RHEL6/input/system/software/updating.xml b/RHEL6/input/system/software/updating.xml
index 09513c5..663faef 100644
--- a/RHEL6/input/system/software/updating.xml
+++ b/RHEL6/input/system/software/updating.xml
@@ -9,7 +9,7 @@ that are already installed. In the <b>Applications</b> menu, <tt>pirut</tt>
 is labeled <b>Add/Remove Software</b> and pup is labeled
 <b>Software Updater</b>.
 <br /><br />
-Red Hat Enteprise Linux systems contain an embedded Installed Software
+Red Hat Enterprise Linux systems contain an embedded Installed Software
 Catalog, or "RPM Database," which records metadata of installed packages.
 The <tt>yum</tt>, <tt>pirut</tt>, and <tt>pup</tt> tools interface
 with the Installed Software Catalog to ensure all system metadata is
diff --git a/RHEL6/references/cce-rhel5.xml b/RHEL6/references/cce-rhel5.xml
index 0716f75..245492a 100644
--- a/RHEL6/references/cce-rhel5.xml
+++ b/RHEL6/references/cce-rhel5.xml
@@ -2360,7 +2360,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-3845-5" platform="rhel5" modified="2011-10-07">
-      <description>The SSH idle timout interval should be set to an appropriate value</description>
+      <description>The SSH idle timeout interval should be set to an appropriate value</description>
       <parameters>
         <parameter>integer (seconds)</parameter>
       </parameters>
@@ -2456,7 +2456,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-4303-4" platform="rhel5" modified="2011-10-07">
-      <description>DEPRECTATED in favor of CCE-4448-7</description>
+      <description>DEPRECATED in favor of CCE-4448-7</description>
       <parameters/>
       <technical_mechanisms/>
       <references>
@@ -4344,7 +4344,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14089-7" platform="rhel5" modified="2011-10-07">
-      <description>Support for cramfs filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for cramfs filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4358,7 +4358,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14457-6" platform="rhel5" modified="2011-10-07">
-      <description>Support for freevxfs filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for freevxfs filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4372,7 +4372,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-15087-0" platform="rhel5" modified="2011-10-07">
-      <description>Support for hfs filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for hfs filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4386,7 +4386,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14093-9" platform="rhel5" modified="2011-10-07">
-      <description>Support for hfsplus filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for hfsplus filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4400,7 +4400,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14853-6" platform="rhel5" modified="2011-10-07">
-      <description>Support for jffs2 filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for jffs2 filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4414,7 +4414,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14118-4" platform="rhel5" modified="2011-10-07">
-      <description>Support for squashfs filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for squashfs filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
@@ -4428,7 +4428,7 @@
       </references>
     </cce>
     <cce cce_id="CCE-14871-8" platform="rhel5" modified="2011-10-07">
-      <description>Support for udf filesystems should be enabeld or disabled as appropriate.</description>
+      <description>Support for udf filesystems should be enabled or disabled as appropriate.</description>
       <parameters>
         <parameter>enabled / disabled</parameter>
       </parameters>
diff --git a/RHEL6/references/disa-cci-list.xml b/RHEL6/references/disa-cci-list.xml
index c86a8bc..7111eec 100644
--- a/RHEL6/references/disa-cci-list.xml
+++ b/RHEL6/references/disa-cci-list.xml
@@ -1032,7 +1032,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization manages informaiton system accounts by defining the frequency of information system account reviews.</definition>
+			<definition>The organization manages information system accounts by defining the frequency of information system account reviews.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AC-2 j"/>
@@ -2303,7 +2303,7 @@
 			<status>draft</status>
 			<publishdate>2009-05-19</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization documents the rationale for authorized network access toorganization-defined privileged commands in the security plan for the information system.</definition>
+			<definition>The organization documents the rationale for authorized network access to organization-defined privileged commands in the security plan for the information system.</definition>
 			<type>policy</type>
 			<note>The organization employs the concept of least privilege, limiting authorized access for users (and processes acting on behalf of users) as necessary, to accomplish assigned tasks.</note>
 			<references>
@@ -2458,7 +2458,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-22</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organziation defines the number of consecutive, unsuccessful login attempts to the mobile device.</definition>
+			<definition>The organization defines the number of consecutive, unsuccessful login attempts to the mobile device.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AC-7 (2)"/>
@@ -2678,7 +2678,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the frequency of security awareness and traning policy reviews/updates.</definition>
+			<definition>The organization defines the frequency of security awareness and training policy reviews/updates.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AT-1 a"/>
@@ -3174,7 +3174,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The information system produces a system-wide (logical or physical) audit trail of informaiton system audit records.</definition>
+			<definition>The information system produces a system-wide (logical or physical) audit trail of information system audit records.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AU-12 (1)"/>
@@ -3328,7 +3328,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the list of informatio nsystem auditable events.</definition>
+			<definition>The organization defines the list of information nsystem auditable events.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AU-2 a"/>
@@ -4153,7 +4153,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-15</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates formal, documented security assessment and authorization procedures to elements within the organization having associated security assessment and authorization roles and responsibilities.</definition>
+			<definition>The organization disseminates formal, documented security assessment and authorization procedures to elements within the organization having associated security assessment and authorization roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CA-1 b"/>
@@ -4318,7 +4318,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organziation identifies connections to external information systems (i.e., information systems outside of the authorization boundary).</definition>
+			<definition>The organization identifies connections to external information systems (i.e., information systems outside of the authorization boundary).</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CA-3 b"/>
@@ -4527,7 +4527,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-11</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organizatoin defines the forms of security testing (e.g., in depth monitoring, malicious user testing, penetration testing, red team exercises) to be inlcuded in planning, scheduling, and conducting assessments to ensure compliance with all vulnerability mitigation procedures.</definition>
+			<definition>The organization defines the forms of security testing (e.g., in depth monitoring, malicious user testing, penetration testing, red team exercises) to be inlcuded in planning, scheduling, and conducting assessments to ensure compliance with all vulnerability mitigation procedures.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CA-7 (2)"/>
@@ -4714,7 +4714,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates a formal, documented configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.</definition>
+			<definition>The organization disseminates a formal, documented configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CM-1.1 (iii)"/>
@@ -4747,7 +4747,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates formal, documented procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.</definition>
+			<definition>The organization disseminates formal, documented procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CM-1.1 (vi)"/>
@@ -6563,7 +6563,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization disseminates a formal, documente contingency planning procedure to elements within the organization having associated contingency planning roles and responsibilities.</definition>
+			<definition>The organization disseminates a formal, documented contingency planning procedure to elements within the organization having associated contingency planning roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-1"/>
@@ -6607,7 +6607,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-18</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates a formal, documented contingency planning policy to elements within the organization having associated contingency planning roles and responsibilities.</definition>
+			<definition>The organization disseminates a formal, documented contingency planning policy to elements within the organization having associated contingency planning roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-1.1 (iii)"/>
@@ -6640,7 +6640,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization provides automated mechanicsms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a disruption.</definition>
+			<definition>The organization provides automated mechanisms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a disruption.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-10"/>
@@ -6651,7 +6651,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization provides fautomated mechanicsms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a compromise.</definition>
+			<definition>The organization provides fautomated mechanisms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a compromise.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-10"/>
@@ -6662,7 +6662,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization provides automated mechanicsms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a failure.</definition>
+			<definition>The organization provides automated mechanisms and/or manual procedures for the recovery and reconstitution of the information system to a known state after a failure.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-10"/>
@@ -6684,7 +6684,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines in the security plan, explicitly or by reference, the circumstatnces that can inhibit recovery and reconstitution of the information system to a known state.</definition>
+			<definition>The organization defines in the security plan, explicitly or by reference, the circumstances that can inhibit recovery and reconstitution of the information system to a known state.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-10 (3)"/>
@@ -6783,7 +6783,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization sustains operational continuity of essential missions until full informatin system restoration at primary processing and/or storage sites.</definition>
+			<definition>The organization sustains operational continuity of essential missions until full information system restoration at primary processing and/or storage sites.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-2 (5)"/>
@@ -6794,7 +6794,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization sustains operaitonal continuity of business functions until full information system restoration at primary processing and/or storage sites.</definition>
+			<definition>The organization sustains operational continuity of business functions until full information system restoration at primary processing and/or storage sites.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-2 (5)"/>
@@ -6992,7 +6992,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-18</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines a list of key contingency personnel (identified by name and/or by role) and organizational elements desginated to receive copies of the contigency plan.</definition>
+			<definition>The organization defines a list of key contingency personnel (identified by name and/or by role) and organizational elements designated to receive copies of the contingency plan.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-2.1 (ii)"/>
@@ -7213,7 +7213,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-18</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization plans for the full resumption of affected missions within organzation-defined time period of contigency plan activation.</definition>
+			<definition>The organization plans for the full resumption of affected missions within organization-defined time period of contingency plan activation.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-2 (4).1 (ii)"/>
@@ -7378,7 +7378,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization tests the contingency plan using the organization-defined tests in accordance with organziation-defined frequency.</definition>
+			<definition>The organization tests the contingency plan using the organization-defined tests in accordance with organization-defined frequency.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-4.1 (iii)"/>
@@ -7389,7 +7389,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization exercises the contingency plan using organization-defined exercises in accordance with organziation-defined frequency.</definition>
+			<definition>The organization exercises the contingency plan using organization-defined exercises in accordance with organization-defined frequency.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-4.1 (iii)"/>
@@ -7609,7 +7609,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organiztion defines the time period for achieving the recovery time objectives for business functions within which processing must be resumed at the atlernate processing site.</definition>
+			<definition>The organization defines the time period for achieving the recovery time objectives for business functions within which processing must be resumed at the alternate processing site.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-7"/>
@@ -8038,7 +8038,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines time period and transferring information system backup information to the atlernate storage site to support recovery time objectives and recovery point objectives.</definition>
+			<definition>The organization defines time period and transferring information system backup information to the alternate storage site to support recovery time objectives and recovery point objectives.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="CP-9 (5)"/>
@@ -8082,7 +8082,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissemenates a formal, documented identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.</definition>
+			<definition>The organization disseminates a formal, documented identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IA-1 a"/>
@@ -8104,7 +8104,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines a freqency for reviewing/updating  the formal, documented identification and authentication policy.</definition>
+			<definition>The organization defines a frequency for reviewing/updating  the formal, documented identification and authentication policy.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IA-1 a"/>
@@ -8126,7 +8126,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissemenates formal, documented procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.</definition>
+			<definition>The organization disseminates formal, documented procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IA-1 b"/>
@@ -8148,7 +8148,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines a freqency for reviewing/updating the formal, documented procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.</definition>
+			<definition>The organization defines a frequency for reviewing/updating the formal, documented procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IA-1 b"/>
@@ -8368,7 +8368,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-17</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization audits DHCP lease information Iincluding IP addresses) when assigned to a device.</definition>
+			<definition>The organization audits DHCP lease information including IP addresses) when assigned to a device.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IA-3 (3).1 (ii)"/>
@@ -9596,7 +9596,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-18</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization develops an incident response plan that provides the organization with a roadmap for implementing its incident response capability, describes the structure and organization of the incident response capability, provides a high-level approach for how the incident response capability fits into the overall organziation , meets the unique requirements of the organizationk, which relate to mission, size, structure, and functions, defines reportable incidents, provides metrics for measuring the incident response capability within the organization and defines the resources and management support needed to effectively maintain and mature an incident response capability.</definition>
+			<definition>The organization develops an incident response plan that provides the organization with a roadmap for implementing its incident response capability, describes the structure and organization of the incident response capability, provides a high-level approach for how the incident response capability fits into the overall organization , meets the unique requirements of the organization, which relate to mission, size, structure, and functions, defines reportable incidents, provides metrics for measuring the incident response capability within the organization and defines the resources and management support needed to effectively maintain and mature an incident response capability.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="IR-8.1"/>
@@ -10124,7 +10124,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-18</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines personel to be notified when non-local maintenance is planned (i.e., date/time).</definition>
+			<definition>The organization defines personnel to be notified when non-local maintenance is planned (i.e., date/time).</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="MA-4 (5).1 (ii)"/>
@@ -10872,7 +10872,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines a frequencyof physical and environmental protection procedure reviews/updates.</definition>
+			<definition>The organization defines a frequency of physical and environmental protection procedure reviews/updates.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PE-1.2 (iii)"/>
@@ -11367,7 +11367,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the frequency to review and approve the physical access list and uathorization credentials for the facility.</definition>
+			<definition>The organization defines the frequency to review and approve the physical access list and authorization credentials for the facility.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PE-2.2 (i)"/>
@@ -11477,7 +11477,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the frequency for conducting invenotires of physical access devices.</definition>
+			<definition>The organization defines the frequency for conducting inventories of physical access devices.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PE-3.2 (i)"/>
@@ -11862,7 +11862,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates a formal, documented security planning policy to elements within the organization having associated security planning roles and responsibilities.</definition>
+			<definition>The organization disseminates a formal, documented security planning policy to elements within the organization having associated security planning roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PL-1 a"/>
@@ -11917,7 +11917,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization develops a security plan for the information system that is consistent with the organization?s enterprise architecture; explicitly defines the authorization boundary for the system; describes the operational context of the information system in terms of mission and business processes; provides the security category and impact level of the information system including supporting rationale; describes the operational environment for the information system; describes relationships with or connections to other information systems; provides an overview of the security requirements for the system; describes the security controls in place or planned for meeting those reuqirements including a rationale for the tailoring and supplemental decisions.</definition>
+			<definition>The organization develops a security plan for the information system that is consistent with the organization?s enterprise architecture; explicitly defines the authorization boundary for the system; describes the operational context of the information system in terms of mission and business processes; provides the security category and impact level of the information system including supporting rationale; describes the operational environment for the information system; describes relationships with or connections to other information systems; provides an overview of the security requirements for the system; describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplemental decisions.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PL-2 a"/>
@@ -12533,7 +12533,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organizaiton updates the critical infrastructure and key resource protection plan.</definition>
+			<definition>The organization updates the critical infrastructure and key resource protection plan.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PM-8"/>
@@ -12621,7 +12621,7 @@
 			<status>draft</status>
 			<publishdate>2009-11-02</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the frequency of the personnel securiy procedure reviews/updates.</definition>
+			<definition>The organization defines the frequency of the personnel security procedure reviews/updates.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="PS-1 b"/>
@@ -13138,7 +13138,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization conducts an assessment of risk of the information system and the information it processes, stores, or transmits that includes the likelihood and magnitue of harm from the unauthorized access, use, disclosure, disruption, modification, or destruction.</definition>
+			<definition>The organization conducts an assessment of risk of the information system and the information it processes, stores, or transmits that includes the likelihood and magnitude of harm from the unauthorized access, use, disclosure, disruption, modification, or destruction.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="RA-3.1 (i)"/>
@@ -13226,7 +13226,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization employes vulnerability scanning procedures that can demonstrate the depth of coverage (i.e. vulnerabilities checked).</definition>
+			<definition>The organization employs vulnerability scanning procedures that can demonstrate the depth of coverage (i.e. vulnerabilities checked).</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="RA-5 (3)"/>
@@ -13490,7 +13490,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates a formal, documented system services and acquisition policy to elements within the organization having associated system services and acquisition roles and responsibilities.</definition>
+			<definition>The organization disseminates a formal, documented system services and acquisition policy to elements within the organization having associated system services and acquisition roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-1 a"/>
@@ -13523,7 +13523,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization dissiminates formal, documented system services and acquisition procedures to elements within the organization having associated system services and acquisition roles and responsibilities.</definition>
+			<definition>The organization disseminates formal, documented system services and acquisition procedures to elements within the organization having associated system services and acquisition roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-1 b"/>
@@ -14755,7 +14755,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization obtains administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintaenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.</definition>
+			<definition>The organization obtains administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-5 a"/>
@@ -14766,7 +14766,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization protects as required administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintaenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.</definition>
+			<definition>The organization protects as required administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-5 a"/>
@@ -14799,7 +14799,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization  protects as required user documentation for the information system that describes user-accessible security features/functions and how to effectively use those security features/functions; methods for user interaction with the information system, which enables individuals to use the system in a more secure manner; and user responsibilities in maitaining the security of the information and information system.</definition>
+			<definition>The organization  protects as required user documentation for the information system that describes user-accessible security features/functions and how to effectively use those security features/functions; methods for user interaction with the information system, which enables individuals to use the system in a more secure manner; and user responsibilities in maintaining the security of the information and information system.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-5 a"/>
@@ -15008,7 +15008,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization provides exceptions to the source code requirement only when no alternative solutions are available to support compelling mission/oeprational requirements.</definition>
+			<definition>The organization provides exceptions to the source code requirement only when no alternative solutions are available to support compelling mission/operational requirements.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SA-6 (1) (b)"/>
@@ -15261,7 +15261,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization disseminates a formal, documented system and communications protection policy to elements within the organizatin having associated system and communications protection roles and responsibilities.</definition>
+			<definition>The organization disseminates a formal, documented system and communications protection policy to elements within the organization having associated system and communications protection roles and responsibilities.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SC-1.1 (iii)"/>
@@ -15360,7 +15360,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the security functions within the information system to be included in a trusted communciations path.</definition>
+			<definition>The organization defines the security functions within the information system to be included in a trusted communications path.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SC-11.1"/>
@@ -15690,7 +15690,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organizaiton controls the use of mobile code within the information system.</definition>
+			<definition>The organization controls the use of mobile code within the information system.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SC-18.1 (iii)"/>
@@ -16394,7 +16394,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization employs organization-defined information system components with no writeable storage that are persistent across component restart or power on/off.</definition>
+			<definition>The organization employs organization-defined information system components with no writable storage that are persistent across component restart or power on/off.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SC-34 (1).1 (ii)"/>
@@ -16405,7 +16405,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-21</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization defines the information system components to be employed with no writeable storage..</definition>
+			<definition>The organization defines the information system components to be employed with no writable storage..</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SC-34 (1).1 (i)"/>
@@ -16966,7 +16966,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-22</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization reviews/updates system and information integrity policy in accordance with origanization-defined frequency.</definition>
+			<definition>The organization reviews/updates system and information integrity policy in accordance with organization-defined frequency.</definition>
 			<type>policy</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SI-1 a"/>
@@ -17439,7 +17439,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization employs malicious code protection mechanicsms at workstations, servers, or mobile computing devices on the network to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted through the exploitation of information system vulnerabilities.</definition>
+			<definition>The organization employs malicious code protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted through the exploitation of information system vulnerabilities.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SI-3 a"/>
@@ -17461,7 +17461,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-22</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted trhough the exploitation of information system vulnerabilities.</definition>
+			<definition>The organization employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted through the exploitation of information system vulnerabilities.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SI-3 a"/>
@@ -17615,7 +17615,7 @@
 			<status>draft</status>
 			<publishdate>2010-05-12</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization analyses outbound communciations traffic at selected interior points within the system (e.g., subnets, subsystems), as deemed necessary, to discover anomalies.</definition>
+			<definition>The organization analyses outbound communications traffic at selected interior points within the system (e.g., subnets, subsystems), as deemed necessary, to discover anomalies.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SI-4 (11)"/>
@@ -18275,7 +18275,7 @@
 			<status>draft</status>
 			<publishdate>2009-09-22</publishdate>
 			<contributor>DISA FSO</contributor>
-			<definition>The organization employs malicious code protection mechanicsms at information system entry and exit points to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means.</definition>
+			<definition>The organization employs malicious code protection mechanisms at information system entry and exit points to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means.</definition>
 			<type>technical</type>
 			<references>
 				<reference creator="NIST" title="NIST SP 800-53" version="3" location="http://csrc.nist.gov/publications/PubsSPs.html" index="SI-8 a"/>
diff --git a/RHEL6/references/disa-os-srg-v1r1.xml b/RHEL6/references/disa-os-srg-v1r1.xml
index 8c7868e..c9ef9aa 100644
--- a/RHEL6/references/disa-os-srg-v1r1.xml
+++ b/RHEL6/references/disa-os-srg-v1r1.xml
@@ -5421,9 +5421,9 @@ For this requirement, the operating environment is the operating system.&lt;/Vul
 		<description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
 		<Rule id="SV-37020r1_rule" severity="medium" weight="10.0">
 			<version>SRG-OS-000189</version>
-			<title>The operating system must employ organization-defined information system components with no writeable storage that are persistent across component restart or power on/off.
+			<title>The operating system must employ organization-defined information system components with no writable storage that are persistent across component restart or power on/off.
 </title>
-			<description>&lt;VulnDiscussion&gt;Organizations may require operating systems to be non-modifiable or to be stored and executed on non-writeable storage. Use of non-modifiable storage ensures the integrity of the program from the point of creation of the read-only image and eliminates the possibility of malicious code insertion.
+			<description>&lt;VulnDiscussion&gt;Organizations may require operating systems to be non-modifiable or to be stored and executed on non-writable storage. Use of non-modifiable storage ensures the integrity of the program from the point of creation of the read-only image and eliminates the possibility of malicious code insertion.
 &lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
 			<ident system="http://iase.disa.mil/cci">CCI-001214</ident>
 		</Rule>
diff --git a/RHEL6/references/disa-stig-rhel5-v1r0.6-oval.xml b/RHEL6/references/disa-stig-rhel5-v1r0.6-oval.xml
index 2c336a6..63194fa 100644
--- a/RHEL6/references/disa-stig-rhel5-v1r0.6-oval.xml
+++ b/RHEL6/references/disa-stig-rhel5-v1r0.6-oval.xml
@@ -758,7 +758,7 @@
     </definition>
     <definition id="oval:mil.disa.fso.rhel:def:179" version="3" class="compliance">
       <metadata>
-        <title>The audit system must aleart the SA when the audit storage volume approaches its capacity.</title>
+        <title>The audit system must alert the SA when the audit storage volume approaches its capacity.</title>
         <affected family="unix">
           <platform>Red Hat Enterprise Linux 5</platform>
         </affected>
@@ -3987,7 +3987,7 @@ An acceptable method of disabling 'ldd' is changing its mode to 0000. The SA may
         <affected family="unix">
           <platform>Red Hat Enterprise Linux 5</platform>
         </affected>
-        <description>Systems must employ crptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes that are more vulnerable to compromise.</description>
+        <description>Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes that are more vulnerable to compromise.</description>
       </metadata>
       <criteria operator="AND" negate="false" comment="The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm">
         <criterion comment="The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm" test_ref="oval:mil.disa.fso.rhel:tst:5900" negate="false" />
@@ -6492,10 +6492,10 @@ An acceptable method of disabling 'ldd' is changing its mode to 0000. The SA may
     <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.fso.rhel:tst:39902" version="16" check="all" comment="mail.debug logging test" check_existence="at_least_one_exists">
       <object object_ref="oval:mil.disa.fso.rhel:obj:39902" />
     </textfilecontent54_test>
-    <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.fso.rhel:tst:40000" version="2" check="all" comment="test for host.deny existance and content" check_existence="at_least_one_exists">
+    <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.fso.rhel:tst:40000" version="2" check="all" comment="test for host.deny existence and content" check_existence="at_least_one_exists">
       <object object_ref="oval:mil.disa.fso.rhel:obj:40000" />
     </textfilecontent54_test>
-    <file_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" id="oval:mil.disa.fso.rhel:tst:40001" version="2" check="all" comment="test for host.allow existance" check_existence="at_least_one_exists">
+    <file_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" id="oval:mil.disa.fso.rhel:tst:40001" version="2" check="all" comment="test for host.allow existence" check_existence="at_least_one_exists">
       <object object_ref="oval:mil.disa.fso.rhel:obj:40001" />
     </file_test>
     <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.fso.rhel:tst:40500" version="1" check="all" comment="appletalk not in /etc/modprobe.conf" check_existence="none_exist">
@@ -7362,7 +7362,7 @@ An acceptable method of disabling 'ldd' is changing its mode to 0000. The SA may
       <ind-def:object object_ref="oval:mil.disa.fso.rhel:obj:6300" />
       <ind-def:state state_ref="oval:mil.disa.fso.rhel:ste:6300" />
     </ind-def:textfilecontent54_test>
-    <unix-def:file_test check_existence="any_exist" id="oval:mil.disa.fso.rhel:tst:11500" version="1" check="all" comment="home directories are group writeable">
+    <unix-def:file_test check_existence="any_exist" id="oval:mil.disa.fso.rhel:tst:11500" version="1" check="all" comment="home directories are group writable">
       <unix-def:object object_ref="oval:mil.disa.fso.rhel:obj:11500" />
       <unix-def:state state_ref="oval:mil.disa.fso.rhel:ste:11500" />
     </unix-def:file_test>
@@ -7436,7 +7436,7 @@ An acceptable method of disabling 'ldd' is changing its mode to 0000. The SA may
       <ind-def:object object_ref="oval:mil.disa.fso.rhel:obj:7900" />
       <ind-def:state state_ref="oval:mil.disa.fso.rhel:ste:7900" />
     </ind-def:textfilecontent54_test>
-    <lin-def:rpminfo_test xmlns:lin-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" check_existence="all_exist" id="oval:mil.disa.fso.rhel:tst:3200" version="1" check="all" comment="check for redhat 5">
+    <lin-def:rpminfo_test xmlns:lin-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" check_existence="all_exist" id="oval:mil.disa.fso.rhel:tst:3200" version="1" check="all" comment="check for RHEL 5">
       <lin-def:object object_ref="oval:mil.disa.fso.rhel:obj:3200" />
       <lin-def:state state_ref="oval:mil.disa.fso.rhel:ste:3200" />
     </lin-def:rpminfo_test>
@@ -15844,7 +15844,7 @@ An acceptable method of disabling 'ldd' is changing its mode to 0000. The SA may
     </constant_variable>
     <external_variable id="oval:mil.disa.fso.rhel:var:6500" version="1" datatype="string" comment="External variable for definition 20073" />
     <external_variable id="oval:mil.disa.fso.rhel:var:5800" version="1" datatype="string" comment="External variable for definition 20083 Password hashing algorithm" />
-    <external_variable id="oval:mil.disa.fso.rhel:var:5200" version="1" datatype="string" comment="External variable for definitions 20098 20100 Inactivity timout" />
+    <external_variable id="oval:mil.disa.fso.rhel:var:5200" version="1" datatype="string" comment="External variable for definitions 20098 20100 Inactivity timeout" />
     <external_variable id="oval:mil.army.us.rhel5:var:20083" version="1" datatype="string" comment="External variable for definition 20083 Password hashing algorithm" />
     <external_variable id="oval:mil.army.us.rhel5:var:20084" version="1" datatype="int" comment="External variable for definition 20084 number of passwords to remember" />
     <local_variable id="oval:mil.disa.fso.rhel:var:6300" version="1" datatype="string" comment="ocredit pattern">
diff --git a/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf-manual.xml b/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf-manual.xml
index 4a0b8a4..edf5c54 100644
--- a/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf-manual.xml
+++ b/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf-manual.xml
@@ -5769,7 +5769,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <fix id="F-31220r1_fix" />
       <check system="C-35964r1_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
-        <check-content>Perform the following to check NIS file premissions. # ls -la /var/yp/*; If the file's mode is more permissive than 0755, this is a finding.</check-content>
+        <check-content>Perform the following to check NIS file permissions. # ls -la /var/yp/*; If the file's mode is more permissive than 0755, this is a finding.</check-content>
       </check>
     </Rule>
   </Group>
@@ -7353,8 +7353,8 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <check system="C-402r6_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
         <check-content>Check the permissions on the files or scripts executed from system startup scripts to see if they are world-writable. Create a list of all potential run command level scripts. ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut
-        -f 9,9 -d " " Create a list of world writeable files. # find / -perm -002 -type f &gt;&gt; worldWriteableFileList Determine if any of the world writeable files in worldWriteableFileList are called from the run command level scripts. Note:
-        Depending upon the number of scripts vs world writeable files, it may be easier to inspect the scripts manually. # more `ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d "` If any system startup script executes any file or script
+        -f 9,9 -d " " Create a list of world writable files. # find / -perm -002 -type f &gt;&gt; worldWriteableFileList Determine if any of the world writable files in worldWriteableFileList are called from the run command level scripts. Note:
+        Depending upon the number of scripts vs world writable files, it may be easier to inspect the scripts manually. # more `ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d "` If any system startup script executes any file or script
         that is world-writable, this is a finding.</check-content>
       </check>
     </Rule>
@@ -9321,7 +9321,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <check system="C-37221r1_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
         <check-content>Check /boot/grub/grub.conf permissions: # ls -lL /boot/grub/grub.conf If /boot/grub/grub.conf has a mode more permissive than 0600, then this is a finding. For any bootloader other than GRUB which has been authorized, justified and
-        documented for use on the system refer to the vendor documentation for the locatioin of the configuration file. If the bootloader configuration file has a mode more permissive than 0600, this is a finding.</check-content>
+        documented for use on the system refer to the vendor documentation for the location of the configuration file. If the bootloader configuration file has a mode more permissive than 0600, this is a finding.</check-content>
       </check>
     </Rule>
   </Group>
@@ -10620,8 +10620,8 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <fix id="F-31417r1_fix" />
       <check system="C-36166r1_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
-        <check-content>Determine the version of the SMTP service software. Procedure: #rpm -q sendmail RedHat sendmail 8.13.8-8 is the latest required version. If the RedHat sendmail is installed and the version is not at least 8.13.8-8, this is a
-        finding. #rpm -q postfix RedHat postfix-2.5.1-0.4.rhel5 is the latest required version. If the postfix is installed and the version is not at least 2-5.1-0.4, this is a finding.</check-content>
+        <check-content>Determine the version of the SMTP service software. Procedure: #rpm -q sendmail Red Hat sendmail 8.13.8-8 is the latest required version. If the Red Hat sendmail is installed and the version is not at least 8.13.8-8, this is a
+        finding. #rpm -q postfix Red Hat postfix-2.5.1-0.4.rhel5 is the latest required version. If the postfix is installed and the version is not at least 2-5.1-0.4, this is a finding.</check-content>
       </check>
     </Rule>
   </Group>
@@ -10754,13 +10754,13 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
         <dc:identifier>2154</dc:identifier>
       </reference>
       <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-31423r1_fix">If the WIZ command exists on sendmail then the version of sendmail is archaic and should be replaced with the latest version from RedHat. WIZ is not available on any sendmail distrubution of RHEL. However,If the WIZ
+      <fixtext fixref="F-31423r1_fix">If the WIZ command exists on sendmail then the version of sendmail is archaic and should be replaced with the latest version from Red Hat. WIZ is not available on any sendmail distribution of RHEL. However,If the WIZ
       command is enabled on sendmail, it should be disabled by adding this line to the sendmail.cf configuration file (note that it must be typed in uppercase): OW* For the change to take effect, kill the sendmail process, refreeze the sendmail.cf file,
       and restart the sendmail process.</fixtext>
       <fix id="F-31423r1_fix" />
       <check system="C-36172r1_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
-        <check-content>Log into the sendmail server with telnet and test the "wiz" commmand" Procedure: # telnet localhost 25 Trying 127.0.0.1... Connected to locahost.localdomain (127.0.0.1). Escape character ... Once the telnet greeting is complete
+        <check-content>Log into the sendmail server with telnet and test the "wiz" command" Procedure: # telnet localhost 25 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character ... Once the telnet greeting is complete
         type: wiz If you do not get a "Command unrecognized: " message, this is a finding.</check-content>
       </check>
     </Rule>
@@ -11387,7 +11387,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
         <dc:identifier>2154</dc:identifier>
       </reference>
       <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-31242r1_fix">Edit the local initialization file and remove the relative path entry from the executable search path variable. If this is not feasable, justify and document the necessity of having the relative path for a specific
+      <fixtext fixref="F-31242r1_fix">Edit the local initialization file and remove the relative path entry from the executable search path variable. If this is not feasible, justify and document the necessity of having the relative path for a specific
       application.</fixtext>
       <fix id="F-31242r1_fix" />
       <check system="C-35985r1_chk">
@@ -12339,7 +12339,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <version>GEN000241</version>
       <title>The system clock must be synchronized continuously, or at least daily.</title>
       <description>&lt;VulnDiscussion&gt;A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. Internal system clocks tend to drift and require periodic
-      resynchronization to ensure their accuracy. Software, such as ntpd, can be used to continuously synchronize the system clock with authoritative sources. Alternatively, the system may be synchronized periodically, with a maximum of one day between
+      re-synchronization to ensure their accuracy. Software, such as ntpd, can be used to continuously synchronize the system clock with authoritative sources. Alternatively, the system may be synchronized periodically, with a maximum of one day between
       synchronizations. If the system is completely isolated (i.e., it has no connections to networks or other systems), time synchronization is not required as no correlation of events or operation of time-dependent protocols between systems will be
       necessary. If the system is completely isolated, this requirement is not
       applicable.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;System
@@ -14631,7 +14631,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
     <Rule id="SV-37382r1_rule" severity="medium" weight="10.0">
       <version>GEN002990</version>
       <title>The cron.allow file must not have an extended ACL.</title>
-      <description>&lt;VulnDiscussion&gt;A readable and/or writeable cron.allow file by other users than root could allow potential intruders and malicious users to use the file contents to help discern information, such as who is allowed to execute cron
+      <description>&lt;VulnDiscussion&gt;A readable and/or writable cron.allow file by other users than root could allow potential intruders and malicious users to use the file contents to help discern information, such as who is allowed to execute cron
       programs, which could be harmful to overall system and network
       security.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;System
       Administrator&lt;/Responsibility&gt;&lt;IAControls&gt;ECLP-1&lt;/IAControls&gt;</description>
@@ -18400,7 +18400,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
         <dc:identifier>2154</dc:identifier>
       </reference>
       <ident system="http://iase.disa.mil/cci">CCI-000032</ident>
-      <fixtext fixref="F-31279r1_fix">Enable one of the SELinux prolicies. Edit /etc/sysconfig/selinux and set the value of the SELINUX option to "enforcing" and SELINUXTYPE to "targeted" or "strict". Restart the system.</fixtext>
+      <fixtext fixref="F-31279r1_fix">Enable one of the SELinux policies. Edit /etc/sysconfig/selinux and set the value of the SELINUX option to "enforcing" and SELINUXTYPE to "targeted" or "strict". Restart the system.</fixtext>
       <fix id="F-31279r1_fix" />
       <check system="C-36036r1_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
@@ -18640,7 +18640,7 @@ xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/sch
       <check system="C-37168r2_chk">
         <check-content-ref name="M" href="VMS_XCCDF_Benchmark_RHEL_5_STIG.xml" />
         <check-content>Check for any running routing protocol daemons. If the system is a VM host and acts as a router solely for the benefits of its client systems, then this rule is not applicable. # chkconfig --list |grep :on|egrep
-        '(ospf|route|bgp|zebra|quagga)' If any routing protocal daemons are listed, this is a finding.</check-content>
+        '(ospf|route|bgp|zebra|quagga)' If any routing protocol daemons are listed, this is a finding.</check-content>
       </check>
     </Rule>
   </Group>
diff --git a/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf.xml b/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf.xml
index 6dfdedf..6a4219a 100644
--- a/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf.xml
+++ b/RHEL6/references/disa-stig-rhel5-v1r0.6-xccdf.xml
@@ -6894,7 +6894,7 @@ will change all files not owned by root or bin to root.</fixtext>
         <dc:identifier>2154</dc:identifier>
       </reference>
       <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-31242r1_fix">Edit the local initialization file and remove the relative path entry from the executable search path variable. If this is not feasable, justify and document the necessity of having the relative path for a specific application.</fixtext>
+      <fixtext fixref="F-31242r1_fix">Edit the local initialization file and remove the relative path entry from the executable search path variable. If this is not feasible, justify and document the necessity of having the relative path for a specific application.</fixtext>
       <fix id="F-31242r1_fix" />
       <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
         <check-content-ref name="oval:mil.disa.fso.rhel:def:142" href="U_RedHat_5_V1R0.6_STIG_Benchmark-oval.xml" />
@@ -7315,7 +7315,7 @@ Procedure:
     <Rule id="SV-26292r1_rule" severity="medium" weight="10.0">
       <version>GEN000241</version>
       <title>The system clock must be synchronized continuously, or at least daily.</title>
-      <description>&lt;VulnDiscussion&gt;A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems.  Internal system clocks tend to drift and require periodic resynchronization to ensure their accuracy.  Software, such as ntpd, can be used to continuously synchronize the system clock with authoritative sources.  Alternatively, the system may be synchronized periodically, with a maximum of one day between synchronizations.
+      <description>&lt;VulnDiscussion&gt;A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems.  Internal system clocks tend to drift and require periodic re-synchronization to ensure their accuracy.  Software, such as ntpd, can be used to continuously synchronize the system clock with authoritative sources.  Alternatively, the system may be synchronized periodically, with a maximum of one day between synchronizations.
 
 If the system is completely isolated (i.e., it has no connections to networks or other systems), time synchronization is not required as no correlation of events or operation of time-dependent protocols between systems will be necessary. If the system is completely isolated, this requirement is not applicable.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;System Administrator&lt;/Responsibility&gt;&lt;IAControls&gt;ECSC-1&lt;/IAControls&gt;</description>
       <reference>
@@ -10560,7 +10560,7 @@ Note:  Depending on the particular implementation, group and other read permissi
       </reference>
       <ident system="http://cce.mitre.org">CCE-3977-6</ident>
       <ident system="http://iase.disa.mil/cci">CCI-000032</ident>
-      <fixtext fixref="F-31279r1_fix">Enable one of the SELinux prolicies.
+      <fixtext fixref="F-31279r1_fix">Enable one of the SELinux policies.
 Edit /etc/sysconfig/selinux and set the value of the SELINUX option to "enforcing" and SELINUXTYPE to "targeted" or "strict".
 Restart the system.</fixtext>
       <fix id="F-31279r1_fix" />
diff --git a/RHEL6/references/usgcb-rhel5desktop-oval.xml b/RHEL6/references/usgcb-rhel5desktop-oval.xml
index 57b3c71..bf3620d 100644
--- a/RHEL6/references/usgcb-rhel5desktop-oval.xml
+++ b/RHEL6/references/usgcb-rhel5desktop-oval.xml
@@ -2924,7 +2924,7 @@
 					<platform>Red Hat Enterprise Linux 5</platform>
 				</affected>
 				<reference ref_id="CCE-3845-5" source="CCE"/>
-				<description>The SSH idle timout interval should be set to an appropriate value (and dependencies are met)</description>
+				<description>The SSH idle timeout interval should be set to an appropriate value (and dependencies are met)</description>
 			</metadata>
 			<criteria operator="OR" comment="SSH is not being used or conditions are met">
 				<extend_definition definition_ref="oval:gov.nist.usgcb.rhel:def:20234" comment="sshd service is disabled"/>
@@ -3997,7 +3997,7 @@
 		</definition>
 	</definitions>
 	<tests>
-		<!-- OVAL Repostiory defniition tests -->
+		<!-- OVAL Repository definition tests -->
 		<uname_test id="oval:org.mitre.oval:tst:3929" version="1" comment="ix64 architecture" check_existence="at_least_one_exists" check="at least one" xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix">
 			<object object_ref="oval:org.mitre.oval:obj:2759"/>
 			<state state_ref="oval:org.mitre.oval:ste:3081"/>
@@ -4388,7 +4388,7 @@
 			<unix-def:object object_ref="oval:gov.nist.usgcb.rhel:obj:200855"/>
 			<unix-def:state state_ref="oval:gov.nist.usgcb.rhel:ste:2008552"/>
 		</unix-def:file_test>
-		<unix-def:file_test check_existence="any_exist" id="oval:gov.nist.usgcb.rhel:tst:200861" version="1" check="all" comment="home directories are group writeable">
+		<unix-def:file_test check_existence="any_exist" id="oval:gov.nist.usgcb.rhel:tst:200861" version="1" check="all" comment="home directories are group writable">
 			<unix-def:object object_ref="oval:gov.nist.usgcb.rhel:obj:20086"/>
 			<unix-def:state state_ref="oval:gov.nist.usgcb.rhel:ste:200861"/>
 		</unix-def:file_test>
@@ -5999,7 +5999,7 @@
 		<ind-def:unknown_test id="oval:gov.nist.usgcb.rhel:tst:142680" version="1" check="all" comment="Test implementation is unknown, unavailable, or impossible"/>
 		<ind-def:unknown_test id="oval:gov.nist.usgcb.rhel:tst:41880" version="1" check="all" comment="Test implementation is unknown, unavailable, or impossible"/>
 		<ind-def:unknown_test id="oval:gov.nist.usgcb.rhel:tst:42490" version="1" check="all" comment="Test implementation is unknown, unavailable, or impossible"/>
-		<unix-def:file_test check="all"  check_existence="none_exist" comment="check for the existince of /proc/net/wireless" version="1" id="oval:gov.nist.usgcb.rhel:tst:42760">
+		<unix-def:file_test check="all"  check_existence="none_exist" comment="check for the existence of /proc/net/wireless" version="1" id="oval:gov.nist.usgcb.rhel:tst:42760">
 			<unix-def:object object_ref="oval:gov.nist.usgcb.rhel:obj:42760"/>
 		</unix-def:file_test>
 		<ind-def:unknown_test id="oval:gov.nist.usgcb.rhel:tst:34850" version="1" check="all" comment="Test implementation is unknown, unavailable, or impossible"/>
@@ -6039,7 +6039,7 @@
 		<lin-def:rpminfo_object id="oval:gov.nist.usgcb.rhel:obj:200065" version="1">
 			<lin-def:name>gpg-pubkey</lin-def:name>
 		</lin-def:rpminfo_object>
-		<unix-def:file_object id="oval:gov.nist.usgcb.rhel:obj:20009" version="1" comment="Check existance of yum.cron">
+		<unix-def:file_object id="oval:gov.nist.usgcb.rhel:obj:20009" version="1" comment="Check existence of yum.cron">
 			<unix-def:path operation="pattern match">^/etc/cron\.(hourly|daily|weekly|monthly)$</unix-def:path>
 			<unix-def:filename>yum.cron</unix-def:filename>
 		</unix-def:file_object>
@@ -9376,14 +9376,14 @@
 		</ind-def:textfilecontent54_object>
 	</objects>
 	<states>
-		<!-- OVAL Repository defintion states -->
+		<!-- OVAL Repository definition states -->
 		<uname_state id="oval:org.mitre.oval:ste:3081" version="1" xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix">
 			<processor_type>x86_64</processor_type>
 		</uname_state>
 		<rpminfo_state id="oval:org.mitre.oval:ste:11314" version="1" xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux">
 			<version operation="pattern match">^.*5.</version>
 		</rpminfo_state>
-		<!-- end OVAL Reposition definition states -->
+		<!-- end OVAL Repository definition states -->
 		<family_state id="oval:gov.nist.usgcb.rhel:ste:20001" version="1" xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent">
 			<family>unix</family>
 		</family_state>
@@ -10233,7 +10233,7 @@
 		<external_variable id="oval:gov.nist.usgcb.rhel:var:20092" version="1" datatype="string" comment="External variable for definition 20092"/>
 		<external_variable id="oval:gov.nist.usgcb.rhel:var:20094" version="1" datatype="string" comment="External variable for definition 20094"/>
 		<external_variable id="oval:gov.nist.usgcb.rhel:var:20093" version="1" datatype="string" comment="External variable for definition 20093"/>
-		<external_variable id="oval:gov.nist.usgcb.rhel:var:20098" version="1" datatype="string" comment="External variable for definitions 20098 20100 Inactivity timout"/>
+		<external_variable id="oval:gov.nist.usgcb.rhel:var:20098" version="1" datatype="string" comment="External variable for definitions 20098 20100 Inactivity timeout"/>
 		<external_variable id="oval:gov.nist.usgcb.rhel:var:20099" version="1" datatype="int" comment="External variable for definitions 20099"/>
 		<!-- turn minutes into seconds -->
 		<external_variable id="oval:gov.nist.usgcb.rhel:var:20102" version="1" datatype="string" comment="External variable for definitions 200102 20103 Warning Banner"/>
diff --git a/RHEL6/references/usgcb-rhel5desktop-xccdf.xml b/RHEL6/references/usgcb-rhel5desktop-xccdf.xml
index a0403c8..cf9525d 100644
--- a/RHEL6/references/usgcb-rhel5desktop-xccdf.xml
+++ b/RHEL6/references/usgcb-rhel5desktop-xccdf.xml
@@ -2,7 +2,7 @@
 <Benchmark xmlns="http://checklists.nist.gov/xccdf/1.1" xmlns:cdf="http://checklists.nist.gov/xccdf/1.1" xmlns:cpe="http://cpe.mitre.org/dictionary/2.0" xmlns:cpel="http://cpe.mitre.org/language/2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dsig="http://w3.org/2000/09/xmldsig#" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="USGCB-RHEL-5-Desktop" xml:lang="en-US" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" style="SCAP_1.1" resolved="false">
 	<!-- Benchmark Information -->
 	<status date="2010-08-20">draft</status>
-	<title override="0">USGCB: Guidance for Securing Redhat Enterprise Linux 5 Desktop Systems for IT
+	<title override="0">USGCB: Guidance for Securing Red Hat Enterprise Linux 5 Desktop Systems for IT
 		Professionals</title>
 	<description override="0">This guide has been created to assist IT professionals in effectively securing
 		systems running Red Hat Enterprise Linux 5 desktops.</description>
@@ -10,7 +10,7 @@
 		this guide without first testing them in a non-operational environment. NIST assumes no
 		responsibility whatsoever for its use by other parties, and makes no guarantees, expressed
 		or implied, about its quality, reliability, or any other characteristic. NIST would
-		appreciate acknowledgement if the document and template are used.</notice>
+		appreciate acknowledgment if the document and template are used.</notice>
 	<front-matter xml:lang="en-US" override="0">TODO::Insert</front-matter>
 	<rear-matter xml:lang="en-US" override="0"><xhtml:strong>Trademark Information</xhtml:strong><xhtml:br/><xhtml:br/> Red Hat and Red Hat Enterprise Linux are either registered trademarks or
 		trademarks of Red Hat, Inc. in the United States and other countries.<xhtml:br/><xhtml:br/><xhtml:br/>All other names are registered trademarks or trademarks of their
@@ -45,12 +45,12 @@
 	<!--                                                                                                      																										-->
 	<!-- These profiles outline the specific guidance outlined by the US Government Configuration Baselines.  														-->
 	<!-- Each defines the set of XCCDF rules that are applicable for that guidance as well as specific values 															-->
-	<!-- to be used when determining complinace.                                                              																				-->
+	<!-- to be used when determining compliance.                                                              																				-->
 	<!--                                                                                      																														-->
 	<Profile id="united_states_government_configuration_baseline" abstract="false" prohibitChanges="false">
 		<title xml:lang="en-US" override="0">United States Government Configuration Baseline 0.0.4.0</title>
 		<description xml:lang="en-US" override="0">This profile represents guidance outlined in United States
-			Government Configuration Baseline for desktop systems with Redhat Enterprise Linux 5
+			Government Configuration Baseline for desktop systems with Red Hat Enterprise Linux 5
 			installed.</description>
 		<select idref="usgcb-rhel5desktop-rule-2.1.1.1.1.a" selected="true"/>
 		<select idref="usgcb-rhel5desktop-rule-2.1.1.1.2.a" selected="true"/>
@@ -345,7 +345,7 @@
 		<refine-value idref="usgcb-rhel5desktop-var-2.3.5.2.b" selector="root"/>
 		<!-- permissions on /etc/hrub.conf -->
 		<refine-value idref="usgcb-rhel5desktop-var-2.3.5.5" selector="15_minutes"/>
-		<!-- Inactivity timout -->
+		<!-- Inactivity timeout -->
 		<refine-value idref="usgcb-rhel5desktop-var-2.3.7" selector="usgcb_default"/>
 		<!-- login banner verbiage -->
 		<refine-value idref="usgcb-rhel5desktop-var-2.4.2.c" selector="enforcing"/>
@@ -1078,7 +1078,7 @@
 					system accounts have a uid lower than 500). Run it once for each local
 					partition PART:<xhtml:br/><xhtml:br/><xhtml:code># find PART -xdev -type d -perm -0002 -uid +500
 						-print<xhtml:br/></xhtml:code><xhtml:br/> If this command produces any output, investigate why the current
-					owner is not root or another system account.<xhtml:br/><xhtml:br/> Allowing a user account to own a world-writeable directory is
+					owner is not root or another system account.<xhtml:br/><xhtml:br/> Allowing a user account to own a world-writable directory is
 					undesirable because it allows the owner of that directory to remove or
 					replace any ﬁles that may be placed in the directory by other
 					users.</description>
@@ -1736,8 +1736,8 @@
 						<Rule id="usgcb-rhel5desktop-rule-2.3.3.1.1.e" selected="false" weight="10.0" prohibitChanges="false" abstract="false" hidden="false" role="full" severity="unknown">
 							<status date="2010-07-01">draft</status>
 							<version update="1"/>
-							<title override="0">CCE-14122-6:The password strenght parameters should require a minimum number of special characters</title>
-							<description override="0">The password strenght parameters should require a minimum number of special characters</description>
+							<title override="0">CCE-14122-6:The password strength parameters should require a minimum number of special characters</title>
+							<description override="0">The password strength parameters should require a minimum number of special characters</description>
 							<ident system="http://cce.mitre.org">CCE-14122-6</ident>
 							<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5" selector="">
 								<check-export value-id="usgcb-rhel5desktop-var-2.3.3.1.1.ocredit" export-name="oval:gov.nist.usgcb.rhel:var:200785"/>
@@ -1748,7 +1748,7 @@
 							<status date="2010-07-01">draft</status>
 							<version update="1"/>
 							<title override="0">CCE-14712-4:Set Password lcredit Requirements</title>
-							<description override="0">The password strenght parameters should require a minimum number of lowercase characters</description>
+							<description override="0">The password strength parameters should require a minimum number of lowercase characters</description>
 							<ident system="http://cce.mitre.org">CCE-14712-4</ident>
 							<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5" selector="">
 								<check-export value-id="usgcb-rhel5desktop-var-2.3.3.1.1.lcredit" export-name="oval:gov.nist.usgcb.rhel:var:200786"/>
@@ -2204,7 +2204,7 @@
 							configuration system, see http://www.gnome.org/projects/gconf and the
 							man page gconftool-2(1).</description>
 						<Value id="usgcb-rhel5desktop-var-2.3.5.5" type="string" operator="equals">
-						<title>Inactivity timout</title>
+						<title>Inactivity timeout</title>
 						<description xml:lang="en-US">Choose allowed duration of inactive SSH
 							connections, shells, and X sessions</description>
 						<value>15</value>
@@ -2468,7 +2468,7 @@ enforcement officials.
 						convenience of category label translation, disable the MCS translation
 						service: <xhtml:br/><xhtml:br/><xhtml:code># chkconfig mcstrans off <xhtml:br/></xhtml:code><xhtml:br/> The mcstransd daemon provides the category label translation
 						information defined in /etc/selinux/targeted/ setrans.conf to client
-						processes which request this information.<xhtml:br/><xhtml:br/> Category labelling is unlikely to be used except in sites with
+						processes which request this information.<xhtml:br/><xhtml:br/> Category labeling is unlikely to be used except in sites with
 						special requirements. Therefore, it should be disabled in order to reduce
 						the amount of potentially vulnerable code running on the system. See Section
 						2.4.6 for more information about systems which use category
@@ -4479,9 +4479,9 @@ enforcement officials.
 					<Rule id="usgcb-rhel5desktop-rule-3.5.2.3.a" selected="false" weight="10.0" prohibitChanges="false" abstract="false" hidden="false" role="full" severity="unknown">
 						<status date="2010-07-01">accepted</status>
 						<version update="1"/>
-						<title override="0">CCE-3845-5:The SSH idle timout interval should be set to an appropriate
+						<title override="0">CCE-3845-5:The SSH idle timeout interval should be set to an appropriate
 							value</title>
-						<description override="0">The SSH idle timout interval should be set to an appropriate
+						<description override="0">The SSH idle timeout interval should be set to an appropriate
 							value</description>
 						<ident system="http://cce.mitre.org">CCE-3845-5</ident>
 						<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5" selector="">
-- 
1.7.11.7

