add status codes, id to reqs

also remove model schema diff

Author: osamaakb

module3-crud-and-data-models/r1-schema-and-data-models/README.md

@@ -33,10 +33,6 @@ CREATE TABLE customer (
 
 We can see that the schema definition for the `customer` has a `name` which is a type `string` and a `zipcode` that is of type `number`.
 
-### The Difference between data model and schema
-
-The database schema is one that contains list of attributes and instructions to tell the database engine how data is organised whereas data model is a collection of conceptional tools for describing data, data-relationship and consistency constraints.
-
 ## Introduction to CRUD operations
 
 When we are building APIs, we want our models to provide four basic types of functionality. The model must be able to Create, Read, Update, and Delete resources. Computer scientists often refer to these functions by the acronym `CRUD`. A model should have the ability to perform at most these four functions in order to be complete.
@@ -85,16 +81,16 @@ Note: Use `PUT` when you want to modify a singular resource which is already a p
 
 ##### Request:
 
-`PUT http://www.myrestaurant.com/dishes/1223`
+`PUT http://www.myrestaurant.com/dishes/:id`
 
 #### Delete
 
 The CRUD operation Delete corresponds to the HTTP method DELETE. It is used to remove a resource from the system.
-Let’s say that the world avocado shortage has reached a critical point, and we can no longer afford to serve this modern delicacy at all. We should go into the database and delete the item that corresponds to `"Avocado Toast"`, which we know has an `id` of 1223.
+Let’s say that the world avocado shortage has reached a critical point, and we can no longer afford to serve this modern delicacy at all. We should go into the database and delete the item that corresponds to `Avocado Toast`, which we know has an `id` of 1223.
 
 ##### Request:
 
-`DELETE http://www.myrestaurant.com/dishes/1223`
+`DELETE http://www.myrestaurant.com/dishes/:id`
 
 ## Resources
 

module3-crud-and-data-models/r1.1-principles-of-setting-up-your-schema/README.md

@@ -10,8 +10,7 @@ Most developers don't see the difference between relational database schema and
 
 <img src="https://i.imgur.com/3yobiPB.jpg" alt="meme" width="400"/>
 
-In a nutshell,
-in relational databases, models are usually independent of queries, there is no duplication of data as data will _mostly_ be separated into different tables, and it is rigid, you will have to define types and fields for your schema beforehand.
+In a nutshell, in relational databases, models are usually independent of queries, there is no duplication of data as data will _mostly_ be separated into different tables, and it is rigid, you will have to define types and fields for your schema beforehand.
 
 in the other hand, `MongoDB`, you have more flexibility, there are no rules, documents can have new data or fields at any point of time, no need to define types.
 

module3-crud-and-data-models/r3.2-models-and-controllers-in-mongoose/README.md

@@ -66,7 +66,7 @@ Example:
 app.post("/food", async (request, response) => {
   const food = new foodModel(request.body);
   await food.save();
-  response.send(food);
+  response.status(201).send(food);
 });
 
 // ...
@@ -81,7 +81,7 @@ Example:
 ```js
 // ...
 
-app.patch("/food/:id", async (request, response) => {
+app.put("/food/:id", async (request, response) => {
     await foodModel.findByIdAndUpdate(request.params.id, request.body);
     await foodModel.save();
     response.send(food);
@@ -104,7 +104,7 @@ app.delete("/food/:id", async (request, response) => {
     const food = await foodModel.findByIdAndDelete(request.params.id);
 
     if (!food) response.status(404).send("No item found");
-    response.status(200).send();
+    response.status(204).send();
   }
 });