[3857] warn about the loose terminology (aka DSO vs shared library)

src/lib/hooks/hooks_component_developer.dox

-// Copyright (C) 2013  Internet Systems Consortium, Inc. ("ISC")
+// Copyright (C) 2013, 2015  Internet Systems Consortium, Inc. ("ISC")
 //
 // Permission to use, copy, modify, and/or distribute this software for any
 // purpose with or without fee is hereby granted, provided that the above
@@ -20,7 +20,9 @@
 The hooks framework is a Kea system that simplifies the way that
 users can write code to modify the behavior of Kea.  Instead of
 altering the Kea source code, they write functions that are compiled
-and linked into a shared library.  The library is specified in the Kea
+and linked into a dynamic shared object called here a shared library
+(even the concepts are different they are implemented in the same
+way with a common naming).  The library is specified in the Kea
 configuration and at run time Kea dynamically loads the library
 into its address space.  At various points in the processing, the component
 "calls out" to functions in the library, passing to them the data is it

src/lib/hooks/hooks_user.dox

-// Copyright (C) 2013-2014  Internet Systems Consortium, Inc. ("ISC")
+// Copyright (C) 2013-2015  Internet Systems Consortium, Inc. ("ISC")
 //
 // Permission to use, copy, modify, and/or distribute this software for any
 // purpose with or without fee is hereby granted, provided that the above
@@ -52,10 +52,11 @@ Kea uses the modified data in the remainder of its processing.
 
 In order to minimize the interaction between Kea and the user
 code, the latter is built independently of Kea in the form of
-a shared library (or libraries).  These are made known to Kea
-through its configuration mechanism, and Kea loads the library at
-run time. Libraries can be unloaded and reloaded as needed while Kea
-is running.
+a dynamic shared object (or objects). Even they are conceptually
+different dynamic shared objects are called here shared libraries.
+These are made known to Kea through its configuration mechanism, and
+Kea loads the library at run time. Libraries can be unloaded and
+reloaded as needed while Kea is running.
 
 Use of a defined API and the Kea configuration mechanism means that
 as new versions of Kea are released, there is no need to modify