fix: xml parsing error caused by an apostrophe

content/blog/dockerized-onion-service.md

@@ -40,13 +40,22 @@ services:
   nginx:
     image: nginx:latest
     container_name: nginx-onion
-    command: 
+    command:
     volumes:
       - ./web/config/onion-default.conf:/etc/nginx/conf.d/default.conf:rw
       - ./web/public:/usr/share/nginx/html:ro
       - nginx-tor-socket:/var/run/onion-sockets:rw
     healthcheck:
-      test: ["CMD", "curl", "-f", "--unix-socket", "/var/run/onion-sockets/site.sock", "||", "exit 1"]
+      test:
+        [
+          "CMD",
+          "curl",
+          "-f",
+          "--unix-socket",
+          "/var/run/onion-sockets/site.sock",
+          "||",
+          "exit 1",
+        ]
       interval: 10s
       timeout: 5s
       retries: 5
@@ -126,7 +135,10 @@ add_header Onion-Location http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65
 Or alternatively include an HTML `<meta>` attribute:
 
 ```html
-<meta http-equiv="onion-location" content="http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65df3khnpyd.onion" />
+<meta
+  http-equiv="onion-location"
+  content="http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65df3khnpyd.onion"
+/>
 ```
 
 Notably, with proxying enabled through Cloudflare, I encountered difficulties in getting the response headers to pass through to the client, necessitating the use of the `<meta>` attribute instead.
@@ -148,4 +160,3 @@ I highly recommend checking out the sites I browsed while figuring this stuff ou
 - ["Connect two NGINX's through UNIX sockets" by David Sierra](https://blog.davidsierra.dev/posts/connect-nginxs-through-sockets/)
 - ["Create a complete Tor Onion Service with Docker and OpenSUSE in less than 15 minutes" by Jason S. Evans](https://www.youtube.com/watch?v=iUxiTk6w1sc)
 - [Onionscan Documentation](https://onionscan.org/)
-

content/blog/understanding-srdi.md

@@ -9,7 +9,7 @@ categories = []
 
 In the ever-evolving landscape of malware, Shellcode Reflective DLL Injection (RDI) stands as a formidable technique despite its age, distinguished by its stealth and efficiency. Unlike traditional DLL injection methods, which often leave apparent traces for AV systems to detect, RDI operates on a more subtle level. Basically it challenges typical defensive solutions such as behavior monitoring, heuristics, or signature-based detection.
 
-Implementing a reflective loader myself provided a great insight into PE files and Windows API, and it's definitely a good initial foothold into more advanced techniques.
+Implementing a reflective loader myself provided a great insight into PE files and Windows API, and it is definitely a good initial foothold into more advanced techniques.
 
 ## Steps