diff --git a/docs/source/the_project/quickstart.rst b/docs/source/the_project/quickstart.rst
index 07a0db3..2a45bea 100644
--- a/docs/source/the_project/quickstart.rst
+++ b/docs/source/the_project/quickstart.rst
@@ -24,15 +24,11 @@ Scenario
 Limitations and constraints
 --------------------------
 
-1. We **don't want** to **grant access** to the :samp:`External Host` to
-anybody.
-2. We **don't want** to manage VPNs or any similar solutions to access to
-:samp:`Internal Host` from the Internet.
-3. We **want to limit the actions** that an user can perform in our intranet
-while it is checking if :samp:`Internal Host` is alive.
-4. We **want** to use the most standard mechanism.  Easy to use and that
-facilitates the automation.
-5. We **don't have a budget** to invest in a custom solution.
+  1. We **don't want** to **grant access** to the :samp:`External Host` to anybody.
+  2. We **don't want** to manage VPNs or any similar solutions to access to :samp:`Internal Host` from the Internet.
+  3. We **want to limit the actions** that an user can perform in our intranet while it is checking if :samp:`Internal Host` is alive.
+  4. We **want** to use the most standard mechanism.  Easy to use and that facilitates the automation.
+  5. We **don't have a budget** to invest in a custom solution.
 
 
 What options we have?
@@ -57,8 +53,7 @@ Accessing via SSH to :samp:`External Host`
 
     1. We need to manage users (violates a constraint)
     2. We need to grant access for users to system (violates a constraint)
-    3. We can't control what :samp:`ping` options the user can use to ping
-    :samp:`Internal Host` (violates a constraint)
+    3. We can't control what :samp:`ping` options the user can use to ping :samp:`Internal Host` (violates a constraint)
 
 
 Develop and deploy a custom solution