Fix code blocks contained in markdown code blocks that should be printed as literals

Author: webstackdev

src/content/articles/api-gateway-metrics-traces-logs-debugging/pdf.mdx

@@ -816,30 +816,30 @@ With instrumentation and dashboards in place, you're ready to debug real problem
 
 You receive an alert: P99 latency has exceeded 2 seconds. Users are complaining. Here is how to investigate systematically:
 
-```markdown title="latency-debug-runbook.md"
+````markdown title="latency-debug-runbook.md"
 # Gateway Latency Spike Investigation
 # Use this runbook when gateway latency alerts fire
 
 ## Step 1: Identify Scope
 
 Query: Is latency high for all routes or specific routes?
 
-\`\`\`promql
+```promql
 histogram_quantile(0.99,
   sum(rate(gateway_request_duration_seconds_bucket[5m])) by (le, route)
 )
-\`\`\`
+```
 
 If one route is slow, focus there. If all routes are slow, the problem is gateway-wide.
 
 ## Step 2: Gateway vs. Backend
 
 Query: Is the gateway slow, or is a backend slow?
 
-\`\`\`promql
+```promql
 # Gateway overhead only
 avg(gateway_request_duration_seconds - gateway_upstream_duration_seconds) by (route)
-\`\`\`
+```
 
 If gateway overhead is high, check gateway resources (CPU, memory, connection pools).
 If upstream time is high, the problem is in the backend.
@@ -853,10 +853,10 @@ Look for: long spans, retries, connection waits, DNS resolution.
 
 Query: Are circuit breakers tripping? Connection pools exhausted?
 
-\`\`\`promql
+```promql
 gateway_circuit_breaker_state{upstream="affected-service"}
 gateway_upstream_connections_active / gateway_upstream_connections_max
-\`\`\`
+```
 
 ## Step 5: Correlate with Logs
 
@@ -865,7 +865,7 @@ Look for: error messages, timeout logs, retry logs, connection errors.
 
 **AWS Alternative**: Use CloudWatch Logs Insights with queries like:
 `fields @timestamp, requestId, route, latency | filter latency > 2000 | sort @timestamp desc`
-```
+````
 
 Code: Latency spike investigation runbook using gateway observability.
 

src/content/articles/argocd-sync-failures-gitops-debugging-troubleshooting/pdf.mdx

@@ -517,7 +517,7 @@ The root cause is almost always a hook Job that isn't completing. Either it's st
 
 Here's the runbook I use:
 
-```markdown title="runbooks/hook-stuck.md"
+````markdown title="runbooks/hook-stuck.md"
 # Runbook: Sync Stuck on Hook
 
 ## Symptoms
@@ -527,19 +527,22 @@ Here's the runbook I use:
 ## Diagnosis
 
 1. Identify the stuck hook:
-\`\`\`bash
+
+```bash
 kubectl get jobs -n myapp -l argocd.argoproj.io/hook
-\`\`\`
+```
 
 2. Check hook job status:
-\`\`\`bash
+
+```bash
 kubectl describe job <hook-job-name> -n myapp
-\`\`\`
+```
 
 3. Check hook pod logs:
-\`\`\`bash
+
+```bash
 kubectl logs -n myapp -l job-name=<hook-job-name>
-\`\`\`
+```
 
 ## Common Causes
 
@@ -552,20 +555,23 @@ kubectl logs -n myapp -l job-name=<hook-job-name>
 ## Resolution
 
 1. If hook can be safely skipped:
-\`\`\`bash
+
+```bash
 argocd app sync myapp --prune --force
-\`\`\`
+```
 
 2. If hook needs to complete:
+
 - Fix the underlying issue
 - Delete the stuck job
 - Trigger new sync
 
 3. To prevent recurrence:
+
 - Add `activeDeadlineSeconds` to job spec
 - Add proper health checks to hook
 - Consider using `hook-delete-policy: BeforeHookCreation`
-```
+````
 Code: Runbook for debugging sync stuck on hook execution.
 
 The key insight is that ArgoCD can't tell you why the hook is stuck—it only knows the Job hasn't reached a terminal state. You have to dig into Kubernetes to find the actual cause.

src/content/articles/demo/index.mdx

@@ -541,6 +541,8 @@ Showcase related articles using the production carousel component:
 
 The project contains the full bundle of Shiki languages. They are dynamically loaded individually. Some common languages: `asm` for Assembly, `astro`, `awk`, `blade`, `clojure`, `cmake`, `cpp` for C++, `csharp` for C#, `css`, `diff`, `docker` for Dockerfiles, `dotenv`, `erlang`, `go`, `graphql`, `haskell`, `html`, `http`, `ini`, `java`, `javascript` / `js`, `json`, `json5`, `jsx`, `kotlin`, `log`, `lua`, `make`, `markdown`, `mdx`, `php`, `powershell`, `puppet`, `python`, `r`, `regexp`, `ruby`, `rust`, `scala`, `scss`, `sql`, `svelte`, `swift`, `systemd`, `terraform`, `toml`, `tsx`, `typescript` / `ts`, `vue`, `xml`, `yaml`. `promql` is aliased to `go` for now.
 
+Note that code blocks that are not inline must be wrapped with _at least_ three backticks, but can be wrapped with more. So for example to include an example code block inside of a markdown code block, you can use four backticks to wrap the markdown code block - which allows you to use a code block with three backticks as a literal inside the code block.
+
 This `console.log("hello, world!")` statement is inline code.
 
 ```typescript