Fix markdown spacing in intro note batch

Author: stacknil

TryHackMe/00-foundations/computer-types.md

@@ -1,25 +1,31 @@
 ---
-
-platform: TryHackMe
+type: resource-note
+status: done
+created: 2026-02-15
+updated: 2026-03-12
+tags: [security-writeup, tryhackme, hardware, systems]
+source: TryHackMe - Computer Types
+platform: tryhackme
 room: Computer Types
 slug: computer-types
 path: TryHackMe/00-foundations/computer-types.md
 topic: 00-foundations
-domain: [Systems]
+domain: [foundations, hardware]
 skills: [hardware-basics, infra-basics, systems-thinking]
 artifacts: [concept-notes]
-status: done
-date: 2026-02-15
+sanitized: true
 ---
 
-## 0) Summary
+# Computer Types
+
+## Summary
 
 * Computers are not defined by having a screen/keyboard; many are “hidden” inside everyday objects.
 * Different computer types exist because design is a trade-off: mobility vs cooling/performance; reliability vs cost; purpose shapes interface and architecture.
 * Key taxonomy covered: Laptop, Desktop, Workstation, Server, Smartphone, Tablet, IoT device, Embedded computer.
 * A practical rule: *There is no best computer; only the right tool for the job.*
 
-## 1) Key Concepts
+## Key Concepts
 
 ### 1.1 Computers you sit in front of
 
@@ -57,9 +63,9 @@ IoT vs Embedded (quick discriminator):
 * Reliability costs money: critical systems use redundancy (extra power supplies/disks) to reduce failure.
 * Purpose shapes everything: phones are interacted with directly; servers are queried for services; embedded systems operate quietly.
 
-## 2) Walkthrough Notes by Task (based on provided screenshots)
+### 2) Walkthrough Notes by Task (based on provided screenshots)
 
-### Task 1 — Sophia’s First Day (Hidden computers)
+#### Task 1 — Sophia’s First Day (Hidden computers)
 
 Goal: find all hidden computers with limited mistakes.
 Found set (8/8):
@@ -75,7 +81,7 @@ Found set (8/8):
 
 Takeaway: “computer” includes any device with compute + control logic, not just PCs.
 
-### Task 2 — The Hot Laptop (Cooling constraints)
+#### Task 2 — The Hot Laptop (Cooling constraints)
 
 Observation:
 
@@ -85,46 +91,46 @@ Observation:
 * Laptop: **throttles under load**.
 * Desktop: **sustained performance**.
 
-### Task 3 — The Server Room (Redundancy)
+#### Task 3 — The Server Room (Redundancy)
 
 Scenario: servers run 24/7; test power configurations.
 Key message: “Redundant power reduces a single failure point.”
 Note: uptime improves when redundancy is combined with backups and monitoring.
 
-### Task 4 — The Right Tool (Match job → computer type)
+#### Task 4 — The Right Tool (Match job → computer type)
 
 Matched jobs (3/3):
 
 * Edit 4K video all day → **Workstation**
 * Host a website 24/7 → **Server**
 * Ring when button pressed → **Embedded**
 
-### Task 5 — Graduation Quiz (answers from screenshots)
+#### Task 5 — Graduation Quiz (answers from screenshots)
 
-1. Why do laptops throttle more than desktops?
+### Why do laptops throttle more than desktops?
 
 * **Less cooling space**
 
-2. What does server redundancy prevent?
+### What does server redundancy prevent?
 
 * **Single point of failure**
 
-3. Why do smartphones last longer on battery than laptops?
+### Why do smartphones last longer on battery than laptops?
 
 * **Optimized for efficiency**
 
-4. Which feature is more common in workstations?
+### Which feature is more common in workstations?
 
 * **ECC RAM and certified drivers**
 
-## 3) Pattern Cards (generalizable)
+## Pattern Cards
 
 * Trade-off lens (Design Trade-offs / 设计权衡): portability ↔ cooling ↔ sustained performance.
 * Reliability engineering (Reliability / 可靠性): redundancy reduces SPOF (Single Point of Failure / 单点故障).
 * Taxonomy heuristic: if a device is single-purpose *and* network-connected → likely IoT; if single-purpose but offline → likely embedded.
 * Selection rule: choose by workload + uptime requirement + interaction model, not by appearance.
 
