diff --git a/docs/books/api_design_patterns/part1/chapter1.md b/docs/books/api_design_patterns/part1/chapter1.md
index 11a0afe..f6c68d9 100644
--- a/docs/books/api_design_patterns/part1/chapter1.md
+++ b/docs/books/api_design_patterns/part1/chapter1.md
@@ -33,7 +33,7 @@ Consider the following API method names:
 4. `CancelReservation()`
 5. `RescheduleFlight()`
 6. `UpgradeTrip()`
-
+<br>
 - Each one of these RPCs is pretty descriptive, but we have to memorize these methods, each of which is subtly different. 
     - e.g. sometimes we talk about flight, other times we talk about a trip or a reservation.
 - We also need to memorise which action is used in the method.
@@ -46,7 +46,7 @@ We need to standardise, by providing a standard set of building blocks - method-
 3. `ListFlightReservation()`
 4. `DeleteFlightReservation()`
 5. `UpdateFlightReservation()`
-
+<br>
 - Resource-oriented APIs will be much easier for users to learn, understand and remember.
     - Standardisation makes it easy to combine what you already know (set of standard actions) which the resource which is easy to learn.