and left up to the user (it is passed as a parameter to the -c command line
option). From the implementation perspective, this is slight change
from the BIND10 days, as back then a subset of the configuration was received by
- the daemon processes. Nowadays the whole configuration is pased. To take a
+ the daemon processes. Nowadays the whole configuration is passed. To take a
specific example, the following is how b10-config.db looks today:
@code
{
how you would like to be credited. The typical answers are by first and
last name, by nickname, by company name or anonymously. Typically we
will add a note to the \c ChangeLog and also set you as the author of
-the commit applying the patch. If the contributted feature is big or
+the commit applying the patch. If the contributed feature is big or
critical for whatever reason, it may also be mentioned in release notes.
@section contributorGuideExtra Extra steps
* - @subpage dhcpv6Other
* - @subpage d2
* - @subpage d2CPL
- * - @subpage d2ProcesDerivation
+ * - @subpage d2ProcessDerivation
* - @subpage d2ConfigMgt
* - @subpage d2NCRReceipt
* - @subpage d2DDNSUpdateExecution
@image html cpl_signal_sequence.svg "CPL Signal Handling Sequence"
-@section d2ProcesDerivation D2's CPL Derivations
+@section d2ProcessDerivation D2's CPL Derivations
D2's core application classes are DDNS-specific derivations of the CPL as show
in the diagram below: