doc/db/README.md

@@ -15,15 +15,15 @@ Thus, here is the current (October '24) model and the reasoning behind it:
 
 There are 2 main types:
 
-    1. **Trips:** Trips can be created by every cox. They are "simple", every-day trips.
+1. **Trips:** Trips can be created by every cox. They are "simple", every-day trips.
-    2. **Events:** Events can be created by everyone who has the `manage_events` role. They are used if multiple coxes are needed, e.g. for "Fetzenfahrt", "Anrudern", .... Additionally, events are shown in public calendar (e.g. on the website).
+2. **Events:** Events can be created by everyone who has the `manage_events` role. They are used if multiple coxes are needed, e.g. for "Fetzenfahrt", "Anrudern", .... Additionally, events are shown in public calendar (e.g. on the website).
 
 `TripDetails` extracts the common data for both Trips and Events.
 Rower can register using the `UserTrip` table. 
 This table expects either...
 
-    - a `user_id`, if a person who has an account registers to the trip/event
+- a `user_id`, if a person who has an account registers to the trip/event
-    - a `user_note`, if the cox of a trip, or a `manage_events` user of an event wants to add a guest which has no account
+- a `user_note`, if the cox of a trip, or a `manage_events` user of an event wants to add a guest which has no account
 
 - **Logbook**
 ![](./logbook.svg)