@@ -582,10 +582,11 @@ edit it, and return the clone. This ensures that no other functions that are
 holding onto a reference of the shopping cart will be affected by any changes.
 
 Two caveats to mention to this approach:
-1. There might be cases where you actually want to modify the input object,
+1. There might be cases where you actually want to modify the input object,
 but when you adopt this programming practice you will find that those case
 are pretty rare. Most things can be refactored to have no side effects!
-2. Cloning big objects can be very expensive in terms of performance. Luckily,
+
+2. Cloning big objects can be very expensive in terms of performance. Luckily,
 this isn't a big issue in practice because there are
 [https://facebook..io/immutable-js/](great libraries) that allow
 this kind of programming approach to be fast and not as memory intensive as