feat: update links

org/org-mode/deploy-blog-written-with-org-mode-on-github-pages.org

@@ -181,6 +181,5 @@ The GitHub Actions workflow will publish them.
 We presented an easier way to deploy your posts with *org-mode*, *hugo*, *GitHub Actions* and *GitHub Pages*.
 With that workflow, we only need to focus on writing org-mode files.
 Lastly, we know this workflow works because we used it to deploy this post!!!
-The code is at https://github.com/danielorihuela/danielorihuela.github.io/tree/development.
 
 I hope you liked it and that you have learned something!

org/org-mode/heap-based-buffer-overflows.org

@@ -7,7 +7,7 @@
 
 * Introduction
 
-In a previous post, I explained what a [[https://danielorihuela.github.io/posts/stack-based-buffer-overflows/][stack-based buffer overflow]] is and how it works. Today, we are going to see the heap-based variant.
+In a previous post, I explained what a [[https://danielorihuela.dev/blog/stack-based-buffer-overflows/][stack-based buffer overflow]] is and how it works. Today, we are going to see the heap-based variant.
 
 * Stack vs Heap-based buffer overflows?
 

org/org-mode/store-shellcode-in-environment-variable.org

@@ -5,7 +5,7 @@
 #+options: ^:nil
 
 
-In the [[https://danielorihuela.github.io/posts/stack-based-buffer-overflows/][previous post]] we explained how stack-based buffer overflows work. In the last exercise, we inserted the shellcode in the stack. However, this might be a problem. What happens if the shellcode doesn't fit in the stack? We can store it in an environment variable.
+In the [[https://danielorihuela.dev/blog/stack-based-buffer-overflows/][previous post]] we explained how stack-based buffer overflows work. In the last exercise, we inserted the shellcode in the stack. However, this might be a problem. What happens if the shellcode doesn't fit in the stack? We can store it in an environment variable.
 
 * Manually store shellcode in env var