deploy: 00e9e5eade

master/package-managers.html

@@ -235,7 +235,7 @@ in the AUR, which builds the master branch.</p>
 <h3 id="nixos"><a class="header" href="#nixos">NixOS</a></h3>
 <p>Helix is available in <a href="https://github.com/nixos/nixpkgs">nixpkgs</a> through the <code>helix</code> attribute,
 the unstable channel usually carries the latest release.</p>
-<p>Helix is also available as a <a href="https://nixos.wiki/wiki/Flakes">flake</a> in the project
+<p>Helix is also available as a <a href="https://wiki.nixos.org/wiki/Flakes">flake</a> in the project
 root. Use <code>nix develop</code> to spin up a reproducible development shell. Outputs are
 cached for each push to master using <a href="https://www.cachix.org/">Cachix</a>. The
 flake is configured to automatically make use of this cache assuming the user

master/print.html

@@ -260,7 +260,7 @@ in the AUR, which builds the master branch.</p>
 <h3 id="nixos"><a class="header" href="#nixos">NixOS</a></h3>
 <p>Helix is available in <a href="https://github.com/nixos/nixpkgs">nixpkgs</a> through the <code>helix</code> attribute,
 the unstable channel usually carries the latest release.</p>
-<p>Helix is also available as a <a href="https://nixos.wiki/wiki/Flakes">flake</a> in the project
+<p>Helix is also available as a <a href="https://wiki.nixos.org/wiki/Flakes">flake</a> in the project
 root. Use <code>nix develop</code> to spin up a reproducible development shell. Outputs are
 cached for each push to master using <a href="https://www.cachix.org/">Cachix</a>. The
 flake is configured to automatically make use of this cache assuming the user