-## 5) Takeaways
+## Takeaways
 
 * “Computer” is a role (compute/control) rather than a shape (screen/keyboard).
 * Sustained workloads expose thermal design limits; desktops win when time-under-load matters.

TryHackMe/00-foundations/history-of-malware.md

@@ -1,18 +1,24 @@
 ---
-
+type: resource-note
+status: done
+created: 2026-02-13
+updated: 2026-03-12
+tags: [security-writeup, tryhackme, malware, history]
+source: TryHackMe - History of Malware
 platform: tryhackme
 room: History of Malware
 slug: history-of-malware
-path: notes/00-foundations/history-of-malware.md
+path: TryHackMe/00-foundations/history-of-malware.md
 topic: 00-foundations
-domain: [malware]
-skills: [networking-history, malware-history, fundamentals]
+domain: [foundations, malware]
+skills: []
 artifacts: [concept-notes]
-status: done
-date: 2026-02-13
+sanitized: true
 ---
 
-## 0) Summary
+# History of Malware
+
+## Summary
 
 * Malware history is tightly coupled with how computers started to **share resources over networks** (resource sharing) and later how microcomputers spread software via **removable media** (floppy disks).
 * Early “malware-like” programs often looked like **experiments** in mobility or replication (e.g., Creeper), but they revealed real operational risks: uncontrolled replication → **resource exhaustion** and denial of service.
@@ -30,7 +36,7 @@ date: 2026-02-13
 * boot sector virus (引导扇区病毒)
 * obfuscation/encryption for stealth (为隐蔽而做的混淆/加密)
 
-## 1) Key Concepts
+## Key Concepts
 
 ### 1.1 Self-replicating programs
 
