new links per Growtika

site/content/guides/monitoring-as-code.md

@@ -208,7 +208,7 @@ MaC makes it easy to monitor performance across regions, simulating user experie
 
 ### **Scheduled Jobs or Cron Jobs**
 
-Scheduled jobs or cron jobs are crucial for automating tasks, but failures can lead to major problems if undetected. MaC enables heartbeat monitoring to ensure these jobs run on schedule.
+Scheduled jobs or cron jobs are crucial for automating tasks, but failures can lead to major problems if undetected. MaC enables [heartbeat monitoring](https://www.checklyhq.com/blog/heartbeat-monitoring-with-checkly/) to ensure these jobs run on schedule.
 
 A heartbeat check verifies that a job reports back within the expected timeframe. If it doesn’t, an alert is triggered, giving you a chance to fix the issue before it impacts your system.
 

site/content/learn/incidents/modern-root-cause-analysis.md

@@ -58,7 +58,7 @@ A payment service fails intermittently. Traditional RCA might check logs in isol
 - **OpenTelemetry** (unified data collection for the back end)
 - **Prometheus/Grafana** (metrics visualization)
 - **Jaeger** (distributed tracing)
-- **Checkly** (Synthetic monitoring of the frontend, correlated with OpenTelemetry traces)
+- **Checkly** ([synthetic monitoring](https://www.checklyhq.com/blog/what-is-synthetic-monitoring/) of the frontend, correlated with OpenTelemetry traces)
 
 Modern RCA reduces MTTR  by replacing guesswork with data-driven decisions. 
 

site/content/learn/monitoring/transaction-monitoring.md

@@ -133,7 +133,8 @@ Although synthetic monitoring provides simulated data, it cannot replace actual
 
 When [retries are set up correctly](https://www.checklyhq.com/docs/alerting-and-retries/), we should only get a synthetic transaction monitoring alert when there’s a real problem that users will notice. But detecting an issue through synthetic monitoring is only the first step. Pinpointing the root cause of problems requires additional diagnostic tools and processes. Synthetic monitoring should be run as a separate service from all of your internal services and tools, and as such will lack insight into how your back end is handling requests. Once you’ve detected a problem, backend logs, traces, and other information from something like an [OpenTelemetry monitoring system](https://www.checklyhq.com/learn/opentelemetry/getting-started-with-observability/), will be needed to find a root cause.
 
-{{< figure src="/learn/images/animated-diagram.gif" alt="an animated graph of the Checkly monitoring process with OpenTelemetry traces" title="Checkly Traces can connect synthetic site checks with the related traces observed by your OpenTelemetry monitoring." >}}
+{{< figure src="/learn/images/animated-diagram.gif" alt="an animated graph of the Checkly monitoring process with OpenTelemetry traces" title="" >}}
+*Checkly Traces can connect synthetic site checks with the related traces observed by your [OpenTelemetry monitoring](https://www.checklyhq.com/learn/opentelemetry/).*
 
 **Tool Integration Needs**
 

site/content/learn/playwright/_index.md

@@ -9,7 +9,7 @@ metatags:
 toc: false
 ---
 
-Playwright serves as the foundation for Checkly's synthetic *Monitoring as Code*. To get the most from Checkly, we put together a series of guides and examples to help you get started with Playwright.
+Playwright serves as the foundation for Checkly's synthetic [*Monitoring as Code*](https://www.checklyhq.com/guides/monitoring-as-code/). To get the most from Checkly, we put together a series of guides and examples to help you get started with Playwright.
 
 ## Getting Started