Merge pull request #2 from strayArch/chroot-link

fixed incorrect link

Author: xorond

contributing/details.md.blade.php

@@ -4,7 +4,7 @@
 * **Detailed description.** The body of the PR must contain a detailed description of what changes are being introduced, and most importantly, *why* this PR should be merged.
 * **One package per request.** PRs must be for a single package only.  A PR addressing multiple packages without merit risks having a delayed merge or being closed.
 * **Squash commits.** Your commits must be meaningful. If you make incremental changes or fixes, they must [be squashed](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#_squashing) before the pull request will be merged.
-* **Check that your changes build.** Your submission must build using the [clean chroot](https://archstrike.org/wiki/chroot) method on *all* supported architectures that the package is to be built for.  No exceptions.
+* **Check that your changes build.** Your submission must build using the [clean chroot](https://archstrike.org/wiki/contributing/chroot) method on *all* supported architectures that the package is to be built for.  No exceptions.
 * **Work within one PR.** Do not close a PR and open another with new changes.  Amend your commit and force push to your branch to update the changes in the pull request.
 * Ensure your PR addresses three of the most common problems:
   * Correctly update the pkgver or pkgrel of the package (see below).

contributing/involvement.md.blade.php

@@ -18,4 +18,4 @@
 
 Submitting PKGBUILDs is a good way of helping out. The packages that fail to build can be seen on our [build issues page](https://archstrike.org/builder) and are prioritised for fixing. You can also create new PKGBUILDs for new tools that you want to see added in our repositories. If you are a developer, we are usually more then happy to add in new packages so you can submit them this way.
 
-You can find a more detailed guide about this on our [wiki entry](https://archstrike.org/wiki/chroot) and also more details on the [contribution details page](https://archstrike.org/wiki/contributing).
+You can find a more detailed guide about this on our [wiki entry](https://archstrike.org/wiki/contributing/chroot) and also more details on the [contribution details page](https://archstrike.org/wiki/contributing).