diff --git a/README.md b/README.md
index 8ed2ee8..77d4b45 100644
--- a/README.md
+++ b/README.md
@@ -15,16 +15,15 @@ Microsoft GitHub (and RIAA) should have known better — not least because [
  - https://git.nixnet.xyz/Amolith/NewPipe
  - https://code.loranger.xyz/rob/NewPipe
  
-[Here's another source of mirror links](https://docs.nixnet.services/Mirror_lists), for good measure. And, you can still clone the original repo using:
+[Here's another source of mirror links](https://docs.nixnet.services/Mirror_lists), for good measure.
 
+Now, *hilariously* GitHub also [decided not to fix a potential security issue related to how repository forks are kept on the back-end](https://iain.learmonth.me/blog/2019/2019w371/). This makes it possible to make it seem like an upstream repo contains content that has never actually been merged into it.
+
+In other words, GitHub has no issue with [`youtube-dl` seemingly hosted in GitHub's own DMCA repository](https://github.com/github/dmca/tree/416da574ec0df3388f652e44f7fe71b1e3a4701f).  And so, you can still clone the original `youtube-dl` code using GitHub's own DMCA repo (the irony is just too sweet):
 ```
 git clone -n https://github.com/github/dmca.git youtube-dl && cd youtube-dl && git fetch origin 416da574ec0df3388f652e44f7fe71b1e3a4701f && git checkout FETCH_HEAD
 ```
 
-Now, *hilariously* GitHub also [decided not to fix a potential security issue related to how repository forks are kept on the back-end](https://iain.learmonth.me/blog/2019/2019w371/). This makes it possible to make it seem like an upstream repo contains content that never actually ended up in it.
-
-In other words, GitHub has no issue with [`youtube-dl` seemingly hosted in GitHub's own DMCA repository](https://github.com/github/dmca/tree/416da574ec0df3388f652e44f7fe71b1e3a4701f).
-
 ## Better alternatives
 
  - [SourceHut](https://sr.ht/) is a nice, ethical forge.