diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..d62ddbb
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+*.pdf
+*.txt
diff --git a/lab01.pdf b/lab01.pdf
deleted file mode 100644
index 482bcf2..0000000
Binary files a/lab01.pdf and /dev/null differ
diff --git a/lab02.pdf b/lab02.pdf
deleted file mode 100644
index d3fca80..0000000
Binary files a/lab02.pdf and /dev/null differ
diff --git a/lab03-eerd.pdf b/lab03-eerd.pdf
deleted file mode 100644
index 1af54eb..0000000
Binary files a/lab03-eerd.pdf and /dev/null differ
diff --git a/lab03.pdf b/lab03.pdf
deleted file mode 100644
index af62594..0000000
Binary files a/lab03.pdf and /dev/null differ
diff --git a/lab6_reflection.txt b/lab6_reflection.txt
deleted file mode 100644
index 30cf686..0000000
--- a/lab6_reflection.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Almost all the tables and or constraints caused errors, so I had to spend a lot of time, updating the lab5 schema sql file to accomodate the data given for lab 6 as well as update some constraints to ensure all the insertions worked as intended.
-
-Here is an example of some of the error messages given while attemping to delete data in task 4 that is referenced by entities in other tables.
-
-psql:lab6_dml.sql:322: ERROR:  update or delete on table "department" violates foreign key constraint "professor_dep_code_fkey" on table "professor"
-DETAIL:  Key (dep_code)=(COMP) is still referenced from table "professor".
-psql:lab6_dml.sql:325: ERROR:  column "off_sectoin" does not exist
-LINE 2: WHERE off_sectoin = 'L2';
-              ^
-HINT:  Perhaps you meant to reference the column "course_offering.off_section".
-psql:lab6_dml.sql:328: ERROR:  update or delete on table "location" violates foreign key constraint "department_loc_code_fkey" on table "department"
-DETAIL:  Key (loc_code)=(SE12 260) is still referenced from table "department".
-
-Finally, I think the schema is much better not only to fit the data given but being correct and making sense logically on what data should be there, and what their constraints should be to better reflect the real world.
diff --git a/lab7_reflection_Sowinski_Braeden.txt b/lab7_reflection_Sowinski_Braeden.txt
deleted file mode 100644
index a89f913..0000000
--- a/lab7_reflection_Sowinski_Braeden.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-Yes, all of the row counts make sense, there may be some duplicatoin.
-For example, when we are getting all student ids, and their enrollments, there may be duplicate enrollment data.
-i.e. two students are enrolled in the same course_offering. However, we since we are showing the student_id we are able to tell them apart.
-
-I dont think distinct would change the result in the example above, there is student x enrolled in class A, and student y enrolled in class A too. Those are already distinct.
-
-I think for the most part I am selecting the minimul necessary columns, only showing relavent related information.
-
-Unless asked to show all data of a table.