Fix tips_and_tricks links

Related to d6b0ee8

Author: meator

src/mini-tutors/completions.md

@@ -70,7 +70,7 @@ As you sure remember, you can't run programs compiled for target architecture on
 host. If the program is compiled (`hatch` mentioned above isn't by the way, so
 the following advice doesn't apply to it), you'll have to use `build_helper=qemu`.
 
-This is described in [tips and tricks](../tips_and_tricks.md#qemu).
+This is described in [tips and tricks](../tips-and-tricks.md#qemu).
 
 This is used in
 [`mdBook`](https://github.com/void-linux/void-packages/blob/3ddc63b10ff4f7a574996a3a43952c39c732101f/srcpkgs/mdBook/template#L18-L21)

src/package-update-tutorial.md

@@ -389,7 +389,7 @@ package](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md
 ---
 
 [^clone]: There are alternative ways of cloning. They are described at
-          [different ways of cloning](tips_and_tricks.md#different-ways-of-cloning).
+          [different ways of cloning](tips-and-tricks.md#different-ways-of-cloning).
 [^remotes]: This is briefly described in the [remotes section of contributing
             (of this tutorial, not void-packages'
             CONTRIBUTING)](packaging/contributing.md#remotes)

src/packaging/bat.md

@@ -290,7 +290,7 @@ post_install() {
 }
 ```
 
-[This is an useful trick by the way.](../tips_and_tricks.md#setting-environmental-variables)
+[This is an useful trick by the way.](../tips-and-tricks.md#setting-environmental-variables)
 
 `BAT_ASSETS_GEN_DIR` uses `XBPS_BUILDDIR`, `pkgname` and `version` variables.
 `pkgname` and `version` are defined in the template and `XBPS_BUILDDIR` is an

src/packaging/contributing.md

@@ -209,7 +209,7 @@ Here is an example of a failed check:
 ![failed check](../images/contributing/failed_check.png)
 
 You can click on Details to see what `xbps-src` outputted. [It is also useful to
-reproduce the error locally.](../tips_and_tricks.md#reproduce-checks-locally)
+reproduce the error locally.](../tips-and-tricks.md#reproduce-checks-locally)
 
 You should try to fix these errors. Cross compilation is the source of most
 problems when contributing new packages. This is briefly described in [Packaging
@@ -426,7 +426,7 @@ like to.
 
 If you want to continue reading, you can look at
 [troubleshooting](../troubleshooting.md) and [tips and
-tricks](../tips_and_tricks.md) for more useful info about `xbps-src`.
+tricks](../tips-and-tricks.md) for more useful info about `xbps-src`.
 
 ---
 

src/packaging/j4-dmenu-desktop.md

@@ -223,7 +223,7 @@ At the time of writing this tutorial, cloning the repo took me 15 minutes on my
 notebook. It had 626 MB.
 
 [There are faster ways to clone, but this way should be
-preferred.](../tips_and_tricks.md#different-ways-of-cloning)
+preferred.](../tips-and-tricks.md#different-ways-of-cloning)
 
 While you wait for it to clone, you can learn more about
 [void-packages](https://github.com/void-linux/void-packages):
@@ -915,12 +915,12 @@ for each architecture?
 No! It has just `x86_64` and it cross compiles to all other architectures.
 
 [Note that there are some specific architectures for which you don't have to
-(and you shouldn't) cross compile.](../tips_and_tricks.md#nocross)
+(and you shouldn't) cross compile.](../tips-and-tricks.md#nocross)
 
 The one rule of cross compiling is that **you can not execute what you build.**
 When your host (your computer) is `x86_64` and you are cross compiling to let's
 say `armv6l`, the compiled result can be executed only on `armv6l`, not on
-`x86_64` ([unless you use QEMU](../tips_and_tricks.md#qemu), but that method can
+`x86_64` ([unless you use QEMU](../tips-and-tricks.md#qemu), but that method can
 not be used everywhere).
 
 Sometimes the build system tries to run what it compiles. Software using such

src/pr-testing-tutorial.md

@@ -63,7 +63,7 @@ git clone https://github.com/void-linux/void-packages.git
 This takes about 15 minutes and 626MiB on my laptop.
 
 To speed this up, you can look at [different ways of
-cloning](tips_and_tricks.md#different-ways-of-cloning). But the full clone
+cloning](tips-and-tricks.md#different-ways-of-cloning). But the full clone
 should be preferred.
 
 You can then continue with [You have a `void-packages`