Add missing links (cncf#1185)

Signed-off-by: Henok Biadglign Ademtew <46082799+HenokB@users.noreply.github.com>

Signed-off-by: Henok Biadglign Ademtew <46082799+HenokB@users.noreply.github.com>
Signed-off-by: Jason (Jay) Smith <jaysmith@google.com>

content/en/site-reliability-engineering.md

@@ -10,13 +10,13 @@ tags: ["methodology", "", ""]
 Site Reliability Engineering or SRE is a discipline that combines operations and software engineering. 
 The latter is applied to infrastructure and operations problems, specifically. 
 Meaning, instead of building product features, Site Reliability Engineers build systems to run applications. 
-There are similarities with DevOps, but while DevOps focuses on getting code to production, 
+There are similarities with [DevOps](/devops/), but while DevOps focuses on getting code to production, 
 SRE ensures that code running in production works properly.
 
 ## Problem it addresses
 
-Ensuring applications run reliably requires multiple capabilities, 
-from performance monitoring, alerting, debugging to troubleshooting. 
+Ensuring applications run [reliably](/reliability/) requires multiple capabilities, 
+from performance monitoring, alerting, [debugging](/debugging/) to troubleshooting. 
 Without these, system operators can only react to problems vs. proactively working towards avoiding them 
 — downtime only becomes a matter of time.
 
@@ -26,4 +26,4 @@ An SRE approach minimizes the cost, time, and effort of the software development
 by continuously improving the underlying system. 
 The system continuously measures and monitors the infrastructure and application components. 
 When something goes wrong, the system points Site Reliability Engineers to when, where, and how to fix it. 
-This approach helps create highly scalable and reliable software systems by automating operational tasks.
+This approach helps create highly [scalable](/scalability/) and reliable software systems by automating operational tasks.