M contents/mn.md → contents/mn.md

@@ -28,9 +28,3 @@ 
 I tried to add compilation variants to reduce the modules to include but that made it more difficult to maintain and still included complex constructs like dictionaries and the full type system, so one day I decided to... fork it! And that's how mn was born.
 
 Is mn the *successor* of min? No! As I said, it is min's little brother, and it has its own (somewhat more minimalist) life. If you want to create a quick script to glue some shell commands together, then mn is definitely the fastest way to do so. If you want to use the concatenative paradigm to create more complex applications, then min comes with a much bigger toolbox.
-
-### Downloads
-
-* [macOS (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_macosx_x64.zip)
-* [Linux (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_linux_x64.zip)
-* [Windows (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_windows_x64.zip)

M contents/nimhttpd.md → contents/nimhttpd.md

@@ -25,9 +25,3 @@ * _port_ is the port to listen to (default: 1337). If the specified port is
   unavailable, the number will be incremented until an available port is found.
 * _address_ is the address to bind to (default: 0.0.0.0).
 * _title_ is the title to use when listing the contents of a directory.
-
-### Downloads
-
-* [macOS (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_macosx_x64.zip)
-* [Linux (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_linux_x64.zip)
-* [Windows (x64)]({{$download}}v{{$version}}/{{$github}}_v{{$version}}_windows_x64.zip)