From da693d32b8c00cb389559e73be8d1dc65f9b9af2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=C3=A9ctor=20Hurtado?= Date: Wed, 27 Nov 2019 10:02:35 +0100 Subject: [PATCH] Fix some typos in 'The Project' section --- docs/source/the_project/quickstart.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/source/the_project/quickstart.rst b/docs/source/the_project/quickstart.rst index 0ae647b..07a0db3 100644 --- a/docs/source/the_project/quickstart.rst +++ b/docs/source/the_project/quickstart.rst @@ -24,22 +24,22 @@ Scenario Limitations and constraints -------------------------- - #. We **don't want** to **grant access** to the :samp:`External Host` to - anybody. - #. We **don't want** to manage VPNs or any similar solutions to access to - *Internal Host* from the Internet. - #. We **want to limit the actions** that an user can perform in our intranet - while it is checking if :samp:`Internal Host` is alive. - #. We **want** to use the most standard mechanism. Easy to use and that - facilitates the automation. - #. 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? --------------------- Alter analyzyng the problem and our goal we conclude that is enough - **to use a simple** :samp:`ping` **to** :samp:`Internal Host`**.** + **to use a simple** :samp:`ping` **to** :samp:`Internal Host`. So, the next step is to **analyze how to perform the ping.**