Update README.md

Author: vyclu20

README.md

@@ -15,7 +15,7 @@ The database consisted of four tables:
 
 > BookCopy: 3 columns "ISBN" (text), "copyNumber" (integer), and "daysLoaned" (integer). These columns are to store information about copies of books, such as their ISBN number, copy number (which would indicate which copy of one book is being borrowed), and the cumulative number of days the copy has been loaned out. The table BookEdition contains many more books than the library can possibly buy, and so SCML may have zero, one or more actual copies of each of the books listed in BookEdition.
 
-> loan: 5 columns "clientId" (integer), "ISBN" (text), "copyNumber" (integer), "dateOut" (text), and "dateBack" (text). These columns are to store information about loans, such as the client ID, ISBN number of the book loaned, the copy number of the book, the dates the book was checked out and the book was returned in YYYY-MM-DD form. Anytime a new tuple is entered into the table loan on the day that the book is loaned out, with the value NULL assigned to the column dateBack, and when a book is returned an update statement is to run to update daysLoaned column in the BookCopy table.
+> loan: 5 columns "clientId" (integer), "ISBN" (text), "copyNumber" (integer), "dateOut" (text), and "dateBack" (text). These columns are to store information about loans, such as the client ID, ISBN number of the book loaned, the copy number of the book, the dates the book was checked out and the book was returned in YYYY-MM-DD form. Anytime a new tuple is entered into the table loan on the day that the book is loaned out, with the value NULL assigned to the column dateBack, and when a book is returned an update statement is to run to update daysLoaned column in the BookCopy table. This is where the trigger comes in handy.
 
 > Client: 3 columns "clientId" (integer), "name" (text), and "residence" (text). These columns are to store information about clients, such as their unique client ID, name, and residence. Each client has a unique clientId and the library also keeps information about the client’s name and their aged-care residence and a client can be registered in the Client table even if they have not (yet) borrowed any books.