doc: replace 'intact' keyword with something more clear

Keeping the config intact might be misunderstood. I say that even if VRF
netns is automatically discovered, it is possible for administrator to
save the netns information in the config file, to bring more clarity (
hence the config commands available).

Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>

diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst
index d28669506388daf2eb301ad3ffd39273e98be516..b6060f0737312e62f133a12512b03ac7c727f3ed 100644 (file)
--- a/doc/user/zebra.rst
+++ b/doc/user/zebra.rst
@@ -464,8 +464,9 @@ commands in relationship to VRF. Here is an extract of some of those commands:
 
    This command is available on configuration mode. By default, above command
    permits accessing the vrf configuration mode. This mode is available for
-   both VRFs. It is to be noted that *Zebra* does not create *Linux VRF*.
-   Provisioning this command is used to keep the configuration intact.
+   both VRFs. It is to be noted that *Zebra* does not create Linux VRF.
+   The network administrator can however decide to provision this command in
+   configuration file to provide more clarity about the intended configuration.
 
 .. index:: netns NAMESPACE
 .. clicmd:: netns NAMESPACE
@@ -474,8 +475,9 @@ commands in relationship to VRF. Here is an extract of some of those commands:
    when *Zebra* is run in :option:`-n` mode. This command reflects which *Linux
    network namespace* is to be mapped with *Zebra* VRF. It is to be noted that
    *Zebra* creates and detects added/suppressed VRFs from the Linux environment
-   (in fact, those managed with iproute2). Provisioning this command is used to
-   keep the configuration intact.
+   (in fact, those managed with iproute2). The network administrator can however
+   decide to provision this command in configuration file to provide more clarity
+   about the intended configuration.
 
 .. index:: ip route NETWORK NETMASK GATEWAY NEXTHOPVRF
 .. clicmd:: ip route NETWORK NETMASK GATEWAY NEXTHOPVRF