Native_manifests: pkcs11 paths may be relative

Undocumented support for relative paths existed for a long while, and
became an explicit first-class supported feature in
https://bugzilla.mozilla.org/show_bug.cgi?id=1759162

This fixes the documentation accordingly, to set the correct
expectations.

And prepend "PKCS 11" to "module" to emphasize that this fragment of the
table is about the manifests for the pkcs11 API, to avoid confusion in
case the reader was looking for the native messaging manifest.

files/en-us/mozilla/add-ons/webextensions/native_manifests/index.md

@@ -257,7 +257,7 @@ The PKCS #11 manifest is a file with a name that matches the name of the PKCS #1
       <td>String</td>
       <td>
         <p>Name of the PKCS #11 module.</p>
-        <p>This must match the name used in the <code>pkcs11</code> API.</p>
+        <p>This must match the name used in the {{WebExtAPIRef("pkcs11")}} API.</p>
         <p>
           On Windows, use this as the name of the registry key you create,
           which contains the location of the manifest.
@@ -274,7 +274,7 @@ The PKCS #11 manifest is a file with a name that matches the name of the PKCS #1
       <td><code>description</code></td>
       <td>String</td>
       <td>
-        <p>Description of the module.</p>
+        <p>Description of the PKCS #11 module.</p>
         <p>
           This sets the friendly name for the module in the browser's
           UI (for example, the "Security Devices" dialog in Firefox).
@@ -285,10 +285,9 @@ The PKCS #11 manifest is a file with a name that matches the name of the PKCS #1
       <td><code>path</code></td>
       <td>String</td>
       <td>
-        <p>Path to the module.</p>
+        <p>Path to the PKCS #11 module.</p>
         <p>
-          On Windows, this may be relative to the manifest itself. On MacOS and
-          Linux, it must be absolute.
+          The path to the PKCS #11 module may be absolute, or relative to the manifest itself.
         </p>
       </td>
     </tr>