@@ -46,9 +52,9 @@ A simple mental model:
 [Data/File] -> [Packets] -> (Network routes) -> [Packets] -> [Reassembled Data/File]
 ```
 
-## 2) Timeline Notes (Task-by-Task)
+### 2) Timeline Notes (Task-by-Task)
 
-### 2.1 Creeper (1971)
+#### 2.1 Creeper (1971)
 
 Context:
 
@@ -73,14 +79,14 @@ Key Q/A anchors:
 * Re-designed by: **Ray Tomlinson**
 * Printed text: **“I’m the creeper, catch me if you can!”**
 
-### 2.2 ARPANET basics
+#### 2.2 ARPANET basics
 
 * “ARPANET” stands for **Advanced Research Projects Agency Network**.
 * Early ARPANET emphasized **remote login** and **file transfer**.
 * The Network Working Group created the **Network Control Program (NCP)**.
 * Data transfer model: **packet switching**.
 
-### 2.3 Reaper
+#### 2.3 Reaper
 
 Context:
 
@@ -98,7 +104,7 @@ Key Q/A anchors:
 * Main project (Bob Thomas): develop a **resource-sharing capability** (RSEXEC).
 * API: **Application Programming Interface**.
 
-### 2.4 Wabbit / Rabbit (1974)
+#### 2.4 Wabbit / Rabbit (1974)
 
 Context:
 
@@ -118,7 +124,7 @@ Key Q/A anchors:
 * Modern-day “fork bomb” also known as: **Denial-of-Service attack**
 * Name derived from: Elmer Fudd’s pronunciation of “Rabbit” (“Wabbit”).
 
-### 2.5 ANIMAL + PERVADE (1975)
+#### 2.5 ANIMAL + PERVADE (1975)
 
 Context:
 
@@ -142,7 +148,7 @@ Key Q/A anchors:
 * Malware type: **Trojan**
 * Wooden horse built by: **Greeks**
 
-### 2.6 Elk Cloner (1982)
+#### 2.6 Elk Cloner (1982)
 
 Context:
 
@@ -167,7 +173,7 @@ Key Q/A anchors:
 * More/less common today: **less common**
 * Development time: **2 weeks**
 
-### 2.7 The Morris Internet Worm (1988)
+#### 2.7 The Morris Internet Worm (1988)
 
 Context:
 
@@ -196,7 +202,7 @@ Key Q/A anchors:
 * rsh meaning: **remote shell**
 * Fork bomb is a type of: **Denial-of-Service**
 
-### 2.8 Cascade
+#### 2.8 Cascade
 
 What made it notable:
 
@@ -220,7 +226,7 @@ Key Q/A anchors:
 * OS: **DOS**
 * Added bytes (typical): **1704**
 
-## 3) Pattern Cards (transferable mental models)
+## Pattern Cards
 
 ### Pattern 1: Uncontrolled replication → DoS
 
@@ -248,7 +254,7 @@ Encryption/obfuscation can be used defensively (privacy) or offensively (avoid d
 * First anti-virus program in this narrative: Reaper
 * API stands for: Application Programming Interface
 
-## 5) References (optional, for fact-checking)
+## References
 
 * SANS ISC diary on early worms / Creeper discussion (secondary summary).
 * Cascade (computer virus) overview (encyclopedic summary).

TryHackMe/00-foundations/intro-cybersecurity/careers-in-cyber.md

@@ -1,12 +1,30 @@
-# Careers in Cyber – Role Overview Notes
+---
+type: resource-note
+status: done
+created: 2026-03-11
+updated: 2026-03-11
+tags: [security-writeup, tryhackme, careers, cyber]
+source: TryHackMe - Careers in Cyber
+platform: tryhackme
+room: Careers in Cyber
+slug: careers-in-cyber
+path: TryHackMe/00-foundations/intro-cybersecurity/careers-in-cyber.md
+topic: 00-foundations
+domain: [foundations]
+skills: []
+artifacts: [concept-notes]
+sanitized: true
+---
+
+# Careers in Cyber
 
 - **Type:** Concept / career mapping  
 - **Focus:** Security roles & typical responsibilities  
 - **Source context:** TryHackMe “Careers in Cyber” room
 
 ---
 
-## 1. Why Cyber Security as a Career?
+## Summary
 
 Key points from the room:
 
@@ -22,9 +40,11 @@ This note summarises the main roles presented in the room and how they connect.
 
 ---
 
-## 2. Core Defensive & Monitoring Roles
+## Key Concepts
+
+### 2. Core Defensive & Monitoring Roles
 
-### 2.1 Security Analyst
+#### 2.1 Security Analyst
 
 **Goal:** Maintain and continuously assess the security posture of an organisation.
 
@@ -49,7 +69,7 @@ Role keywords:
 
 ---
 
-### 2.2 Security Engineer
+#### 2.2 Security Engineer
 
 **Goal:** Design, build, and maintain the technical defences.
 
@@ -72,7 +92,7 @@ Role keywords:
 
 ---
 
-### 2.3 Incident Responder
+#### 2.3 Incident Responder
 
 **Goal:** Handle attacks while they are happening and minimise damage.
 
@@ -98,9 +118,9 @@ Role keywords:
 
 ---
 
-## 3. Investigation & Analysis Roles
+### 3. Investigation & Analysis Roles
 
-### 3.1 Digital Forensics Examiner
+#### 3.1 Digital Forensics Examiner
 
 **Goal:** Use digital evidence to understand what really happened.
 
@@ -122,7 +142,7 @@ Role keywords:
 
 ---
 
-### 3.2 Malware Analyst
+#### 3.2 Malware Analyst
 
 **Goal:** Understand how malicious software works and how to detect/stop it.
 
@@ -141,9 +161,9 @@ Role keywords:
 
 ---
 
-## 4. Offensive & Adversarial Roles
+### 4. Offensive & Adversarial Roles
 
-### 4.1 Penetration Tester
+#### 4.1 Penetration Tester
 
 **Goal:** Legally attack systems to find vulnerabilities before criminals do.
 
@@ -168,7 +188,7 @@ Role keywords:
 
 ---
 
-### 4.2 Red Teamer
+#### 4.2 Red Teamer
 
 **Goal:** Emulate real-world threat actors to test detection and response capabilities.
 
@@ -197,7 +217,7 @@ Role keywords:
 
 ---
 
-## 5. How These Roles Connect (Mental Map)
+### 5. How These Roles Connect (Mental Map)
 
 You can think of an organisation’s security function as a loop:
 
@@ -223,7 +243,7 @@ For a personal career path, common entry points are:
 
 ---
 
-## 6. Personal Notes / Planning Hooks
+### 6. Personal Notes / Planning Hooks
 
 Some questions to help align this with my own path:
 
@@ -238,7 +258,7 @@ Some questions to help align this with my own path:
 
 ---
 
-## 7. Glossary (EN–ZH)
+### 7. Glossary (EN–ZH)
 
 - **Security Analyst** – 安全分析师  
 - **Security Engineer** – 安全工程师