<listitem>
<simpara>
<command>-p <replaceable>server-port</replaceable></command> -
- specifies the UDP local port on which the server will listen.
+ specifies the local UDP port on which the server will listen.
This is only useful during testing, as a DHCPv4 server
listening on ports other than the standard ones will not
be able to handle regular DHCPv4 queries.</simpara>
<listitem>
<simpara>
<command>-P <replaceable>client-port</replaceable></command> -
- specifies the UDP remote port to which the server will send
+ specifies the remote UDP port to which the server will send
all responses. This is only useful during testing, as a
DHCPv4 server sending responses to ports other than the
standard ones will not be able to handle regular DHCPv4
<para>After all the parameters have been specified, we have two contexts open:
global and Dhcp4, so we need two closing curly brackets to close them.
In a real-life configuration file there most likely would be an additional
-component defined such as Logging, so the closing brace would be followed
+component defined such as Logging, so the first closing brace would be followed
by a comma and another object definition.</para>
</section>