Fix broken anchor links

Signed-off-by: Thomas Staudinger <Staudi.Kaos@gmail.com>

Author: Staudey

docs/packaging/creating-a-new-package.md

@@ -166,7 +166,7 @@ git commit
 
 ### Commit message format for new packages
 
-`git commit` on [an initialized repository](prepare-for-packaging.md#initialize-git-hooks) will automatically open your editor with the correct template.
+`git commit` on [an initialized repository](prepare-for-packaging.md#initialize-git-hooks-for-linting) will automatically open your editor with the correct template.
 Note that lines starting with a `#` will be ignored by Git and do not need to be removed.
 
 There should be a summary line (with the package name), a blank line, and then the rest of the commit message.

docs/packaging/packaging-changes.md

@@ -118,7 +118,7 @@ This page is meant to serve as a changelog of sorts for the Solus packaging envi
 
 #### Git hooks
 
-- Run `go-task init` to initialize Git hooks for the packages repository. See [Prepare for packaging](prepare-for-packaging.md#initialize-git-hooks).
+- Run `go-task init` to initialize Git hooks for the packages repository. See [Prepare for packaging](prepare-for-packaging.md#initialize-git-hooks-for-linting).
 - Use `git commit` for committing packaging changes and fill in the template shown.
   It is no longer required to manually copy-paste the template or use `git commit --cleanup=scissors`.
 

docs/packaging/updating-an-existing-package.md

@@ -129,7 +129,7 @@ The following guidelines apply to the commit message body:
 - There may also be a section for Solus specific work (e.g. rebuild against x / rework to remove dependency).
 - Optional: A link to the upstream release notes page.
 
-`git commit` on [an initialized repository](prepare-for-packaging.md#initialize-git-hooks) will automatically open your editor with the correct template.
+`git commit` on [an initialized repository](prepare-for-packaging.md#initialize-git-hooks-for-linting) will automatically open your editor with the correct template.
 Note that lines starting with a `#` will be ignored by Git and do not need to be removed.
 
 _Important_: Do not include issue numbers in changelogs. This will incorrectly link your issue to another one in our repository.