removed absolute urls

SSWConsulting · Dec 17, 2023 · 149230b · 149230b
1 parent 4a862d2
commit 149230b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/rules/do-you-use-co-creation-patterns/rule.md b/rules/do-you-use-co-creation-patterns/rule.md
@@ -43,7 +43,7 @@ Inefficient code reviews can be caused by:
   * This requires a smaller block of time to review which makes it easier for the reviewer to find the time
   * Less risk - reduces the chance of an incorrect approach being taken
   * Get quality feedback - small blocks of code are easier to digest
-  * Create a [great pull request](https://www.ssw.com.au/rules/write-a-good-pull-request/) to make it easier for the reviewer to understand your changes.
+  * Create a [great pull request](/write-a-good-pull-request/) to make it easier for the reviewer to understand your changes.
 * Reviewer - When reviewing asynchronously
   * Be explicit and suggest the exact code changes where possible (GitHub has a feature for this, see <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request>)
   * Call the developer for more complicated changes

diff --git a/rules/do-you-zz-old-files-rather-than-deleting-them/rule.md b/rules/do-you-zz-old-files-rather-than-deleting-them/rule.md
@@ -65,6 +65,6 @@ On YouTube click the ‘New Version’ link in the description.
 
 ::: info
 
-If you are deleting something that uses resources and/or cost money, it is a good idea to 'zz' it first - and use a follow up to remind yourself to delete it after a reasonable amount of time, as per: https://www.ssw.com.au/rules/follow-up-effectively/
+If you are deleting something that uses resources and/or cost money, it is a good idea to 'zz' it first - and use a follow up to remind yourself to delete it after a reasonable amount of time, as per: [https://www.ssw.com.au/rules/follow-up-effectively/](/follow-up-effectively/)
 
-:::
+:::