[#1100] Addressed comments before rebase

doc/sphinx/arm/config.rst

@@ -178,7 +178,7 @@ the older mechanisms and we hope to deprecate JSON comments one day in the
 future. To promote this way of storing comments, Kea code is able to understand
 JSON comments, but converts them to user context on the fly. The
 comments entries in user-context were converted back to JSON comments to
-keep backward compatibility, but that conversion went away in version 1.7.x.
+keep backward compatibility, but that conversion went away in version 1.7.9.
 
 The is one side effect, however. If your configuration uses the old JSON
 comment, the `config-get` command will return a slightly modified

doc/sphinx/arm/hooks.rst

@@ -2839,7 +2839,7 @@ operations, for example.
 If user context is supported in a given context, the parser translates
 "comment" entries into user context with a "comment" entry. The pretty
 print of a configuration did the opposite operation and put "comment"
-entries at the beginning of maps, but this was withdrawn in 1.7.x.
+entries at the beginning of maps, but this was withdrawn in 1.7.9.
 
 As of Kea 1.3, the structures that allow user contexts are pools of all
 types (addresses and prefixes) and subnets. Kea 1.4 extended user

src/bin/agent/tests/testdata/get_config.json

@@ -22,7 +22,7 @@
         },
         "hooks-libraries": [
             {
-                "library": "/tmp/k1100/src/bin/agent/tests/.libs/libbasic.so",
+                "library": "/opt/local/control-agent-commands.so",
                 "parameters": {
                     "param1": "foo"
                 }