📝 Fixed non-descriptive link texts (#564)

* 📝 Fixed non-descriptive link texts

* 📝 Updated link text

Author: devtobi

docs/templates/develop.md

@@ -253,7 +253,7 @@ Code Rabbit is free to use for open-source projects. If you are developing a pro
 
 ### CodeQL
 
-**CodeQL** is a GitHub tool for discovering vulnerabilities and code smells in code. More details can be found [here](https://codeql.github.com/).
+**CodeQL** is a GitHub tool for discovering vulnerabilities and code smells in code. More details can be found on the [official CodeQL website](https://codeql.github.com/).
 
 The template enables CodeQL for Pull Requests and configures CodeQL to only scan for Java and JavaScript/TypeScript/Vue files by default.
 For further information on how to change the configuration, please check out the documentation of the related custom [GitHub workflow](https://github.com/it-at-m/.github/blob/main/workflow-templates/codeql.yaml).
@@ -292,7 +292,7 @@ More information about Rulesets can be found in the [official GitHub documentati
 
 ::: danger IMPORTANT
 Note that the tools mentioned above (CodeRabbit, CodeQL, Dependency Review) are optional by default and are not required to pass when a PR should be merged.
-We strongly encourage you to enable the status checks for those tools before being able to merge a PR. More information about status checks can be found [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
+We strongly encourage you to enable the status checks for those tools before being able to merge a PR. More information about status checks can be found in the [official GitHub documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
 Status checks are configurable as part of the rulesets.
 :::
 

docs/templates/organize.md

@@ -15,7 +15,7 @@ Additionally, labels indicate the priority of issues, for example, `Medium`.
 There are also labels that specify the type of issue, like `Documentation`.
 
 We highly recommend using labels to maintain a clear structure.
-You can view all our current labels [here](https://github.com/it-at-m/refarch-templates/labels) for inspiration.
+You can view all our current labels on the [GitHub repository's label page](https://github.com/it-at-m/refarch-templates/labels) for inspiration.
 For more information on how to set up labels for your own project, please check the official [GitHub documentation](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels).
 
 Your project labels are also utilized for [Automatic Labeling](#automatic-labeling).

docs/tools.md

@@ -8,7 +8,7 @@ The tools itself are described in [Develop](./templates/develop).
 ## PMD
 
 The `refarch-pmd` Java module provides a default ruleset for [PMD](https://pmd.github.io/) which is used for code linting.
-The module code can be found [here](https://github.com/it-at-m/refarch/tree/main/refarch-tools/refarch-java-tools/refarch-pmd) and the specific ruleset configuration [here](https://github.com/it-at-m/refarch/blob/main/refarch-tools/refarch-java-tools/refarch-pmd/src/main/resources/refarch-pmd-ruleset.xml).
+The module code can be found in the [`refarch-pmd` directory](https://github.com/it-at-m/refarch/tree/main/refarch-tools/refarch-java-tools/refarch-pmd) and the specific ruleset configuration inside the [`resources` subdirectory](https://github.com/it-at-m/refarch/blob/main/refarch-tools/refarch-java-tools/refarch-pmd/src/main/resources/refarch-pmd-ruleset.xml).
 
 All available rules can be found in [the according PMD documentation](https://docs.pmd-code.org/latest/pmd_rules_java.html).