From e400493b30e357fbca892381e82a50d68ace5a24 Mon Sep 17 00:00:00 2001 From: dmiller Date: Fri, 8 Sep 2017 18:10:16 +0000 Subject: [PATCH] Some grammar fixes in the refguide. Closes #992 --- docs/refguide.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/refguide.xml b/docs/refguide.xml index e1450aa33..039eea079 100644 --- a/docs/refguide.xml +++ b/docs/refguide.xml @@ -3012,7 +3012,7 @@ Use nmap -V to see which engines are supported. While the fine-grained timing controls discussed in the previous section are powerful and effective, some people find them confusing. Moreover, choosing the appropriate values can sometimes take more time -than the scan you are trying to optimize. So Nmap offers a simpler +than the scan you are trying to optimize. Fortunately, Nmap offers a simpler approach, with six timing templates. You can specify them with the option and their number (0–5) or their name. The template names are @@ -3041,7 +3041,7 @@ fine-grained control options do not currently exist. For example, prohibits the dynamic scan delay from exceeding 10 ms for TCP ports and caps that value at 5 ms. Templates can be used in combination with fine-grained -controls, and the fine-grained controls that you specify take +controls, and the fine-grained controls that you specify will take precedence over the timing template default for that parameter. I recommend using when scanning reasonably modern and reliable networks. Keep that option even when you add