Remove http://default from content

content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.yml

@@ -55,7 +55,7 @@ body:
               
     format: full_html
     processed: |
-      <p>Once you've <a href="http://default/daily/2024/09/02/no-one-sees-your-clean-up-commits">cleaned up and tided your commits</a>, re-ordered them and squashed any commits together to combine them into logical changes, before you push them, you should also check if your commit messages still make sense.</p>
+      <p>Once you've <a href="/daily/2024/09/02/no-one-sees-your-clean-up-commits">cleaned up and tided your commits</a>, re-ordered them and squashed any commits together to combine them into logical changes, before you push them, you should also check if your commit messages still make sense.</p>
 
       <p>Using short or generic commit messages is fine when spiking a solution in very short feedback loops, but when you push your changes, you want them to be as descriptive and meaningful as possible.</p>
 
@@ -67,7 +67,7 @@ body:
 
       <p>Does it capture why the change is needed, any alternative approaches that we considered or tried, or any complications that were encountered?</p>
 
-      <p>If you're following a standard like <a href="http://default/daily/2022/09/01/conventional-commits-changelogs">conventional commits</a>, have you correctly included the required information, such as the type, scope and any references, such as the task reference?</p>
+      <p>If you're following a standard like <a href="/daily/2022/09/01/conventional-commits-changelogs">conventional commits</a>, have you correctly included the required information, such as the type, scope and any references, such as the task reference?</p>
 
       <p>Having a Git log with detailed history is valuable when you need to review the changes in the future, but it also makes it more likely your changes will be approved and merged, whether you're working on a paid project or volunteering on an open-source project.</p>