fix more links

syllabus/0-Miscellaneous/0-Security/0-overview_slides.md

@@ -87,7 +87,7 @@ Notes:
 - https://bravenewcoin.com/insights/cryptopia-exchange-liquidator-releases-third-report
 - https://elementus.io/blog/cryptopia-hack-transparency/
 - https://blog.merklescience.com/hacktrack/hack-track-eterbase-cryptocurrency-exchange
-- https://www.reuters.com/investigates/special-report/fintech-crypto-binance-dirtymoney/
+- https://www.reuters.com/investigates/special-report/fintech-crypto-binance-dirtymoney/ <!-- markdown-link-check-disable-line -->
 
 ---
 

syllabus/0-Miscellaneous/0-Security/3-infra-security_slides.md

@@ -117,7 +117,7 @@ Some company offered a prize for reading ToS till the end, by placing an easter
 
 <img rounded style="width: 1400px" data-src="./img/3-infra-security/2-hetzner.png" />
 
-[Web source: Reddit](https://www.reddit.com/r/hetzner/comments/wucxs4/comment/ilfoj8u/)
+[Web source: Reddit](https://www.reddit.com/r/hetzner/comments/wucxs4/comment/ilfoj8u/) <!-- markdown-link-check-disable-line -->
 
 Notes:
 

syllabus/5-Substrate/1-Intro-to-Substrate_Slides.md

@@ -971,7 +971,7 @@ Notes:
 - An interesting question on JVM/Wasm: https://stackoverflow.com/questions/58131892/why-the-jvm-cannot-be-used-in-place-of-webassembly
 
 - Rust safety: https://stanford-cs242.github.io/f18/lectures/05-1-rust-memory-safety.html
-- https://www.reddit.com/r/rust/comments/5y3cxb/how_many_security_exploits_would_rust_prevent/
+- https://www.reddit.com/r/rust/comments/5y3cxb/how_many_security_exploits_would_rust_prevent/ <!-- markdown-link-check-disable-line -->
 
 - The substrate clients should still have some level of _determinism in their performance_. If
   authority nodes have extremely varied performances, they could start finalizing different forks.

syllabus/7-Polkadot/Blockchain_Scaling_Part_2/Blockchain_Scaling_Slides.md

@@ -72,8 +72,8 @@ https://www.starknet.io/en/posts/developers/rollup-validium-volition-where-is-yo
 
 Notes:
 
-- https://celestia.org/learn/sovereign-rollups/an-introduction/
-- https://rollkit.dev/blog/sovereign-rollups-on-bitcoin#sovereign-rollups-on-bitcoin-with-rollkit
+- https://celestia.org/learn/sovereign-rollups/an-introduction/ <!-- markdown-link-check-disable-line -->
+- https://rollkit.dev/blog/sovereign-rollups-on-bitcoin/
 
 ---
 
@@ -164,7 +164,7 @@ Notes:
 
 Notes:
 
-- https://docs.celestia.org/concepts/how-celestia-works/data-availability-layer/ <!-- markdown-link-check-disable-line -->
+- https://docs.celestia.org/concepts/how-celestia-works/data-availability-layer/
 
 ---
 
@@ -216,7 +216,7 @@ Notes:
 - Proposers post a state root to L1 with deposit
 - Challengers can submit fraud proofs within period (typically 7 days)
   - If successful, rewarded portion of deposit
-- Fraud proofs can be interactive (Arbitrum) or non-interactive (Optimism)
+- Fraud proofs can be interactive (Arbitrum) or noninteractive (Optimism)
 
 Notes:
 
@@ -306,7 +306,7 @@ Notes:
 
 ## How Does Polkadot Compare to Other Rollup Protocols?
 
-<img rounded style="width: 700px" src="../../../assets/img/7-Polkadot/Blockchain_Scaling/polkadot-rollup.png" />
+<img rounded style="width: 700px" src="../../../assets/img/7-Polkadot/Blockchain_Scaling/polkadotrollup.png" />
 
 - Approval checking is a decentralized shared watchtower network
 - The value proposition of Polkadot is making consistent security assumptions across the modular stack