diff --git a/_posts/2014-01-27-Cubieboard2-supported-platform.markdown b/_posts/2014-01-27-Cubieboard2-supported-platform.markdown
index 83203d8..79a3aa6 100644
--- a/_posts/2014-01-27-Cubieboard2-supported-platform.markdown
+++ b/_posts/2014-01-27-Cubieboard2-supported-platform.markdown
@@ -19,4 +19,4 @@ The Cubieboard2 is a small low-cost device with the following specifications:
  - 1x IR, 1x line in, 1x line out
  - 96 extend pin interface, including I2C, SPI, RGB/LVDS, CSI/TS, FM-IN, ADC, CVBS, VGA, SPDIF-OUT, R-TP, and more
 
-You can find the image for 2GB SD cards and the rootfs in the [downloads section](http://voidlinux.eu/download/)
+You can find the image for 2GB SD cards and the rootfs in the [downloads section](http://voidlinux.org/download/)
diff --git a/_posts/2014-01-27-Odroid-u2-and-u3-supported-platform.markdown b/_posts/2014-01-27-Odroid-u2-and-u3-supported-platform.markdown
index d0b610f..4d25252 100644
--- a/_posts/2014-01-27-Odroid-u2-and-u3-supported-platform.markdown
+++ b/_posts/2014-01-27-Odroid-u2-and-u3-supported-platform.markdown
@@ -23,4 +23,4 @@ The Odroid U2/U3 are small low-cost devices with the following specifications:
 - Storage Slot 	Micro-SD slot, eMMC module connector
 - DC Input 5V / 2A input, Plug specification is inner diameter 0.8mm and outer diameter 2.5mm
 
-You can find the image for 2GB SD cards and the rootfs in the [downloads section](http://voidlinux.eu/download/)
+You can find the image for 2GB SD cards and the rootfs in the [downloads section](http://voidlinux.org/download/)
diff --git a/_posts/2014-02-01-New-official-repos.markdown b/_posts/2014-02-01-New-official-repos.markdown
index d5f8d1d..40b0dfc 100644
--- a/_posts/2014-02-01-New-official-repos.markdown
+++ b/_posts/2014-02-01-New-official-repos.markdown
@@ -12,7 +12,7 @@ XBPS 0.31 already contains the updated xbps.conf file with the new repository lo
 
 The URLs for the new repositories are the following:
 
-- http://repo.voidlinux.eu/current
-- http://repo.voidlinux.eu/current/nonfree
+- http://repo.voidlinux.org/current
+- http://repo.voidlinux.org/current/nonfree
 
 Happy xbps'ing!
diff --git a/_posts/2014-03-06-Steam-for-x86_64.markdown b/_posts/2014-03-06-Steam-for-x86_64.markdown
index 8751497..576f6d8 100644
--- a/_posts/2014-03-06-Steam-for-x86_64.markdown
+++ b/_posts/2014-03-06-Steam-for-x86_64.markdown
@@ -15,7 +15,7 @@ To install and run steam with Void on x86\_64, follow these steps:
 
 Uncomment the *nonfree* repository from `/etc/xbps/xbps.conf`:
 
-    http://repo.voidlinux.eu/current/nonfree
+    http://repo.voidlinux.org/current/nonfree
 
 And then install steam and required 32bit packages:
 
diff --git a/_posts/2014-04-01-void-is-dead.markdown b/_posts/2014-04-01-void-is-dead.markdown
index 2278995..273cf2d 100644
--- a/_posts/2014-04-01-void-is-dead.markdown
+++ b/_posts/2014-04-01-void-is-dead.markdown
@@ -14,7 +14,7 @@ that is not a fork and has been created exclusively by one human (Juan RP), that
 is able to cross compile, supports multiple C libraries (glibc and musl),
 supports build options, debugging packages, subpackages, contains GNOME 3.12 before
 any other distribution, multiple Linux kernel packages (3.10, 3.12, 3.13, 3.14),
-and uses [buildbot](http://build.voidlinux.eu:8010/) to build them in real time.
+and uses [buildbot](http://build.voidlinux.org:8010/) to build them in real time.
 
 Thanks for all your support, and enjoy your life. You can still use other distributions
 such as [Biebian](http://biebian.sourceforge.net/), which contains genuine features:
diff --git a/_posts/2014-05-05-New-repositories.markdown b/_posts/2014-05-05-New-repositories.markdown
index b69a347..99f5a5b 100644
--- a/_posts/2014-05-05-New-repositories.markdown
+++ b/_posts/2014-05-05-New-repositories.markdown
@@ -17,9 +17,9 @@ meaningful for 64bit platforms.
 
 The URL for those repositories:
 
-- http://repo.voidlinux.eu/current/multilib
-- http://repo.voidlinux.eu/current/multilib/nonfree
-- http://repo.voidlinux.eu/current/debug
+- http://repo.voidlinux.org/current/multilib
+- http://repo.voidlinux.org/current/multilib/nonfree
+- http://repo.voidlinux.org/current/debug
 
 Also available on any of the mirrors listed in the `xbps.conf` configuration file.
 
diff --git a/_posts/2014-12-03-Live-flavours.markdown b/_posts/2014-12-03-Live-flavours.markdown
index f757133..6e34c8c 100644
--- a/_posts/2014-12-03-Live-flavours.markdown
+++ b/_posts/2014-12-03-Live-flavours.markdown
@@ -13,14 +13,14 @@ various Desktop Environments for testing. Those images are also known as `flavou
 
 Those images are generated automatically with the `void-mklive` script in 5 minutes
 and will be created periodically with updated packages thanks to our continuous
-package building available at [http://build.voidlinux.eu](http://build.voidlinux.eu).
+package building available at [http://build.voidlinux.org](http://build.voidlinux.org).
 
 The attached screenshot is my desktop with three `flavours` running at the same
 time via `QEMU`:
 
 [![xtraeme desktop](/assets/screenshots/live-flavours.jpg "xtraeme desktop")](/assets/screenshots/live-flavours.jpg)
 
-Check the [downloads](http://www.voidlinux.eu/download/) section to grab them!
+Check the [downloads](http://www.voidlinux.org/download/) section to grab them!
 
 Don't forget to help us improving `Void` with your donations and/or contributions
 to the `wiki`, `void-packages` or any available repository.
diff --git a/_posts/2014-12-05-BeagleBone.markdown b/_posts/2014-12-05-BeagleBone.markdown
index c535115..2bf7ffe 100644
--- a/_posts/2014-12-05-BeagleBone.markdown
+++ b/_posts/2014-12-05-BeagleBone.markdown
@@ -13,7 +13,7 @@ to `void-packages` and `void-mklive` to generate the base platform package `beag
 As any other supported ARM platform, once booted, `dhcpcd`, `ntpd` and `sshd` are started
 automatically to be able to connect to it via `ssh` (log in as `root`, password `voidlinux`).
 
-Check the [downloads](http://www.voidlinux.eu/download/) section to grab them!
+Check the [downloads](http://www.voidlinux.org/download/) section to grab them!
 
 - [http://en.wikipedia.org/wiki/BeagleBoard#BeagleBone](http://en.wikipedia.org/wiki/BeagleBoard#BeagleBone)
 - [http://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black](http://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black)
diff --git a/_posts/2015-02-21-New-x86-images.markdown b/_posts/2015-02-21-New-x86-images.markdown
index 260503a..93c3a98 100644
--- a/_posts/2015-02-21-New-x86-images.markdown
+++ b/_posts/2015-02-21-New-x86-images.markdown
@@ -19,4 +19,4 @@ problem to update it.
 Additionally there's now a new flavour containing the latest [Cinnamon](http://cinnamon.linuxmint.com/)
 Desktop Environment.
 
-Check out the [Download](http://www.voidlinux.eu/download/) section to grab them.
+Check out the [Download](http://www.voidlinux.org/download/) section to grab them.
diff --git a/_posts/2015-02-22-Raspberry-Pi-2.markdown b/_posts/2015-02-22-Raspberry-Pi-2.markdown
index f41c173..6abb0df 100644
--- a/_posts/2015-02-22-Raspberry-Pi-2.markdown
+++ b/_posts/2015-02-22-Raspberry-Pi-2.markdown
@@ -13,4 +13,4 @@ to `void-packages` and `void-mklive` to generate a working rootfs/image.
 As any other supported ARM platform, once booted, `dhcpcd`, `ntpd` and `sshd` are started
 automatically to be able to connect to it via `ssh` (log in as `root`, password `voidlinux`).
 
-Check the [downloads](http://www.voidlinux.eu/download/) section to grab them!
+Check the [downloads](http://www.voidlinux.org/download/) section to grab them!
diff --git a/_posts/2015-04-29-USB-armory.markdown b/_posts/2015-04-29-USB-armory.markdown
index 9c4683c..0e54a76 100644
--- a/_posts/2015-04-29-USB-armory.markdown
+++ b/_posts/2015-04-29-USB-armory.markdown
@@ -23,6 +23,6 @@ Then log in using ssh:
 
 The default password is ```voidlinux```
 
-Check the [downloads](http://www.voidlinux.eu/download/) section to grab them!
+Check the [downloads](http://www.voidlinux.org/download/) section to grab them!
 
 - [http://inversepath.com/usbarmory](http://inversepath.com/usbarmory)
diff --git a/_posts/2015-06-15-New-images.markdown b/_posts/2015-06-15-New-images.markdown
index ce2a636..14c1fdd 100644
--- a/_posts/2015-06-15-New-images.markdown
+++ b/_posts/2015-06-15-New-images.markdown
@@ -26,4 +26,4 @@ Our list of supported ARM platforms continues growing:
 - RaspberryPi 2
 - USB Armory
 
-You can find all images and rootfs tarballs at [http://repo.voidlinux.eu/live/current](http://repo.voidlinux.eu/live/current)
+You can find all images and rootfs tarballs at [http://repo.voidlinux.org/live/current](http://repo.voidlinux.org/live/current)
diff --git a/_posts/2015-11-10-forum-wiki-announcement.markdown b/_posts/2015-11-10-forum-wiki-announcement.markdown
index ad13e36..d3e7fa6 100644
--- a/_posts/2015-11-10-forum-wiki-announcement.markdown
+++ b/_posts/2015-11-10-forum-wiki-announcement.markdown
@@ -9,12 +9,12 @@ For a while now we have used github for our wiki. We wanted to make contributing
 to the wiki easier, and be able to make it look better. Since most users are
 familiar with [mediawiki](https://www.mediawiki.org/wiki/MediaWiki) that is
 what we went with. All of the existing content was imported into the new wiki,
-and it is live at [wiki.voidlinux.eu](https://wiki.voidlinux.eu). Searching and
+and it is live at [wiki.voidlinux.org](https://wiki.voidlinux.org). Searching and
 organization should be improved from the github experience. We look forward to
 seeing new contributors and your feedback.
 
 We are also taking this time to announce our new
-[forums](https://forum.voidlinux.eu). We hope to build a community here, users
+[forums](https://forum.voidlinux.org). We hope to build a community here, users
 can share screenshots, talk about their Void Linux setups, ask questions, and
 more.
 
diff --git a/_posts/2016-08-31-Tor-Hidden-Service.markdown b/_posts/2016-08-31-Tor-Hidden-Service.markdown
index fd749d0..4a9cb17 100644
--- a/_posts/2016-08-31-Tor-Hidden-Service.markdown
+++ b/_posts/2016-08-31-Tor-Hidden-Service.markdown
@@ -1,6 +1,6 @@
 ---
 layout: post
-title: "We Love Your Privacy: repo.voidlinux.eu as tor hidden service"
+title: "We Love Your Privacy: repo.voidlinux.org as tor hidden service"
 comments: true
 ---
 
@@ -8,9 +8,9 @@ The Void Linux Community is pleased to announce that our main repository- and bu
 
 The onion addresses are:
 
-* [repo.voidlinux.eu](https://repo.voidlinux.eu):  
+* [repo.voidlinux.org](https://repo.voidlinux.org):  
   onion address: [fd6dqrupy3af4xwb.onion](http://fd6dqrupy3af4xwb.onion)
-* [build.voidlinux.eu](https://build.voidlinux.eu):  
+* [build.voidlinux.org](https://build.voidlinux.org):  
   onion address: [http://s7y2awkwau4nbdpu.onion](http://s7y2awkwau4nbdpu.onion)
 
 Feel free to test the onion addresses with xbps:
diff --git a/_posts/2016-09-17-aarch64-support.markdown b/_posts/2016-09-17-aarch64-support.markdown
index 5f2d302..2d6d06a 100644
--- a/_posts/2016-09-17-aarch64-support.markdown
+++ b/_posts/2016-09-17-aarch64-support.markdown
@@ -24,7 +24,7 @@ first installable image was prepared and ran on native hardware.
 In September 2016, a virtual machine was dedicated to be the official
 aarch64 cross-builder, and now packages are officially provided (both
 for glibc and musl)---so far in the seperate repository:
-https://repo.voidlinux.eu/current/aarch64.
+https://repo.voidlinux.org/current/aarch64.
 
 We are still looking for [powerful native aarch64
 hardware](https://twitter.com/clandmeter/status/766215821257543680) to
diff --git a/_posts/2017-07-13-wiki-cleanup.markdown b/_posts/2017-07-13-wiki-cleanup.markdown
index f48f665..0d98f27 100644
--- a/_posts/2017-07-13-wiki-cleanup.markdown
+++ b/_posts/2017-07-13-wiki-cleanup.markdown
@@ -6,5 +6,5 @@ comments: true
 
 ![I don't like spam](https://media.giphy.com/media/VEN5MTs0yhr2/giphy.gif)
 
-We're going to clean up our wiki from spammers. Please contact us via [twitter](https://twitter.com/voidlinux) or the [forum](https://forum.voidlinux.eu)
+We're going to clean up our wiki from spammers. Please contact us via [twitter](https://twitter.com/voidlinux) or the [forum](https://forum.voidlinux.org)
 if you're accidentally blocked.
diff --git a/_posts/2017-12-01-advent-gcal.markdown b/_posts/2017-12-01-advent-gcal.markdown
index 00d1c44..eaa2221 100644
--- a/_posts/2017-12-01-advent-gcal.markdown
+++ b/_posts/2017-12-01-advent-gcal.markdown
@@ -13,7 +13,7 @@ The first tool is `gcal`, a "a program for calculating and printing
 calendars", because we need to prepare our advent calendar, right?
 
 gcal is the GNU version of the trusty old
-[cal(1)](https://man.voidlinux.eu/cal.1), but that description doesn't
+[cal(1)](https://man.voidlinux.org/cal.1), but that description doesn't
 do it justice because it's probably one of the most powerful and
 flexible calendaring tools, supporting many different calendars and
 astronomical data.
@@ -97,6 +97,6 @@ Sun,  Dec 24th 2017:            (        @@@@@
 
 gcal also has good support for *resource files*, where you can
 configure your own holidays, dates and reminders (replacing many uses
-of [calendar(1)](https://man.voidlinux.eu/calendar.1] or
-[when(1)](https://man.voidlinux.eu/when.1)).  I recommend you to check
+of [calendar(1)](https://man.voidlinux.org/calendar.1] or
+[when(1)](https://man.voidlinux.org/when.1)).  I recommend you to check
 out the extensive info manual.
diff --git a/_posts/2017-12-03-advent-ministat.markdown b/_posts/2017-12-03-advent-ministat.markdown
index 69fc7ae..d8a3656 100644
--- a/_posts/2017-12-03-advent-ministat.markdown
+++ b/_posts/2017-12-03-advent-ministat.markdown
@@ -5,15 +5,15 @@ comments: true
 ---
 
 On day 3 we introduce you to the small statistics tool
-[ministat(1)](https://man.voidlinux.eu/ministat.1) that originates
+[ministat(1)](https://man.voidlinux.org/ministat.1) that originates
 from FreeBSD.
 
 When we sling around data on the command line, sometimes we want to
 compute some basic statistics on it.  While minimum, average and
 maximum are easily computed with
-[awk(1)](https://man.voidlinux.eu/awk.1), you probably forgot the
+[awk(1)](https://man.voidlinux.org/awk.1), you probably forgot the
 formula for more complicated statistics.  There is no need to pull out
-[R](https://man.voidlinux.eu/R.1) already, lets use ministat instead!
+[R](https://man.voidlinux.org/R.1) already, lets use ministat instead!
 
 For example, let's have a look at the
 [historical summer temperatures in Germany](ftp://ftp-cdc.dwd.de/pub/CDC/regional_averages_DE/seasonal/air_temperature_mean/regional_averages_tm_summer.txt).
@@ -45,7 +45,7 @@ the data distribution.  We have 137 measurements, and an average
 temperature of 16.1°C.
 
 To compare multiple datasets, we need to pass them as multiple input files.
-Luckily, [our shell](https://man.voidlinux.eu/zsh.1) has process substitution.
+Luckily, [our shell](https://man.voidlinux.org/zsh.1) has process substitution.
 Let's match the Bavarian measurements with the German average:
 
 ```
diff --git a/_posts/2017-12-04-advent-containers.markdown b/_posts/2017-12-04-advent-containers.markdown
index 9533e40..cfb71ab 100644
--- a/_posts/2017-12-04-advent-containers.markdown
+++ b/_posts/2017-12-04-advent-containers.markdown
@@ -19,10 +19,10 @@ The `containers` package leverages the same kernel features as Docker and LXC, b
 To setup a small void container we run `xbps-install` with `pseudo` to populate a directory with a base system where files that are usually owned by root are owned by our user outside the namespace. Inside the namespace they will appear as if those files are owned by root.
 
 ```
-$ pseudo xbps-install -R https://repo.voidlinux.eu/current/ -MSr /tmp/void base-voidstrap
-[*] Updating `https://repo.voidlinux.eu/current//armv7l-repodata' ...
+$ pseudo xbps-install -R https://repo.voidlinux.org/current/ -MSr /tmp/void base-voidstrap
+[*] Updating `https://repo.voidlinux.org/current//armv7l-repodata' ...
 armv7l-repodata: 1140KB [avg rate: 9126MB/s]
-`https://repo.voidlinux.eu/current/' repository has been RSA signed by "Void Linux"
+`https://repo.voidlinux.org/current/' repository has been RSA signed by "Void Linux"
 Fingerprint: 60:ae:0c:d6:f0:95:17:80:bc:93:46:7a:89:af:a3:2d
 Do you want to import this public key? [Y/n] y
 
@@ -111,7 +111,7 @@ bash-4.4# ip link
 bash-4.4# sv s /var/service/*
 run: /var/service/udevd: (pid 41) 61s
 bash-4.4# xbps-install -Su
-[*] Updating `https://repo.voidlinux.eu/current/armv7l-repodata' ...
+[*] Updating `https://repo.voidlinux.org/current/armv7l-repodata' ...
 bash-4.4# ps auxf
 USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
 root        43  0.0  0.2   3136  2556 ?        S    16:43   0:00 /bin/bash
diff --git a/_posts/2017-12-05-advent-perl-Math-Prime-Util.markdown b/_posts/2017-12-05-advent-perl-Math-Prime-Util.markdown
index be226c0..adb4c2e 100644
--- a/_posts/2017-12-05-advent-perl-Math-Prime-Util.markdown
+++ b/_posts/2017-12-05-advent-perl-Math-Prime-Util.markdown
@@ -5,7 +5,7 @@ comments: true
 ---
 
 Folks that enjoy playing with numbers and riddles probably know
-[factor(1)](https://man.voidlinux.eu/factor.1), a small tool of
+[factor(1)](https://man.voidlinux.org/factor.1), a small tool of
 coreutils to factorize a number:
 
 ```
@@ -28,7 +28,7 @@ This works pretty well for numbers up to a certain size, but trying to
 check a 160-bit prime already takes a few seconds.
 
 Luckily, there is
-[Math::Prime::Util](https://man.voidlinux.eu/Math::Prime::Util),
+[Math::Prime::Util](https://man.voidlinux.org/Math::Prime::Util),
 a Perl library consisting of "utilities related to prime numbers,
 including fast sieves and factoring".  And it also contains two
 command line tools `primes.pl` and `factor.pl`, which are far more
diff --git a/_posts/2017-12-06-advent-jq.markdown b/_posts/2017-12-06-advent-jq.markdown
index f33a086..55b7936 100644
--- a/_posts/2017-12-06-advent-jq.markdown
+++ b/_posts/2017-12-06-advent-jq.markdown
@@ -5,7 +5,7 @@ comments: true
 ---
 
 Day 6! Today we want to get some pseudo modern web technology in the game.
-[jq(1)](https://man.voidlinux.eu/jq.1) is a commandline tool that allows to query and manipulate JSON documents
+[jq(1)](https://man.voidlinux.org/jq.1) is a commandline tool that allows to query and manipulate JSON documents
 and is great to use with shell scripts.
 
 Let's get started with this simple JSON document:
@@ -14,8 +14,8 @@ Let's get started with this simple JSON document:
 {
  "title" : "The Advent of Void: Day 4: containers",
  "pubDate" : "2017-12-04 00:00:00",
- "link" : "http://voidlinux.eu/news/2017/12/advent-containers.html",
- "guid" : "http://voidlinux.eu/news/2017/12/advent-containers"
+ "link" : "http://voidlinux.org/news/2017/12/advent-containers.html",
+ "guid" : "http://voidlinux.org/news/2017/12/advent-containers"
 }
 ```
 
@@ -46,27 +46,27 @@ That's quite helpful. But the real power of jq comes to light once we work with
 ```json
 [
   {
-     "guid" : "http://voidlinux.eu/news/2017/12/advent-containers",
+     "guid" : "http://voidlinux.org/news/2017/12/advent-containers",
      "pubDate" : "2017-12-04 00:00:00",
-     "link" : "http://voidlinux.eu/news/2017/12/advent-containers.html",
+     "link" : "http://voidlinux.org/news/2017/12/advent-containers.html",
      "title" : "The Advent of Void: Day 4: containers"
   },
   {
-     "link" : "http://voidlinux.eu/news/2017/12/advent-ministat.html",
+     "link" : "http://voidlinux.org/news/2017/12/advent-ministat.html",
      "title" : "The Advent of Void: Day 3: ministat",
-     "guid" : "http://voidlinux.eu/news/2017/12/advent-ministat",
+     "guid" : "http://voidlinux.org/news/2017/12/advent-ministat",
      "pubDate" : "2017-12-03 00:00:00"
   },
   {
-     "link" : "http://voidlinux.eu/news/2017/12/advent-taskwarrior.html",
+     "link" : "http://voidlinux.org/news/2017/12/advent-taskwarrior.html",
      "title" : "The Advent of Void: Day 2: taskwarrior and friends",
      "pubDate" : "2017-12-02 00:00:00",
-     "guid" : "http://voidlinux.eu/news/2017/12/advent-taskwarrior"
+     "guid" : "http://voidlinux.org/news/2017/12/advent-taskwarrior"
   },
   {
-     "link" : "http://voidlinux.eu/news/2017/12/advent-gcal.html",
+     "link" : "http://voidlinux.org/news/2017/12/advent-gcal.html",
      "title" : "The Advent of Void: Day 1: gcal",
-     "guid" : "http://voidlinux.eu/news/2017/12/advent-gcal",
+     "guid" : "http://voidlinux.org/news/2017/12/advent-gcal",
      "pubDate" : "2017-12-01 00:00:00"
   }
 ]
@@ -78,13 +78,13 @@ Our first step is to extract them both from the document:
 ```
 # jq -r '.[] | ( .title, .link )' file.json
 The Advent of Void: Day 4: containers
-http://voidlinux.eu/news/2017/12/advent-containers.html
+http://voidlinux.org/news/2017/12/advent-containers.html
 The Advent of Void: Day 3: ministat
-http://voidlinux.eu/news/2017/12/advent-ministat.html
+http://voidlinux.org/news/2017/12/advent-ministat.html
 The Advent of Void: Day 2: taskwarrior and friends
-http://voidlinux.eu/news/2017/12/advent-taskwarrior.html
+http://voidlinux.org/news/2017/12/advent-taskwarrior.html
 The Advent of Void: Day 1: gcal
-http://voidlinux.eu/news/2017/12/advent-gcal.html
+http://voidlinux.org/news/2017/12/advent-gcal.html
 ```
 
 That's all that's needed to query the information. To format the output we need to generate an array from every article:
@@ -93,19 +93,19 @@ That's all that's needed to query the information. To format the output we need
 # jq -r '.[] | [.title, .link ]' json
 [
   "The Advent of Void: Day 4: containers",
-  "http://voidlinux.eu/news/2017/12/advent-containers.html"
+  "http://voidlinux.org/news/2017/12/advent-containers.html"
 ]
 [
   "The Advent of Void: Day 3: ministat",
-  "http://voidlinux.eu/news/2017/12/advent-ministat.html"
+  "http://voidlinux.org/news/2017/12/advent-ministat.html"
 ]
 [
   "The Advent of Void: Day 2: taskwarrior and friends",
-  "http://voidlinux.eu/news/2017/12/advent-taskwarrior.html"
+  "http://voidlinux.org/news/2017/12/advent-taskwarrior.html"
 ]
 [
   "The Advent of Void: Day 1: gcal",
-  "http://voidlinux.eu/news/2017/12/advent-gcal.html"
+  "http://voidlinux.org/news/2017/12/advent-gcal.html"
 ]
 ```
 
@@ -113,10 +113,10 @@ Now as a last step join the arrays using the tab character:
 
 ```
 # jq -r '.[] | [.title, .link ] | join("\t")' file.json
-The Advent of Void: Day 4: containers    http://voidlinux.eu/news/2017/12/advent-containers.html
-The Advent of Void: Day 3: ministat http://voidlinux.eu/news/2017/12/advent-ministat.html
-The Advent of Void: Day 2: taskwarrior and friends    http://voidlinux.eu/news/2017/12/advent-taskwarrior.html
-The Advent of Void: Day 1: gcal http://voidlinux.eu/news/2017/12/advent-gcal.html
+The Advent of Void: Day 4: containers    http://voidlinux.org/news/2017/12/advent-containers.html
+The Advent of Void: Day 3: ministat http://voidlinux.org/news/2017/12/advent-ministat.html
+The Advent of Void: Day 2: taskwarrior and friends    http://voidlinux.org/news/2017/12/advent-taskwarrior.html
+The Advent of Void: Day 1: gcal http://voidlinux.org/news/2017/12/advent-gcal.html
 ```
 
 All in all jq is a quite powerful tool and we did only scratch the surface of
diff --git a/_posts/2017-12-07-advent-mosh.markdown b/_posts/2017-12-07-advent-mosh.markdown
index fe03403..31fcde7 100644
--- a/_posts/2017-12-07-advent-mosh.markdown
+++ b/_posts/2017-12-07-advent-mosh.markdown
@@ -7,12 +7,12 @@ comments: true
 Accessing a remote server over an unstable or high latency connection ... can
 be ... a tedious ``CONNECTION TIMEOUT`` ... ``RECONNECT`` task.
 
-[mosh(1)](https://man.voidlinux.eu/mosh.1) stands for MObile SHell and provides
+[mosh(1)](https://man.voidlinux.org/mosh.1) stands for MObile SHell and provides
 a reliable command line connection that outlives network outages and roaming
 between different networks.
 
 The usage of mosh is pretty easy. On un-firewalled hosts just make sure the
-remote server runs an [sshd(8)](https://man.voidlinux.eu/sshd) deamon and
+remote server runs an [sshd(8)](https://man.voidlinux.org/sshd) deamon and
 has mosh installed. Then connecting to the server is as easy as:
 
 ```
diff --git a/_posts/2017-12-09-advent-zutils.markdown b/_posts/2017-12-09-advent-zutils.markdown
index 35b6003..9eabcbc 100644
--- a/_posts/2017-12-09-advent-zutils.markdown
+++ b/_posts/2017-12-09-advent-zutils.markdown
@@ -33,7 +33,7 @@ Luckily, there are the `zutils`, which provide some compression-aware
 general purpose Unix tools.  In Void Linux, they use a capital `Z` as
 command prefix, to avoid name clashes.
 
-[Zcat(1)](https://man.voidlinux.eu/Zcat.1) will decompress all
+[Zcat(1)](https://man.voidlinux.org/Zcat.1) will decompress all
 supported file formats on the fly:
 
 ```
@@ -43,7 +43,7 @@ Sat Dec  9 18:37:12 CET 2017
 Sat Dec  9 18:37:24 CET 2017
 ```
 
-Very useful is [Zgrep(1)](https://man.voidlinux.eu/Zgrep.1) to search
+Very useful is [Zgrep(1)](https://man.voidlinux.org/Zgrep.1) to search
 in compressed files:
 
 ```
@@ -52,12 +52,12 @@ date.bz2:Sat Dec  9 18:37:20 CET 2017
 date.xz:Sat Dec  9 18:37:24 CET 2017
 ```
 
-In contrast to the [zgrep(1)](https://man.voidlinux.eu/zcat.1) script
+In contrast to the [zgrep(1)](https://man.voidlinux.org/zcat.1) script
 of `gzip`, it supports the `-r` flag to recurse into directories,
 which is very useful if you want to search in all files in `/var/log`
 for example.
 
-`zutils` also contains [Zcmp(1)](https://man.voidlinux.eu/Zcmp.1) and
-[Zdiff(1)](https://man.voidlinux.eu/Zdiff.1) to compare files to each
-other, and [Ztest](https://man.voidlinux.eu/Ztest.1) to verify files
+`zutils` also contains [Zcmp(1)](https://man.voidlinux.org/Zcmp.1) and
+[Zdiff(1)](https://man.voidlinux.org/Zdiff.1) to compare files to each
+other, and [Ztest](https://man.voidlinux.org/Ztest.1) to verify files
 are not corrupted.
diff --git a/_posts/2017-12-10-advent-dvtm.markdown b/_posts/2017-12-10-advent-dvtm.markdown
index 4372dd8..bfa4284 100644
--- a/_posts/2017-12-10-advent-dvtm.markdown
+++ b/_posts/2017-12-10-advent-dvtm.markdown
@@ -35,7 +35,7 @@ You know window managers, right? Like tiled window managers. There are plenty of
 
 
 
-[dvtm(1)](https://man.voidlinux.eu/dvtm.1) helps you to organize multiple shells
+[dvtm(1)](https://man.voidlinux.org/dvtm.1) helps you to organize multiple shells
 within the same screen without relying on such n00p-software as any form of
 graphical user interface.
 
@@ -61,4 +61,4 @@ by `V` followed by the tag digit.
 
 There are a lot more features in dvtm. You may read about them on the
 [dvtm website](http://www.brain-dump.org/projects/dvtm/#quickstart)
-or the [manpage](https://man.voidlinux.eu/dvtm.1)
+or the [manpage](https://man.voidlinux.org/dvtm.1)
diff --git a/_posts/2017-12-11-advent-fatrace.markdown b/_posts/2017-12-11-advent-fatrace.markdown
index 07f7a17..1106389 100644
--- a/_posts/2017-12-11-advent-fatrace.markdown
+++ b/_posts/2017-12-11-advent-fatrace.markdown
@@ -5,12 +5,12 @@ comments: true
 ---
 
 As a Linux user, you probably know how to use
-[strace(1)](https://man.voidlinux.eu/strace.1) to see what a
+[strace(1)](https://man.voidlinux.org/strace.1) to see what a
 *particular* process is doing.  However, getting a picture of what the
 whole system is doing is more difficult.
 
 If it's related to file access,
-[fatrace(1)](https://man.voidlinux.eu/fatrace.1) can be of great help
+[fatrace(1)](https://man.voidlinux.org/fatrace.1) can be of great help
 then.  fatrace uses the Linux fanotify API, which allows *global tracing*
 of all file operations.
 `CONFIG_FANOTIFY=y` is enabled on Void Linux by default.
diff --git a/_posts/2017-12-12-advent-xpra.markdown b/_posts/2017-12-12-advent-xpra.markdown
index 52bf24d..23c0e03 100644
--- a/_posts/2017-12-12-advent-xpra.markdown
+++ b/_posts/2017-12-12-advent-xpra.markdown
@@ -4,7 +4,7 @@ title: "The Advent of Void: Day 12: xpra"
 comments: true
 ---
 
-Here's our first tool using a GUI: [xpra(1)](https://man.voidlinux.eu/xpra.1) is
+Here's our first tool using a GUI: [xpra(1)](https://man.voidlinux.org/xpra.1) is
 a headless X-Server that allows remotely detaching and attaching its windows 
 from multiple platforms including X11, Windows, and Mac.
 
diff --git a/_posts/2017-12-13-advent-ncdu.markdown b/_posts/2017-12-13-advent-ncdu.markdown
index 7f031d1..4ec82a5 100644
--- a/_posts/2017-12-13-advent-ncdu.markdown
+++ b/_posts/2017-12-13-advent-ncdu.markdown
@@ -12,7 +12,7 @@ course, which recursively lists all files and aggregates sizes for
 directories.  But for a big disk, this results in a long, unwieldy and
 unfathomable list.
 
-[ncdu(1)](https://man.voidlinux.eu/ncdu.1) to the rescue!
+[ncdu(1)](https://man.voidlinux.org/ncdu.1) to the rescue!
 This ncurses program will display the disk usage data as a
 [nice menu](https://dev.yorhel.nl/ncdu/scr)
 that you can browse interactively; sorted by size of course.
diff --git a/_posts/2017-12-15-advent-an.markdown b/_posts/2017-12-15-advent-an.markdown
index 84a0a67..7c733c7 100644
--- a/_posts/2017-12-15-advent-an.markdown
+++ b/_posts/2017-12-15-advent-an.markdown
@@ -10,7 +10,7 @@ For example, ELVIS has the same letters as LIVES,
 and THE MORSE CODE has the same letters as HERE COMES DOTS.
 
 How can we find such anagrams? With our computer! Today, we'll use the tool
-[an(6)](https://man.voidlinux.eu/an.6) for that.
+[an(6)](https://man.voidlinux.org/an.6) for that.
 
 By default, it will list all anagrams it finds, with the longest word first:
 
diff --git a/_posts/2017-12-16-advent-pv.markdown b/_posts/2017-12-16-advent-pv.markdown
index 42f759e..dadd36f 100644
--- a/_posts/2017-12-16-advent-pv.markdown
+++ b/_posts/2017-12-16-advent-pv.markdown
@@ -4,7 +4,7 @@ title: "The Advent of Void: Day 16: pv"
 comments: true
 ---
 
-A tool with many uses is [pv(1)](https://man.voidlinux.eu/pv.1), the
+A tool with many uses is [pv(1)](https://man.voidlinux.org/pv.1), the
 'pipe viewer'.  Essentially, you can put it between any pipe and
 you'll see statistics on its throughput.
 
@@ -29,10 +29,10 @@ Or copy a whole disk to a remote host, with a progress bar:
 
 `pv` has a few nifty flags, for example, it also can count
 *lines* instead of bytes.  So we can build a progress bar for
-a [find](https://man.voidlinux.eu/find.1)/[xargs](https://man.voidlinux.eu/xargs.1) call
+a [find](https://man.voidlinux.org/find.1)/[xargs](https://man.voidlinux.org/xargs.1) call
 (or rather,
-[lr](https://man.voidlinux.eu/lr.1)/
-[xe](https://man.voidlinux.eu/xe.1)):
+[lr](https://man.voidlinux.org/lr.1)/
+[xe](https://man.voidlinux.org/xe.1)):
 
 ```
 % find /tmp -name '*.png' | pv -l | xargs -P4 -n1 pngcrush -ow
diff --git a/_posts/2017-12-17-advent-dstat.markdown b/_posts/2017-12-17-advent-dstat.markdown
index 5280ccb..a3278ea 100644
--- a/_posts/2017-12-17-advent-dstat.markdown
+++ b/_posts/2017-12-17-advent-dstat.markdown
@@ -5,13 +5,13 @@ comments: true
 ---
 
 There are many ways to see what's going on your system, such as
-[top(1)](https://man.voidlinux.eu/top.1),
-[htop(1)](https://man.voidlinux.eu/htop.1),
-[atop(1)](https://man.voidlinux.eu/atop.1).  However, these tools only
+[top(1)](https://man.voidlinux.org/top.1),
+[htop(1)](https://man.voidlinux.org/htop.1),
+[atop(1)](https://man.voidlinux.org/atop.1).  However, these tools only
 show the current state of the system, and it's not so easy to see how
 the data changes.
 
-[dstat(1)](https://man.voidlinux.eu/dstat.1) works differently: it
+[dstat(1)](https://man.voidlinux.org/dstat.1) works differently: it
 prints a line every second with some system stats you can configure.
 By default, it shows CPU usage, disk I/O, network traffic, paging,
 and context switches:
diff --git a/_posts/2017-12-18-advent-mblaze.markdown b/_posts/2017-12-18-advent-mblaze.markdown
index 3c9d874..af4e388 100644
--- a/_posts/2017-12-18-advent-mblaze.markdown
+++ b/_posts/2017-12-18-advent-mblaze.markdown
@@ -4,7 +4,7 @@ title: "The Advent of Void: Day 18: mblaze"
 comments: true
 ---
 
-Today I want to introduce [mblaze(7)](https://man.voidlinux.eu/mblaze.7), a set of Unix utilities to deal with mails stored in the maildir format.
+Today I want to introduce [mblaze(7)](https://man.voidlinux.org/mblaze.7), a set of Unix utilities to deal with mails stored in the maildir format.
 
 It aims to be used for both interactive usage and scripting, similar to MH or nmh.
 Except that its `mblaze` was written from scratch to be performant and memory efficient allowing to work with large amounts of mails.
@@ -15,7 +15,7 @@ Sequences can be used in memory by using pipes or as files which enabled further
 
 There are tools to create, sort, filter and manipulate sequences, other tools like `mshow`, `maddr` or `magrep` use those sequences to gather, address or show specific mails from sequences.
 
-[mlist(1)](https://man.voidlinux.eu/mlist.1) creates the initial sequence, It takes mail directories as argument and prints out all the mails it can find, it also has some arguments to filter mails by flags that are stored in the file name, as example `-S` and `-s` to show only seen or not seen mails respectively.
+[mlist(1)](https://man.voidlinux.org/mlist.1) creates the initial sequence, It takes mail directories as argument and prints out all the mails it can find, it also has some arguments to filter mails by flags that are stored in the file name, as example `-S` and `-s` to show only seen or not seen mails respectively.
 
 ```
 $ mlist ~/mail/
@@ -30,8 +30,8 @@ $ mlist ~/mail/
 /home/duncan/mail/1505313797.1422_502.tux,U=41582:2,ST
 ```
 
-Most mails and MUAs work with mails in threads, `mblaze` has [mthread(1)](https://man.voidlinux.eu/mthread.1) to group the mails in a sequence into threads.
-To sort mails we use [msort(1)](https://man.voidlinux.eu/msort.1) which uses mail headers like `Date` or `Subject` to sort the sequence in the specified way.
+Most mails and MUAs work with mails in threads, `mblaze` has [mthread(1)](https://man.voidlinux.org/mthread.1) to group the mails in a sequence into threads.
+To sort mails we use [msort(1)](https://man.voidlinux.org/msort.1) which uses mail headers like `Date` or `Subject` to sort the sequence in the specified way.
 
 ```
 $ mlist ~/mail/ | mthread
@@ -62,8 +62,8 @@ $ mlist ~/mail/ | mthread | msort -d
 9 mails threaded
 ```
 
-To avoid creating and piping sequences every time we can use [mseq(1)](https://man.voidlinux.eu/mseq.1) to save and manipulate mail sequence files.
-If the sequence is stored as file the `mblaze` utilities can use the sequence from the file to address mails by index numbers and [mmsg(7)](https://man.voidlinux.eu/mmsg.7) selectors.
+To avoid creating and piping sequences every time we can use [mseq(1)](https://man.voidlinux.org/mseq.1) to save and manipulate mail sequence files.
+If the sequence is stored as file the `mblaze` utilities can use the sequence from the file to address mails by index numbers and [mmsg(7)](https://man.voidlinux.org/mmsg.7) selectors.
 
 ```
 $ mlist ~/mail/ | mthread | msort -d  | mseq -S
@@ -82,7 +82,7 @@ $ cat ~/.mblaze/seq
 /home/duncan/mail//1505402355.860_22.tux,U=41682:2,
 ```
 
-Now that the sequence is saved we can continue can use [mscan(1)](https://man.voidlinux.eu/mscan.1) a tool to print one line message lists including the subject, the date and a visual representation for the flags.
+Now that the sequence is saved we can continue can use [mscan(1)](https://man.voidlinux.org/mscan.1) a tool to print one line message lists including the subject, the date and a visual representation for the flags.
 
 ```
 $ mscan
@@ -102,7 +102,7 @@ $ mscan
 
 The first column is for flags, `x` is for Trashed mails, and `.` (dot) for unseen mails, the second column is the index of the mail in the sequence.
 
-`mscan` can use the previously mentioned [mmsg(7)](https://man.voidlinux.eu/mmsg.7) syntax to address or select mails.
+`mscan` can use the previously mentioned [mmsg(7)](https://man.voidlinux.org/mmsg.7) syntax to address or select mails.
 In this example the first one just addresses two mails by their index, the second example selects a range of mails starting and ending at the specified index.
 
 ```
@@ -118,14 +118,14 @@ $ mscan 2:5
 4 mails scanned
 ```
 
-The next tool is [mshow(1)](https://man.voidlinux.eu/mshow.1) which renders mails or extracts attachments.
+The next tool is [mshow(1)](https://man.voidlinux.org/mshow.1) which renders mails or extracts attachments.
 
 ```
 $ mshow 2
 From: gravicappa <notifications@github.com>
 Subject: Re: [voidlinux/void-packages] dmenu-4.7 doesn't allow cyrillic input (#7614)
 To: voidlinux/void-packages <void-packages@noreply.github.com>
-Cc: Duncan Overbruck <duncaen@voidlinux.eu>,  Comment <comment@noreply.github.com>
+Cc: Duncan Overbruck <duncaen@voidlinux.org>,  Comment <comment@noreply.github.com>
 Date: Sun, 10 Sep 2017 09:30:36 -0700 (14 weeks, 1 day, 1 hour ago)
 Reply-To: voidlinux/void-packages <reply+002aecdf7dfdc8d5ee7bc8a57eb08b436b6d3af844c59c4192cf0000000115cd2aac92a169ce0f49ca87@reply.github.com>
 
@@ -139,7 +139,7 @@ Reply to this email directly or view it on GitHub:
 https://github.com/voidlinux/void-packages/issues/7614#issuecomment-328354106
 ```
 
-[mless(1)](https://man.voidlinux.eu/mless.1) is a small wrapper around less that lets you page through your sequence.
+[mless(1)](https://man.voidlinux.org/mless.1) is a small wrapper around less that lets you page through your sequence.
 On the top it prints a few lines from `mscan` with the current mail highlighted and on the bottom it shows the content of the mail.
 You can now use `:n` and `:p` to navigate through mails.
 
@@ -155,7 +155,7 @@ $ mless
 From: Enno Boland <notifications@github.com>
 Subject: Re: [voidlinux/void-packages] dmenu-4.7 doesn't allow cyrillic input (#7614)
 To: voidlinux/void-packages <void-packages@noreply.github.com>
-Cc: Duncan Overbruck <duncaen@voidlinux.eu>,  Comment <comment@noreply.github.com>
+Cc: Duncan Overbruck <duncaen@voidlinux.org>,  Comment <comment@noreply.github.com>
 Date: Wed, 13 Sep 2017 23:15:15 -0700 (13 weeks, 4 days, 17 hours ago)
 Reply-To: voidlinux/void-packages <reply+002aecdfbf62a2c14f84705a7fd3c31678cfae556dcc03ee92cf0000000115d1e07392a169ce0f49ca87@reply.github.com>
 
@@ -172,7 +172,7 @@ https://github.com/voidlinux/void-packages/issues/7614#event-1248561716
 mless 2 (message 3 of 12)
 ```
 
-Another tool is [mpick(1)](https://man.voidlinux.eu/mpick.1) which can be used to write extensive filters for mail sequences.
+Another tool is [mpick(1)](https://man.voidlinux.org/mpick.1) which can be used to write extensive filters for mail sequences.
 
 ```
 $ mpick -t 'subject =~~ "dmenu"' | mscan
@@ -192,4 +192,4 @@ $ mpick -t 'date >= "2017-09-01" && date < "2017-10-01" && (replied || !seen)' |
 1 mails scanned
 ```
 
-This is just a very small example, `mblaze` is capable of a lot more and has great man pages that are worth reading, see [mblaze(7)](https://man.voidlinux.eu/mblaze.7) and the [git repository](https://github.com/chneukirchen/mblaze) as starting point if you want to learn more about it.
+This is just a very small example, `mblaze` is capable of a lot more and has great man pages that are worth reading, see [mblaze(7)](https://man.voidlinux.org/mblaze.7) and the [git repository](https://github.com/chneukirchen/mblaze) as starting point if you want to learn more about it.
diff --git a/_posts/2017-12-19-advent-mblaze-part-2.markdown b/_posts/2017-12-19-advent-mblaze-part-2.markdown
index 9e5f4aa..35e94a2 100644
--- a/_posts/2017-12-19-advent-mblaze-part-2.markdown
+++ b/_posts/2017-12-19-advent-mblaze-part-2.markdown
@@ -4,11 +4,11 @@ title: "The Advent of Void: Day 19: mblaze part 2"
 comments: true
 ---
 
-Today is a followup on yesterdays [mblaze(7)](https://man.voidlinux.eu/mblaze.7) post.
+Today is a followup on yesterdays [mblaze(7)](https://man.voidlinux.org/mblaze.7) post.
 
-This time I show how I use mblaze to send and receive patches using `git` and [mblaze(7)](https://man.voidlinux.eu/mblaze.7) as example.
+This time I show how I use mblaze to send and receive patches using `git` and [mblaze(7)](https://man.voidlinux.org/mblaze.7) as example.
 
-First I create a patch file with `git format-patch`, afterwards I use [mcom(1)](https://man.voidlinux.eu/mcom.1) to compose a new mail to that I deliver to my local mailbox for this example.
+First I create a patch file with `git format-patch`, afterwards I use [mcom(1)](https://man.voidlinux.org/mcom.1) to compose a new mail to that I deliver to my local mailbox for this example.
 
 ```
 voidlinux.github.com@pi$ git format-patch HEAD~1
@@ -34,15 +34,15 @@ What now? ([s]end, [c]ancel, [d]elete, [e]dit, [m]ime, sign, encrypt) m
 What now? ([s]end, [c]ancel, [d]elete, [e]dit, [m]ime, sign, encrypt) s
 ```
 
-First [mcom(1)](https://man.voidlinux.eu/mcom.1) opened my `$EDITOR` with a template mail, I added the subject, the body and my patch as attachment, using the `#contenttype filename` syntax.
-Then I write the file and close my editor (`:wq`), [mcom(1)](https://man.voidlinux.eu/mcom.1) asks me then what to do next.
+First [mcom(1)](https://man.voidlinux.org/mcom.1) opened my `$EDITOR` with a template mail, I added the subject, the body and my patch as attachment, using the `#contenttype filename` syntax.
+Then I write the file and close my editor (`:wq`), [mcom(1)](https://man.voidlinux.org/mcom.1) asks me then what to do next.
 I choose `[m]ime` first to attach the attachment, mime is requiered for mails that contain multiple parts.
-[mcom(1)](https://man.voidlinux.eu/mcom.1) asks me again what to do next and I choose `[s]end` to deliver the mail.
+[mcom(1)](https://man.voidlinux.org/mcom.1) asks me again what to do next and I choose `[s]end` to deliver the mail.
 
 On my system [opensmtpd(8)](https://man.openbsd.org/smtpd.8) delivers local mails to a maildir.
 
-When the mail is delivered I use [minc(1)](https://man.voidlinux.eu/minc.1) to incorporate the new mails into maildirs `cur` directory and use [mlist(1)](https://man.voidlinux.eu/mlist.1) and [mseq(1)](https://man.voidlinux.eu/mseq.1) to create a new sequence to work with.
-With the new sequence I can now use [mless(1)](https://man.voidlinux.eu/mless.1) to read and navigate through my mails.
+When the mail is delivered I use [minc(1)](https://man.voidlinux.org/minc.1) to incorporate the new mails into maildirs `cur` directory and use [mlist(1)](https://man.voidlinux.org/mlist.1) and [mseq(1)](https://man.voidlinux.org/mseq.1) to create a new sequence to work with.
+With the new sequence I can now use [mless(1)](https://man.voidlinux.org/mless.1) to read and navigate through my mails.
 
 ```
 voidlinux.github.com@pi$ minc ~/mail/local -q
@@ -66,9 +66,9 @@ From 84eb8bea765561c2b4bb0b2b2d239393eb5c97f5 Mon Sep 17 00:00:00 2001
 [...]
 ```
 
-[mless(1)](https://man.voidlinux.eu/mless.1) saves the currently selected mail, which makes it possible to close [mless(1)](https://man.voidlinux.eu/mless.1) and then work with the last viewed mail using other [mblaze(7)](https://man.voidlinux.eu/mblaze.7) tools.
+[mless(1)](https://man.voidlinux.org/mless.1) saves the currently selected mail, which makes it possible to close [mless(1)](https://man.voidlinux.org/mless.1) and then work with the last viewed mail using other [mblaze(7)](https://man.voidlinux.org/mblaze.7) tools.
 
-Because the mail contains a patch I want to apply I use [mshow(1)](https://man.voidlinux.eu/mshow.1)s `-t` flag to get a list of the parts in the mail.
+Because the mail contains a patch I want to apply I use [mshow(1)](https://man.voidlinux.org/mshow.1)s `-t` flag to get a list of the parts in the mail.
 
 ```
 voidlinux.github.com@pi$ mshow -t
@@ -78,7 +78,7 @@ voidlinux.github.com@pi$ mshow -t
     3: text/plain size=3552 name="0001-The-Advent-of-Void-Day-18-mblaze-fixup.patch"
 ```
 
-The third part is the patch file I attached earlier, [mshow(1)](https://man.voidlinux.eu/mshow.1)s `-O` flag to extracts a specified part to `stdout` by its index or by using a pattern.
+The third part is the patch file I attached earlier, [mshow(1)](https://man.voidlinux.org/mshow.1)s `-O` flag to extracts a specified part to `stdout` by its index or by using a pattern.
 I can just pipe the patch directly into `git am` to apply the patch and fix conflicts if necessary.
 
 ```
@@ -86,15 +86,15 @@ voidlinux.github.com@pi$ mshow -O . 3 | git am
 Applying: The Advent of Void: Day 18: mblaze fixup
 ```
 
-Now that the patch is applied and I flag the mail as `seen` and `trashed` using [mflag(1)](https://man.voidlinux.eu/mflag.1), and update the sequence.
-Updating the sequence is necessary because the filename of the mail has changed, I use [mseq(1)](https://man.voidlinux.eu/mseq.1)s `-f` flag in this example to just fix missing mails in the current sequence, using [mlist(1)](https://man.voidlinux.eu/mlist.1) again like at the beginning would get the same result.
+Now that the patch is applied and I flag the mail as `seen` and `trashed` using [mflag(1)](https://man.voidlinux.org/mflag.1), and update the sequence.
+Updating the sequence is necessary because the filename of the mail has changed, I use [mseq(1)](https://man.voidlinux.org/mseq.1)s `-f` flag in this example to just fix missing mails in the current sequence, using [mlist(1)](https://man.voidlinux.org/mlist.1) again like at the beginning would get the same result.
 
 ```
 voidlinux.github.com@pi$ mflag -ST .
 voidlinux.github.com@pi$ mseq -f | mseq -S
 ```
 
-Using [mscan(1)](https://man.voidlinux.eu/mscan.1) once again shows in the second column that the mail is marked as trashed.
+Using [mscan(1)](https://man.voidlinux.org/mscan.1) once again shows in the second column that the mail is marked as trashed.
 
 ```
 voidlinux.github.com@pi$ mscan
@@ -102,4 +102,4 @@ voidlinux.github.com@pi$ mscan
 1 mails scanned
 ```
 
-I hope this post gives a bit more insight on how to work with [mblaze(7)](https://man.voidlinux.eu/mblaze.7).
+I hope this post gives a bit more insight on how to work with [mblaze(7)](https://man.voidlinux.org/mblaze.7).
diff --git a/_posts/2017-12-20-shmux.markdown b/_posts/2017-12-20-shmux.markdown
index 183b920..b00f81b 100644
--- a/_posts/2017-12-20-shmux.markdown
+++ b/_posts/2017-12-20-shmux.markdown
@@ -9,7 +9,7 @@ commands on all of them.  There are many tools for this job, starting
 from simple `for` loops on the shell to full-fledged configuration
 management systems such as Puppet or Chef.
 
-A good compromise is [shmux(1)](https://man.voidlinux.eu/shmux.1), the
+A good compromise is [shmux(1)](https://man.voidlinux.org/shmux.1), the
 *shell multiplexer*.
 
 For example, we can measure the uptimes of my servers,
diff --git a/_posts/2017-12-21-neatvi.markdown b/_posts/2017-12-21-neatvi.markdown
index 839fabb..308f98e 100644
--- a/_posts/2017-12-21-neatvi.markdown
+++ b/_posts/2017-12-21-neatvi.markdown
@@ -5,12 +5,12 @@ comments: true
 ---
 
 On Void, we have many clones of beloved
-[vi(1)](https://man.voidlinux.eu/vi.1p) such as
-[vim](https://man.voidlinux.eu/vim.1),
-[neovim](https://man.voidlinux.eu/nvim.1),
-[nvi](https://man.voidlinux.eu/nvi.1),
-[vile](https://man.voidlinux.eu/vile.1), busybox vi, and of course the
-original [ex-vi](https://man.voidlinux.eu/ex-vi.1).
+[vi(1)](https://man.voidlinux.org/vi.1p) such as
+[vim](https://man.voidlinux.org/vim.1),
+[neovim](https://man.voidlinux.org/nvim.1),
+[nvi](https://man.voidlinux.org/nvi.1),
+[vile](https://man.voidlinux.org/vile.1), busybox vi, and of course the
+original [ex-vi](https://man.voidlinux.org/ex-vi.1).
 
 But today, I want to talk about
 [neatvi](https://github.com/aligrudi/neatvi), a reimplementation from
@@ -24,7 +24,7 @@ of vim and friends,
 but it adds a few important features on top of plain vi,
 such as
 infinite undo/redo, basic syntax highlighting,
-and a partial implementation of [ex(1)](https://man.voidlinux.eu/ex.1p).
+and a partial implementation of [ex(1)](https://man.voidlinux.org/ex.1p).
 
 It's a nice editor for limited environments such as embedded devices
 or recovery systems, or for people that like unbloated software.
diff --git a/_posts/2017-12-24-snooze.markdown b/_posts/2017-12-24-snooze.markdown
index bc74878..da2571a 100644
--- a/_posts/2017-12-24-snooze.markdown
+++ b/_posts/2017-12-24-snooze.markdown
@@ -4,7 +4,7 @@ title: "The Advent of Void: Day 24: snooze"
 comments: true
 ---
 
-[cron(8)](http://man.voidlinux.eu/cron.8) is a nice tool, but it has
+[cron(8)](http://man.voidlinux.org/cron.8) is a nice tool, but it has
 some long-standing problems, among them:
 
 * The cron/crond design requires setuid. 
@@ -15,11 +15,11 @@ some long-standing problems, among them:
   you know about `%`?).
 
 A little, but flexible alternative is to use
-[snooze(1)](http://man.voidlinux.eu/snooze.1), which essentially just
+[snooze(1)](http://man.voidlinux.org/snooze.1), which essentially just
 waits for a particular time, and then executes a command.  To get
 recurring jobs ala cron, we can use this together with our [runit
-service supervision suite](https://www.voidlinux.eu/usage/runit/).
-If we wanted [at(1)](http://man.voidlinux.eu/at.1) instead, we
+service supervision suite](https://www.voidlinux.org/usage/runit/).
+If we wanted [at(1)](http://man.voidlinux.org/at.1) instead, we
 can just run snooze once.
 
 The time for snooze is given using the options
diff --git a/_posts/2017-12-25-ponysay.markdown b/_posts/2017-12-25-ponysay.markdown
index 6400e40..f7f3ac9 100644
--- a/_posts/2017-12-25-ponysay.markdown
+++ b/_posts/2017-12-25-ponysay.markdown
@@ -14,7 +14,7 @@ they are just virtual yet just a command away:
 
 ![Screenshot of ponysay(1)](/assets/screenshots/xmas-ponysay.png)
 
-[ponysay](https://man.voidlinux.eu/ponysay.6) features over 400
+[ponysay](https://man.voidlinux.org/ponysay.6) features over 400
 illustrations of My Little Pony for your terminal.
 Look at all of them using
 
diff --git a/_posts/2018-05-01-serious-issues.md b/_posts/2018-05-01-serious-issues.md
index 0926f1b..7086944 100644
--- a/_posts/2018-05-01-serious-issues.md
+++ b/_posts/2018-05-01-serious-issues.md
@@ -70,5 +70,5 @@ For now, just be aware that the engineering work to help mitigate our problems
 is underway. This engineering work is consuming the full resources of 2 senior
 contributors, and has unfortunately also led to longer PR review times..
 
-If you have any questions, you can contact us via [the forum](https://forum.voidlinux.eu),
+If you have any questions, you can contact us via [the forum](https://forum.voidlinux.org),
 [Twitter](https://twitter.com/VoidLinux), or [IRC](irc://irc.freenode.net/#voidlinux).
diff --git a/_posts/2018-05-02-irc-back.md b/_posts/2018-05-02-irc-back.md
index 9054cbc..2075165 100644
--- a/_posts/2018-05-02-irc-back.md
+++ b/_posts/2018-05-02-irc-back.md
@@ -3,6 +3,6 @@ title: regained control of IRC
 layout: post
 ---
 
-A quick follow-up to [yesterday's post](https://www.voidlinux.eu/news/2018/05/serious-issues.html): We have control over the IRC Channels again!
+A quick follow-up to [yesterday's post](https://www.voidlinux.org/news/2018/05/serious-issues.html): We have control over the IRC Channels again!
 
 Thank you Freenode support team!
diff --git a/_posts/2018-11-05-forum-is-down.markdown b/_posts/2018-11-05-forum-is-down.markdown
index 89ca8bd..0ebcc8c 100644
--- a/_posts/2018-11-05-forum-is-down.markdown
+++ b/_posts/2018-11-05-forum-is-down.markdown
@@ -18,7 +18,7 @@ channels:
     * We have `#voidlinux` and `#xbps` on freenode
     * `#voidlinux` is for general support
     * `#xbps` is for development discussion
-  * [The Wiki](http://wiki.voidlinux.eu)
+  * [The Wiki](http://wiki.voidlinux.org)
     * The wiki is currently in maintenence mode, help us replace it at
       [the docs repo](https://github.com/void-linux/void-docs/)
   * StackExchange