Fixing links and standardising titles

courses/systems_design/availability.md

@@ -76,7 +76,7 @@ The combined availability of the system is
 
 **KEY TAKEAWAYS:** Strive for active/active rather than active/passive solutions, they have a lesser risk of cross over being unreliable. Use LB and right load balancing methods to ensure reliable failover. Model and build your data systems to ensure data is correctly handled when crossover happens. Generally DB systems follow active/passive semantics for writes. Masters accept writes and when master goes down, follower is promoted to master(active from being passive) to accept writes. We have to be careful here that the cutover never introduces more than one masters. This problem is called a split brain.
 
-## SRE Use cases
+## Applications in SRE role
 1. SRE works on deciding an acceptable SLA and make sure system is available to achieve the SLA
 2. SRE is involved in architecture design right from building the data center to make sure site is not affected by network switch, hardware, power or software failures
 3. SRE also run mock drills of failures to see how the system behaves in uncharted territory and comes up with a plan to improve availability if there are misses. 

courses/systems_design/fault-tolerance.md

@@ -60,7 +60,7 @@ Let's take another example, we come up with a new model for our Content sharing
 - https://learning.oreilly.com/library/view/the-art-of/9780134031408/ch21.html#ch21
 
 
-### SRE Use cases:
+### Applications in SRE role
 1. Work with the DC tech or cloud team to distribute infrastructure such that its immune to switch or power failures by creating fault zones within a Data Center
 https://docs.microsoft.com/en-us/azure/virtual-machines/manage-availability#use-availability-zones-to-protect-from-datacenter-level-failures
 2. Work with the partners and design interaction between services such that one service breakdown is not amplified in a cascading fashion to all upstreams

courses/systems_design/intro.md

@@ -3,9 +3,11 @@
 ## Prerequisites
 
 Fundamentals of common software system components:
-- Operating Systems
-- Networking
-- Databases RDBMS/NoSQL
+
+- [Linux Basics](https://linkedin.github.io/school-of-sre/linux_basics/intro/)
+- [Linux Networking](https://linkedin.github.io/school-of-sre/linux_networking/intro/)
+- Databases RDBMS
+- [NoSQL Concepts](https://linkedin.github.io/school-of-sre/databases_nosql/intro/)
 
 ## What to expect from this course
 
@@ -17,9 +19,7 @@ Individual software components’ scalability and reliability concerns like e.g.
 
 More light will be shed on concepts rather than on setting up and configuring components like Loadbalancers to achieve scalability, availability and reliability of systems
 
-## Course Content
-
-### Table of Contents
+## Course Contents
 
 - [Introduction](https://linkedin.github.io/school-of-sre/systems_design/intro/#backstory)
 - [Scalability](https://linkedin.github.io/school-of-sre/systems_design/scalability/)

courses/systems_design/scalability.md

@@ -171,7 +171,7 @@ Here the whole data centre is split and replicated and clients are directed to a
 
 
 
-## SRE Use cases
+## Applications in SRE role
 1. SREs in coordination with the network team work on how to map users traffic to a particular site. 
 https://engineering.linkedin.com/blog/2017/05/trafficshift--load-testing-at-scale
 2. SREs work closely with the Dev team to split monoliths to multiple microservices that are easy to run and manage