-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Learning Path “cybersecurity” #147
base: main
Are you sure you want to change the base?
Update Learning Path “cybersecurity” #147
Conversation
WalkthroughThe cybersecurity content file was comprehensively updated to improve its structure and relevance. Key modifications include a revised title, an updated date, and a new external image URL. The tags were adjusted by removing outdated ones and adding new relevant tags. The introduction and prerequisites sections were rewritten, and new sections for "Topics To Learn" and "Resources" were introduced while several older sections were removed. Additionally, the author and path type declarations were added. Changes
Poem
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for th-learn ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (12)
content/cybersecurity.md (12)
19-22
: Improve Grammar and Punctuation in the Introduction
The updated "What is Cybersecurity?" section improves clarity; however, remove the extra space before the question mark in the heading and consider revising the paragraph (e.g., "It's an ever-evolving field" instead of "Its an every evolving field") for enhanced readability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~21-~21: A period might be missing here.
Context: ...and defenders are getting better day by day ## Prerequisites Cybersecurity is on...(AI_EN_LECTOR_MISSING_PUNCTUATION_PERIOD)
25-30
: Refine the Prerequisites Section for Clarity
The current sentence in this section is a bit convoluted. Consider rephrasing it to something like:"Cybersecurity is a field with a low entry barrier regardless of your background. With a passion for learning, you can easily grasp these topics, such as:"
This change would improve punctuation and overall readability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~25-~25: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...quisites Cybersecurity is one of those field which has the lowest entry barrier no m...(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
[uncategorized] ~25-~25: A punctuation mark might be missing here.
Context: ...field which has the lowest entry barrier no matter you background you can easily gr...(AI_EN_LECTOR_MISSING_PUNCTUATION)
[uncategorized] ~25-~25: A comma might be missing here.
Context: ... the lowest entry barrier no matter you background you can easily grasp these contents if ...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~30-~30: A punctuation mark might be missing here.
Context: ... as cybersecurity is evolving day by day if you wont catch up with new things you w...(AI_EN_LECTOR_MISSING_PUNCTUATION)
[uncategorized] ~30-~30: A comma might be missing here.
Context: ...ay by day if you wont catch up with new things you would be left back ## Topics To L...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
34-34
: Replace Informal Language
The use of "wanna" in this sentence is too informal. Please change it to "want to" for a more professional tone.🧰 Tools
🪛 LanguageTool
[style] ~34-~34: The word ‘wanna’ is informal.
Context: ...left back ## Topics To Learn If you wanna dive into cybersecurity these are the t...(WANNA)
36-45
: Operating System Security: Spelling Consistency
The Operating System Security section is well-organized. However, please check the spelling of "acess control" on line 45 and update it to "access control" with consistent capitalization.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
36-36: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4(MD001, heading-increment)
46-65
: Network Security: Correct Duplicates and Typos
- A duplicate entry for "Firewall Configurations" appears (lines 48 and 52); consider consolidating or clarifying these entries.
- On line 60, "Remote acess configurations" should be corrected to "Remote access configurations."
🧰 Tools
🪛 LanguageTool
[duplication] ~51-~51: Possible typo: you repeated a word.
Context: ...vs stateful inspection * Next gen Firewall * Firewall Configurations * Intrusion Detection...(ENGLISH_WORD_REPEAT_RULE)
[uncategorized] ~55-~55: This expression is usually spelled with a hyphen.
Context: ...revention system * Signature vs anomaly based * Installation & Configuration ...(BASED_HYPHEN)
66-79
: Web Application Security: Enhance Terminology and Consistency
- Consider changing "practises" to "practices" if American English is preferred.
- Update "Token based authentication" to "token-based authentication" to correctly hyphenate the compound adjective.
- Adjust "API Security" to "API Security" for uniformity.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~73-~73: This expression is usually spelled with a hyphen.
Context: ...g practises * API Security * Token based authentication * Rate limiting an...(BASED_HYPHEN)
80-89
: Cryptography: Address Spelling and Formatting Issues
- Correct "encription" on line 83 and similarly on line 84 to "encryption."
- Format "SHA 2, SHA 3" as "SHA-2, SHA-3" for clarity.
90-111
: Penetration Testing & Ethical Hacking: Fix Typos and Clarify Terms
- On line 93, "IFootprinting, OSINTncide" appears to contain typos; consider revising to "Footprinting, OSINT."
- Change "privilage escalations" on line 105 to "privilege escalation."
- Correct the capitalization in "TImestamp tampering" on line 110 to "Timestamp tampering."
112-121
: Incident Response & Digital Forensics: Minor Correction
Please change "memmory forensics" on line 119 to "memory forensics" for accurate spelling.
122-135
: Security Operations & Monitoring: Correct Typos and Verify Terminology
- On line 126, "incident detectionn" should be corrected to "incident detection."
- Update "Procative hunting" on line 129 to "Proactive hunting."
- Review "Automated contamination and remediation" on line 134; if the intended term is "containment," please update accordingly.
136-149
: Cloud Security: Address Formatting and Spelling Issues
- On line 139, replace "Securing AWS< Azure and GCP enviornments." with "Securing AWS, Azure, and GCP environments."
- On line 140, correct "Identity acess management ( IAM )" to "Identity access management (IAM)."
158-158
: Resource URL Formatting Issue
The URL on line 158 contains an unnecessary escape character (\https://www.wi-fi.org/
). Please remove the backslash to ensure the link renders correctly.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/cybersecurity.md
(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/cybersecurity.md
[uncategorized] ~21-~21: A period might be missing here.
Context: ...and defenders are getting better day by day ## Prerequisites Cybersecurity is on...
(AI_EN_LECTOR_MISSING_PUNCTUATION_PERIOD)
[uncategorized] ~25-~25: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...quisites Cybersecurity is one of those field which has the lowest entry barrier no m...
(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
[uncategorized] ~25-~25: A punctuation mark might be missing here.
Context: ...field which has the lowest entry barrier no matter you background you can easily gr...
(AI_EN_LECTOR_MISSING_PUNCTUATION)
[uncategorized] ~25-~25: A comma might be missing here.
Context: ... the lowest entry barrier no matter you background you can easily grasp these contents if ...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~30-~30: A punctuation mark might be missing here.
Context: ... as cybersecurity is evolving day by day if you wont catch up with new things you w...
(AI_EN_LECTOR_MISSING_PUNCTUATION)
[uncategorized] ~30-~30: A comma might be missing here.
Context: ...ay by day if you wont catch up with new things you would be left back ## Topics To L...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[style] ~34-~34: The word ‘wanna’ is informal.
Context: ...left back ## Topics To Learn If you wanna dive into cybersecurity these are the t...
(WANNA)
[duplication] ~51-~51: Possible typo: you repeated a word.
Context: ...vs stateful inspection * Next gen Firewall * Firewall Configurations * Intrusion Detection...
(ENGLISH_WORD_REPEAT_RULE)
[uncategorized] ~55-~55: This expression is usually spelled with a hyphen.
Context: ...revention system * Signature vs anomaly based * Installation & Configuration ...
(BASED_HYPHEN)
[uncategorized] ~73-~73: This expression is usually spelled with a hyphen.
Context: ...g practises * API Security * Token based authentication * Rate limiting an...
(BASED_HYPHEN)
🪛 markdownlint-cli2 (0.17.2)
content/cybersecurity.md
36-36: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
🔇 Additional comments (1)
content/cybersecurity.md (1)
3-15
: Front Matter Update: Date, Image, Tags, Authors, and PathType
The metadata updates (date, external image URL, added tags, new author, and pathType) align with the updated learning path and PR objectives. Ensure the formatting remains consistent with other content pages going forward.
Automatically generated by Netlify CMS
Summary by CodeRabbit