Clean: reformatted README.md and 'git_conventions.md' with MarkDown syntax.

README.md

 # widget_django unchained
-== AUTHORS ==
-John Raymon Yu - Assignments
-Jose Emmanuel B. Laurel - Homepage
-Joshua Graham Son - Announcements
-Ray Rafael Abenido - Forum
 
-== LAB SUBMISSIONS ==
-Lab 1 Video Link: https://youtu.be/QsmKkNtBzik
\ No newline at end of file
+# AUTHORS
+1. John Raymon Yu - Assignments
+2. Jose Emmanuel B. Laurel - Homepage
+3. Joshua Graham Son - Announcements
+4. Ray Rafael Abenido - Forum
+
+# LAB SUBMISSIONS
+1. Lab 1 Video Link: https://youtu.be/QsmKkNtBzik
\ No newline at end of file

git_conventions.md

@@ -18,28 +18,29 @@ will be cases where the new conventions you added will be needed.
 Thanks! ~ Ray
 
 ## GIT CONVENTIONS (AS OF 04/02/2022)
+# GENERAL RULES
 Git messages should be as follows:
 > SUBJECT: A summary of what you did
 
 An example. <i> New Feature: added a new database named 'ID' in homepage. </i>
 
 As much as possible, your git messages should follow these guidelines.
-- Your git messages should be two or three sentences at most. Two is best.
-- Each sentence should communicate intent, explicitly, and <b>not vague</b>.
-
-<b> Types of Subject </b>
-- Fix: if you fixed a bug in the project. 
-- Style: if you're changes you make has an impact on the GUI. 
-- Improvement: if you made an improvements on pre-existing feature
-- Clean: if you cleaned messy code by reformatting, restructuring, changing
+1. Your git messages should be two or three sentences at most. Two is best.
+2. Each sentence should communicate intent, explicitly, and <b>not vague</b>.
+
+# Types of Subject
+1. Fix: if you fixed a bug in the project. 
+2. Style: if you're changes you make has an impact on the GUI. 
+3. Improvement: if you made an improvements on pre-existing feature
+4. Clean: if you cleaned messy code by reformatting, restructuring, changing
 variable, function, or class names, etc.
-- Meta: if you have modified the README.md file or added new files that are
+5. Meta: if you have modified the README.md file or added new files that are
 not part of the project itself but provides information to programmers on how 
 to write the program
-- Others: if it doesn't fit in with the any of the above. AS MUCH AS POSSIBLE
+6. Others: if it doesn't fit in with the any of the above. AS MUCH AS POSSIBLE
 AVOID THIS. 
 
-<b> Other Guidelines </b>
-- One commit message can have multiple subjects. For example, "New Feature: 
+# Other Guidelines
+1. One commit message can have multiple subjects. For example, "New Feature: 
 added foo. Clean: reformatted views.py of homepage." However, the next subject 
 must be in a newline.