diff --git a/doc/sphinx/arm/ext-gss-tsig.rst b/doc/sphinx/arm/ext-gss-tsig.rst
index 112948018b..b0f952a56b 100644
--- a/doc/sphinx/arm/ext-gss-tsig.rst
+++ b/doc/sphinx/arm/ext-gss-tsig.rst
@@ -110,7 +110,7 @@ Using GSS-TSIG
 
 There is a number of steps required to enable the GSS-TSIG mechanism:
 
-1. the gss_tsig DSO has to be loaded by the D2 server
+1. the gss_tsig hook library has to be loaded by the D2 server
 2. the GSS-TSIG capable DNS servers have to be specified with their parameters
 
 An excerpt from D2 server is provided below. More examples are available in the
@@ -226,13 +226,13 @@ An excerpt from D2 server is provided below. More examples are available in the
 
 This configuration file contains a number of extra elements.
 
-First, a list of forward and/or reverse domains with related DNS
-servers identified by their IP+port tuples. If port is not specified,
-the default of 53 is assumed. This is similar to basic mode with no
+First, a list of forward and/or reverse domains with related DNS servers
+identified by their IP+port tuples is defined. If port is not
+specified, the default of 53 is assumed. This is similar to basic mode with no
 authentication or authentication done using TSIG keys, with the
 exception that static TSIG keys are not referenced by name.
 
-Second, the ``gss_tsig.so`` library has to be specified on the
+Second, the ``libdhcp_gss_tsig.so`` library has to be specified on the
 ``hooks-libraries`` list. This hook takes many parameters. The most
 important one is `servers`, which is a list of GSS-TSIG capable
 servers.  If there are several servers and they share some