+++ This bug was initially created as a clone of Bug #1331780 +++

Description of problem - incorrect English words or collocations:
compromized -> compromised
signal a intrusion -> signal an intrusion
be a mislabeled -> be mislabeled
tries modify -> tries to modify

Version-Release number of selected component (if applicable):
setroubleshoot-plugins-3.0.40-2.el6.noarch
setroubleshoot-server-3.0.47-9.1.el6.i686

How reproducible:
always

Steps to Reproduce:
# cd /usr/share/setroubleshoot/plugins/
# grep -R "compromized" *.py
allow_execmod.py:    application is compromized or not.  This could be a serious issue. Your 
allow_execmod.py:setroubleshoot examined '$FIX_TARGET_PATH' to make sure it was built correctly, but can not determine if this application has been compromized.  This alert could be a serious issue and your system could be compromised.
# grep -R "a intrusion" *.py
connect_ports.py:    to connect to $PORT_NUMBER, this could signal a intrusion attempt.
httpd_can_sendmail.py:    signal a intrusion attempt.
rsync_data.py:    it could indicate either a bug or it could signal a intrusion attempt.
samba_share.py:    it could indicate either a bug or it could signal a intrusion attempt.
swapfile.py:    signal a intrusion attempt.
# grep -R "be a mislabeled" *.py
openvpn.py:    be a mislabeled. openvpn is allowed to read content in home directory if it 
restorecon.py:    be a mislabeled.  $TARGET_PATH default SELinux type is
sshd_root.py:    be a mislabeled. sshd is allowed to read content in /root/.ssh directory if it 
# grep -R "tries modify" *.py
mmap_zero.py:    for them.  If a compromised application tries modify the kernel this AVC 
#

Expected results:
* typo errors are gone