Remove http://default from content

content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.yml

@@ -80,7 +80,7 @@ body:
               
     format: full_html
     processed: |
-      <p>Last month, I wrote an email explaining <a href="http://default/daily/2024/02/28/why-i-dont-branch">why I don't create branches</a>.</p>
+      <p>Last month, I wrote an email explaining <a href="/daily/2024/02/28/why-i-dont-branch">why I don't create branches</a>.</p>
 
       <p>After sending that email, I received this question from a reader (shared with permission):</p>
 
@@ -98,7 +98,7 @@ body:
 
       <h2 id="option-1%3A-worktrees">Option 1: Worktrees</h2>
 
-      <p>Whilst I don't create branches, I do use <a href="http://default/daily/2022/08/12/git-worktrees-docker-compose">Git worktrees</a>, which allows me to have multiple versions of the code checked out at the same time - similar to having multiple clones of a repository.</p>
+      <p>Whilst I don't create branches, I do use <a href="/daily/2022/08/12/git-worktrees-docker-compose">Git worktrees</a>, which allows me to have multiple versions of the code checked out at the same time - similar to having multiple clones of a repository.</p>
 
       <p>Having multiple worktrees, you don't need to stash the code for your incomplete feature or worry about commits you haven't pushed yet.</p>
 
@@ -108,7 +108,7 @@ body:
 
       <h2 id="option-2%3A-feature-flags">Option 2: Feature Flags</h2>
 
-      <p>My preferred approach is to use <a href="http://default/daily/2022/12/07/separating-releases-from-deployments-with-feature-flags">feature flags</a>, a.k.a. feature toggles.</p>
+      <p>My preferred approach is to use <a href="/daily/2022/12/07/separating-releases-from-deployments-with-feature-flags">feature flags</a>, a.k.a. feature toggles.</p>
 
       <p>My wrapping the incomplete feature in a feature flag, it can be deployed but won't be active until the flag is enabled - similar to writing a new Drupal module but not enabling it.</p>