net-update docs: s/domain/network/

A leftover from copy paste.
(cherry picked from commit d1236faa)

tools/virsh-network.c

@@ -755,9 +755,9 @@ static const vshCmdOptDef opts_network_update[] = {
      N_("name of file containing xml (or, if it starts with '<', the complete "
         "xml element itself) to add/modify, or to be matched for search")},
     {"parent-index", VSH_OT_INT, 0, N_("which parent object to search through")},
-    {"config", VSH_OT_BOOL, 0, N_("affect next boot")},
-    {"live", VSH_OT_BOOL, 0, N_("affect running domain")},
-    {"current", VSH_OT_BOOL, 0, N_("affect current domain")},
+    {"config", VSH_OT_BOOL, 0, N_("affect next network startup")},
+    {"live", VSH_OT_BOOL, 0, N_("affect running network")},
+    {"current", VSH_OT_BOOL, 0, N_("affect current state of network")},
     {NULL, 0, 0, NULL}
 };
 

tools/virsh.pod

@@ -2051,9 +2051,9 @@ the network; if a parent-index isn't provided, the "most appropriate"
 <dhcp> element), but if I<--parent-index> is given, that particular
 instance of <ip> will get the modification.
 
-If I<--live> is specified, affect a running guest.
-If I<--config> is specified, affect the next boot of a persistent guest.
-If I<--current> is specified, affect the current guest state.
+If I<--live> is specified, affect a running network.
+If I<--config> is specified, affect the next startup of a persistent network.
+If I<--current> is specified, affect the current network state.
 Both I<--live> and I<--config> flags may be given, but I<--current> is
 exclusive. Not specifying any flag is the same as specifying I<--current>.