-by removing the implicitely added prefix <em>lib</em>. This step is not mandatory
-at all because afb-daemon doesn’t check names of files when loading it.
-The only convention that use afb-daemon is that extension is <strong>.so</strong>
-but this convention is used only when afb-daemon discovers plugin
-from a directory hierarchy.</p></li>
-<li><p>It applies a version script at link to only export the conventional name
-of the entry point: <strong>pluginAfbV1Register</strong>. See below. By default, the linker
-that creates the shared object exports all the public symbols (C functions that
-are not <strong>static</strong>).</p></li>
+by removing the implicitly added prefix <em>lib</em>. This step is not mandatory
+because afb-daemon doesn’t check names of files at load time.
+The only filename convention used by afb-daemon relates to <strong>.so</strong> termination.
+*.so pattern is used when afb-daemon automatically discovers plugin from a directory hierarchy.</p></li>
+<li><p>It applies a version script at link time to only export the reserved name
+<strong>pluginAfbV1Register</strong> for registration entry point. By default, when building
+a shared library linker exports all the public symbols (C functions that are not <strong>static</strong>).</p></li>