"RHEL6" => "RHEL 6" naming scheme

Noticed the User Guide incorrectly had "RHEL6," which should be "RHEL 6" per Red Hat's syntax guides.
Removing whitespace in primary README

Removing whitespace line in README file
Updated README to reflect move to GitHub

Added GitHub URL to README file
Created OVAL for aide_periodic_cron_checking

Adds OVAL for aide_periodic_cron_checking.

Original patch by Gabe Alford, modified by swells to:
- Reset signoff to Gabe
- Place OVAL in shared
- Setup symlinks
Added bash remediation for aide_periodic_cron_checking
Merge pull request #1 from OpenSCAP/master

rebase
Merge branch 'master' into crontab_oval
Updating README
Merge pull request #13 from shawndwells/aide_periodic_cron_checking

Aide periodic cron checking
Merge pull request #14 from shawndwells/master

Updating README
Merge pull request #2 from OpenSCAP/master

rebase against upstream
[PATCH] Update C2S profile <description> per request from CIS

The prior wording of the C2S profile contained a statement that the C2S profile,
as it is derived from CIS' publicly available RHEL6 Benchmark [1],
could measure a system against the CIS RHEL6 baseline.

We have been informed that per CIS' terms and conditions, specifically under
RESTRICTIONS, item #8, one may not "represent or claim a particular level of
compliance or consistency with any SB product."

To remain in compliance with CIS' request, this patch updates the C2S profile
description to indicate that while the C2S profile may be sourced from the public,
freely available CIS benchmark, no representation or claim to a particular
level of compliance or consistency is being made.

CIS is eager to collaborate more closely with the community (and Red Hat) on
guidance development, in particular through the SCAP Security Guide. They have
expressed that having automated security guidance and workflows ship with the Operating
System is definitely a positive step, and one they encourage. Unfortunately, we were
unable to reconcile the CIS Terms and Conditions to provide a freely available SCAP
profile against the CIS baseline. When faced with the choice of paying
~$20,000 license fees [2], or rewording references to CIS compliance, the later was chosen.

[1] https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_6_Bench
mark_v1.2.0.pdf
[2] http://benchmarks.cisecurity.org/membership/certified/overview/
Merge pull request #21 from shawndwells/CIS

CIS profile rewording