Merge pull request #21 from krishanthisera/chore/fix_markdown_syntax_…

…issues

Fix a couple of markdown syntax issues

src/content/blog/edge-functions.md

@@ -158,7 +158,7 @@ __A Quick Note:__ For this setup, I'm leveraging a pipeline to deploy the infras
 
 Why is this Dockerfile significant? Spacelift offers the capability to pair custom build environments with its runners. So, I've incorporated `Node.js` and `npm` into the runner's environment.
 
-```Dockerfile
+```dockerfile
 # https://github.com/krishanthisera/aws-static-hosting/blob/main/Dockerfile
 FROM public.ecr.aws/spacelift/runner-terraform:latest
 

src/content/blog/haproxy_case_study.md

@@ -63,7 +63,7 @@ Now, let's examine our HAProxy configurations. The HAProxy configuration file co
 
 #### Global
 
-```conf
+```sh
 global
     log 127.0.0.1   local2
     maxconn 1024
@@ -85,7 +85,7 @@ global
 
 It's time to begin our configurations for HAProxy's Default Configuration. In the default section, we set the default parameters for both frontend and backend sections:
 
-```conf
+```sh
 defaults
     log     global
     option  tcplog
@@ -112,7 +112,7 @@ Finally, the frontend and backend configurations
 
 In the frontend section, HAProxy accepts traffic from public entities, processes them, and forwards the traffic to the relevant backend. In the following frontend section, I will demonstrate how to read HTTP headers, process them with basic ACLs, and forward them to the corresponding backend sections.
 
-```conf
+```sh
 frontend http_handler
     bind *:80
     bind *:443 ssl crt /etc/haproxy/certs/hrms.itcstaging.com-0001.pem
@@ -139,7 +139,7 @@ Traffic arriving at our frontends is tested against the ACLs, so it's essential
 
 #### Backend
 
-```conf
+```sh
 backend be_london
     balance leastcon
     redirect scheme https if !{ ssl_fc }
@@ -195,7 +195,7 @@ firewall-cmd --reload
 
 ## Complete Configuration Sample
 
-```conf
+```sh
 global
     log 127.0.0.1   local2
     maxconn 1024