fix formatting

Author: Shrreya

module1-introduction-to-backend/r1-introduction-to-backend/README.md

@@ -24,7 +24,7 @@ But where does all the data to be displayed on the frontend come from? How is a
 
 A backend developer builds and maintains the code that powers those components which together enable the user-facing side of the website to even exist in the first place. Backend developers must be competent with one or more server-side languages such as JavaScript (Node.js), Ruby, Python, PHP or Java, frameworks like ExpressJS, Ruby on Rails, Python Django and databases like MySQL, PostgreSQL or MongoDB. They are also familiar with Linux as a deployment environment and DevOps tools like AWS, GCP, Apache, Nginx, Docker and Kubernetes.
 
-Backend developers need to be able to navigate across larger codebases and not get lost in the complexities of what may seem like programming labyrinths. They also need to be very meticulous when making changes to not "break" anything as there are usually delicate dependencies. Even frontend codebases are large and complex with delicate dependencies, but unlike frontend development where the written code translates directly to visual output one can see and interact with, backend development of business logic is often hard to visualise. Therefore to be a good backend developer, you need to be comfortable with dealing with abstracts.
+Backend developers need to be able to navigate across larger codebases and not get lost in the complexities. They also need to be very meticulous when making changes to not "break" anything as there are usually delicate dependencies. Even frontend codebases are large and complex with delicate dependencies, but unlike frontend development where the written code translates directly to visual output one can see and interact with, backend development of business logic is often hard to visualise. Therefore to be a good backend developer, you need to be comfortable with dealing with abstracts.
 
 <img src="https://drive.google.com/uc?export=view&id=1PkIrF_pNnGbX1NiW-q1JIKokql1v4FI7" width="50%">
 
@@ -37,7 +37,7 @@ To be a good fullstack developer, you need to be comfortable with dealing with a
 
 <img src="https://drive.google.com/uc?export=view&id=13hdTlUW0tk0J91wV-r7ruPX7uATpt9pe" width="50%">
 
-## Backend web architecture
+## Backend Web Architecture
 Let's start diving deeper into what do we mean when we say frontend and backend. The frontend is the code that is executed on the client side. This code runs in the user’s browser and creates the user interface. The backend is the code that runs on the server, receives requests from the clients, and contains the logic to send the appropriate data back to the client. The backend also includes the database, which will persistently store all of the data for the application.
 
 ### What are clients?

module1-introduction-to-backend/r1.1-beginners-guide-nodejs-npm/README.md

@@ -12,7 +12,7 @@ But to be specific, Node.js is an open-source, cross-platform, backend JavaScrip
 
 And here is what a common Hello World code in Node.js would look like:
 
-```
+```js
 const http = require('http')
 
 const hostname = '127.0.0.1'

module1-introduction-to-backend/r2.1-diving-into-rest-apis/README.md

@@ -20,7 +20,7 @@ HTTP defines a set of request methods to indicate the desired action to be perfo
 
 While developing APIs, GET and POST are the most commonly and frequently used methods.
 
-## Structure of a HTTP Request
+## Structure of an HTTP Request
 
 HTTP requests, and responses, share similar structure and are composed of:
 1. A start-line describing the requests to be implemented, or its status of whether successful or a failure. This start-line is always a single line.
@@ -67,7 +67,7 @@ Bodies can be broadly divided into two categories:
 - Single-resource bodies, consisting of one single file, defined by the two headers: Content-Type and Content-Length.
 - Multiple-resource bodies, consisting of a multipart body, each containing a different bit of information. This is typically associated with HTML Forms.
 
-## Structure of a HTTP Response
+## Structure of an HTTP Response
 
 The structure is similar to HTTP Requests.
 

module1-introduction-to-backend/r3-introduction-to-expressjs/README.md

@@ -17,7 +17,7 @@ While Express itself is fairly minimalist, developers have created compatible mi
 
 This probably looks quite similar to the Hello World example of plain Node.js.
 
-```
+```js
 const express = require('express');
 const app = express();
 const port = 3000;

module1-introduction-to-backend/r3.4-api-best-practices/README.md

@@ -26,7 +26,7 @@ Please note: This list is not necessarily exhaustive and there is always room fo
 REST APIs should accept JSON for request payload and also send responses to JSON. JSON is the standard for transferring data. Almost every networked technology can use it: JavaScript has built-in methods to encode and decode JSON either through the Fetch API or another HTTP client. Server-side technologies have libraries that can decode JSON without doing much work.
 
 In Express, we can use the body-parser middleware to parse the JSON request body.
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 
@@ -49,7 +49,7 @@ For example, we should create routes like GET `/articles` for getting news artic
 The combination of the HTTP verb and resource noun convey the purpose of an API endpoint. API endpoints like GET `/fetchArticles` or POST `/update-articles` use redundant verbs like "fetch" and "update" which is not required.
 
 In Express, we can write these endpoints as:
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 
@@ -89,7 +89,7 @@ When designing endpoints, it makes sense to group those that contain associated
 For example, if we want an endpoint to get the comments for a news article, we should append the `/comments` path to the end of the `/articles` path.
 
 In Express, we can write this as:
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 
@@ -123,7 +123,7 @@ To eliminate confusion for API users when an error occurs, we should handle erro
 Along with error codes, try to provide good feedback through your response messages. Good feedback involves positive validation on correct implementation, and an informative error on incorrect implementation that can help users debug and correct the way they use the product. Describe your error responses well, but keep them concise and neat.
 
 For example, if we want to reject the data from the request payload, then we should return a 400 response as follows in an Express API:
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 
@@ -153,7 +153,7 @@ app.listen(3000, () => console.log('server started'));
 The databases behind a REST API can get very large. Sometimes, there’s so much data that it shouldn’t be returned all at once because it’s way too slow or will bring down our systems. Therefore, we need ways to filter items. We also need ways to paginate data so that we only return a few results at a time. We don’t want to tie up resources for too long by trying to get all the requested data at once. Filtering and pagination both increase performance by reducing the usage of server resources.
 
 Here’s a small example where an API can accept a query string with various query parameters to let us filter out items by their fields:
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 
@@ -209,7 +209,7 @@ This way, we can gradually phase out old endpoints instead of forcing everyone t
 Versioning is usually done with `/v1/`, `/v2/`, etc. added at the start of the API path.
 
 For example, we can do that with Express as follows:
-```
+```js
 const express = require('express');
 const bodyParser = require('body-parser');
 const app = express();

module1-introduction-to-backend/r4-server-side-validation/README.md

@@ -24,7 +24,7 @@ You might be thinking do I have to write a bunch of if statements within my API
 We will be learning to use [express-validator](https://express-validator.github.io/docs/) in the next assignment.
 
 Consider this piece of code:
-```
+```js
 // ...initial code omitted for simplicity
 const { body, validationResult } = require('express-validator');
 
@@ -47,7 +47,7 @@ app.post(
 ```
 
 Now, whenever a request that includes invalid username or password fields is submitted, your server will respond with a 400 error response like this:
-```
+```json
 {
   "errors": [
     {