From bd4257e790d66cb3f3865b2047be4743d8f5201d Mon Sep 17 00:00:00 2001
From: Imbus <>
Date: Sat, 4 May 2024 13:32:53 +0200
Subject: [PATCH] markdown syntax errors

---
 README.md | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 05520aa..375bc08 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 > Krusty Kookies is a bakery which specializes in cookies, and they need a database to keep track of their production and deliveries.
 
-### Base tables
+## Base tables
 
 Unsuprisingly, we will need a cookie table.
 
@@ -90,13 +90,6 @@ This suggests that we may need to relate pallets to customers via a truck entity
 Again, the truck as an entity is irrelevant and we only need a table to keep track of what pallet was delivered to what customer along with a date.
 
 ```sql
-CREATE TABLE deliveries (
-    delivery_id INT PRIMARY KEY,
-    pallet_id INT NOT NULL,
-    customer_name VARCHAR(50) NOT NULL,
-    delivery_date DATE NOT NULL DEFAULT CURRENT_DATE CHECK (delivery_date >= CURRENT_DATE),
-    FOREIGN KEY (pallet_id) REFERENCES pallets(pallet_id)
-);
 ```
 
 > Orders must be registered in the database, and, for production planning purposes, the company must be able to see all orders which are to be delivered during a specific time period.
@@ -124,8 +117,12 @@ This should all be possible with a simple join query.
 
 > Blocked products are of special interest. The company needs to find out **which products are blocked**, and also which pallets contain a certain blocked product.
 
+As well as:
+
 > Finally, they must be able to check **which pallets have been delivered** to a given customer, and the date and time of delivery.
 
+And:
+
 > Orders must be registered in the database, and, for production planning purposes, the company must be able to see all orders which are to be **delivered during a specific time period**.
 
 These are all trivial queries.