docs (level 101): fix typos, punctuation, formatting

courses/CODE_OF_CONDUCT.md

@@ -25,7 +25,7 @@ Note: Some LinkedIn-managed communities have codes of conduct that pre-date this
 
 We encourage all communities to resolve issues on their own whenever possible. This builds a broader and deeper understanding and ultimately a healthier interaction. In the event that an issue cannot be resolved locally, please feel free to report your concerns by contacting [oss@linkedin.com](mailto:oss@linkedin.com).
 
-In your report please include:
+In your report, please include:
 
 *   Your contact information.
 *   Names (real, usernames or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well.

courses/CONTRIBUTING.md

@@ -7,16 +7,16 @@ As a contributor, you represent that the content you submit is not plagiarised.
 ### Contributing Guidelines
 Ensure that you adhere to the following guidelines:
 
-* Should be about principles and concepts that can be applied in any company or individual project. Do not focus on particular tools or tech stack(which usually change over time).
+* Should be about principles and concepts that can be applied in any company or individual project. Do not focus on particular tools or tech stack (which usually change over time).
 * Adhere to the [Code of Conduct](/school-of-sre/CODE_OF_CONDUCT/).
 * Should be relevant to the roles and responsibilities of an SRE.
-* Should be locally tested (see steps for testing) and well formatted.
+* Should be locally tested (see steps for testing) and well-formatted.
 * It is good practice to open an issue first and discuss your changes before submitting a pull request. This way, you can incorporate ideas from others before you even start.
 
 ### Building and testing locally
 Run the following commands to build and view the site locally before opening a PR.
 
-```
+```shell
 python3 -m venv .venv
 source .venv/bin/activate
 pip install -r requirements.txt

courses/index.md

@@ -2,16 +2,16 @@
 
 <img src="img/sos.png" width=200 >
 
-Site Reliability Engineers (SREs)  sits at the intersection of software engineering and systems engineering. While there are potentially infinite permutations and combinations of how infrastructure and software components can be put together to achieve an objective, focusing on foundational skills allows SREs to work with complex systems and software, regardless of whether these systems are proprietary, 3rd party, open systems, run on cloud/on-prem infrastructure, etc. Particularly important is to gain a deep understanding of how these areas of systems and infrastructure relate to each other and interact with each other. The combination of software and systems engineering skills is rare and is generally built over time with exposure to a wide variety of infrastructure, systems, and software. 
+Site Reliability Engineers (SREs) sits at the intersection of software engineering and systems engineering. While there are potentially infinite permutations and combinations of how infrastructure and software components can be put together to achieve an objective, focusing on foundational skills allows SREs to work with complex systems and software, regardless of whether these systems are proprietary, 3rd party, open systems, run on cloud/on-prem infrastructure, etc. Particularly, it is important to gain a deep understanding of how these areas of systems and infrastructure relate to each other and interact with each other. The combination of software and systems engineering skills is rare and is generally built over time with exposure to a wide variety of infrastructure, systems, and software. 
 
 SREs bring in engineering practices to keep the site up. Each distributed system is an agglomeration of many components. SREs validate business requirements, convert them to SLAs for each of the components that constitute the distributed system, monitor and measure adherence to SLAs, re-architect or scale out to mitigate or avoid SLA breaches, add these learnings as feedback to new systems or projects and thereby reduce operational toil. Hence SREs play a vital role right from the day 0 design of the system. 
 
-In early 2019, we started visiting campuses across India to recruit the best and brightest minds to make sure LinkedIn, and all the services that make up its complex technology stack are always available for everyone. This critical function at LinkedIn falls under the purview of the Site Engineering team and Site Reliability Engineers (SREs) who are Software Engineers, specialized in reliability. 
+In early 2019, we started visiting campuses across India to recruit the best and brightest minds to make sure LinkedIn and all the services that make up its complex technology stack are always available for everyone. This critical function at LinkedIn falls under the purview of the Site Engineering team and Site Reliability Engineers (SREs) who are Software Engineers, specialized in reliability. 
 
-As we continued on this journey we started getting a lot of questions from these campuses on what exactly the site reliability engineering role entails? And, how could someone learn the skills and the disciplines involved to become a successful site reliability engineer? Fast forward a few months, and a few of these campus students had joined LinkedIn either as interns or as full-time engineers to become a part of the Site Engineering team; we also had a few lateral hires who joined our organization who were not from a traditional SRE background. That's when a few of us got together and started to think about how we can onboard new graduate engineers to the Site Engineering team.
+As we continued on this journey, we started getting a lot of questions from these campuses on what exactly the site reliability engineering role entails? And, how could someone learn the skills and the disciplines involved to become a successful site reliability engineer? Fast forward a few months, and a few of these campus students had joined LinkedIn either as interns or as full-time engineers to become a part of the Site Engineering team; we also had a few lateral hires who joined our organization who were not from a traditional SRE background. That's when a few of us got together and started to think about how we can onboard new graduate engineers to the Site Engineering team.
 
 There are very few resources out there guiding someone on the basic skill sets one has to acquire as a beginner SRE. Because of the lack of these resources, we felt that individuals have a tough time getting into open positions in the industry. We created the School Of SRE as a starting point for anyone wanting to build their career as an SRE.
-In this course, we are focusing on building strong foundational skills. The course is structured in a way to provide more real life examples and how learning each of these topics can play an important role in day to day job responsibilities of an SRE. Currently we are covering the following topics under the School Of SRE:
+In this course, we are focusing on building strong foundational skills. The course is structured in a way to provide more real life examples and how learning each of these topics can play an important role in day-to-day job responsibilities of an SRE. Currently, we are covering the following topics under the School Of SRE:
 
 -   Level 101
     -   Fundamentals Series
@@ -20,8 +20,8 @@ In this course, we are focusing on building strong foundational skills. The cour
         -   [Linux Networking](https://linkedin.github.io/school-of-sre/level101/linux_networking/intro/)
     -   [Python and Web](https://linkedin.github.io/school-of-sre/level101/python_web/intro/)
     -   Data
-        - [Relational databases(MySQL)](https://linkedin.github.io/school-of-sre/level101/databases_sql/intro/)
-        -   [NoSQL concepts](https://linkedin.github.io/school-of-sre/level101/databases_nosql/intro/)
+        - [Relational Databases (MySQL)](https://linkedin.github.io/school-of-sre/level101/databases_sql/intro/)
+        -   [NoSQL Concepts](https://linkedin.github.io/school-of-sre/level101/databases_nosql/intro/)
         -   [Big Data](https://linkedin.github.io/school-of-sre/level101/big_data/intro/)
     -   [Systems Design](https://linkedin.github.io/school-of-sre/level101/systems_design/intro/)
     -   [Metrics and Monitoring](https://linkedin.github.io/school-of-sre/level101/metrics_and_monitoring/introduction/)
@@ -30,11 +30,11 @@ In this course, we are focusing on building strong foundational skills. The cour
 -   Level 102
     -   [Linux Intermediate](https://linkedin.github.io/school-of-sre/level102/linux_intermediate/introduction/)
     -   Linux Advanced
-        -   [Containers and orchestration](https://linkedin.github.io/school-of-sre/level102/containerization_and_orchestration/intro/)
+        -   [Containers and Orchestration](https://linkedin.github.io/school-of-sre/level102/containerization_and_orchestration/intro/)
         -   [System Calls and Signals](https://linkedin.github.io/school-of-sre/level102/system_calls_and_signals/intro/)
     -   [Networking](https://linkedin.github.io/school-of-sre/level102/networking/introduction/)
     -   [System Design](https://linkedin.github.io/school-of-sre/level102/system_design/intro/)
-    -   [System troubleshooting and performance improvements](https://linkedin.github.io/school-of-sre/level102/system_troubleshooting_and_performance/introduction/) 
+    -   [System Troubleshooting and Performance Improvements](https://linkedin.github.io/school-of-sre/level102/system_troubleshooting_and_performance/introduction/) 
     -   [Continuous Integration and Continuous Delivery](https://linkedin.github.io/school-of-sre/level102/continuous_integration_and_continuous_delivery/introduction/)
 
 We believe continuous learning will help in acquiring deeper knowledge and competencies in order to expand your skill sets, every module has added references that could be a guide for further learning. Our hope is that by going through these modules we should be able to build the essential skills required for a Site Reliability Engineer.