From 60a6c03cdf4fca23895c37056c09bbe667aa538c Mon Sep 17 00:00:00 2001 From: Thomas Markwalder Date: Thu, 30 Aug 2018 08:54:32 -0400 Subject: [PATCH] [#14,!4] Addressed review comments. Clarified (hopefully) text in admin guide. --- doc/guide/hooks.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/guide/hooks.xml b/doc/guide/hooks.xml index 6b96216419..ad8e7619f1 100644 --- a/doc/guide/hooks.xml +++ b/doc/guide/hooks.xml @@ -1422,11 +1422,11 @@ Requirements document. In other words, they are not specific to any subnet. When reservations are supplied via the configuration file, the ID of the containing subnet (or lack thereof) is implicit in the configuration structure. - In order to manage reservations in a data store however, it is - necessary to identify the scope to which the reservation belongs, - along with any other host command parameters. For global reservations, - use a value of zero (0) for subnet-id. For subnet - level reservations, use the ID of the owning subnet. + However, when managing reservations using the host commands, it is + necessary to explicitly identify the scope to which the reservation + belongs. This is done via the subnet-id parameter. + For global reservations, use a value of zero (0). For reservations + scoped to a specific subnet, use that subnet's ID. -- 2.47.2