Cleaned up Awareness Training documentation - #292
Merged
ben-AI-cybersec merged 2 commits intoAug 19, 2025
Merged
Conversation
ben-AI-cybersec
approved these changes
Aug 19, 2025
ben-AI-cybersec
left a comment
Member
There was a problem hiding this comment.
good work, please continue with this!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This update cleans up and improves the Cybersecurity User Awareness Training documentation in the Awareness-Training folder for clarity, structure, and readability.
Detailed Changes
Improved readability: Simplified complex sentences, fixed minor grammar issues, and ensured consistent terminology.
Consistent formatting: Standardised headings, bullet points, and section spacing.
Structural cleanup: Ensured all sections follow a logical flow — Purpose → Introduction → Specific Training → Help Routes → Major Areas → Data Classification → DLP Strategies → Encryption Standards → Playbook Awareness → Ethics.
Policy references: Verified that all policy references (Data Classification – DLP Policy, Cryptography Policy) are mentioned consistently and match naming conventions.
Technical consistency:
File integrity: Maintained original meaning and technical accuracy while improving flow and removing redundant text.