11628 typos detected by mandoc style

@@ -37,12 +37,12 @@
 
      The ${METASLOT_OBJECTSTORE_SLOT} and ${METASLOT_OBJECTSTORE_TOKEN}
      environment variables are used to specify an alternate token object
      store.  A user can specify either slot-description in
      ${METASLOT_OBJECTSTORE_SLOT} or token-label in
-     ${METASLOT_OBJECTSTORE_TOKEN}, or both. Valid values for slot-description
-     and token-label are available from output of the command:
+     ${METASLOT_OBJECTSTORE_TOKEN}, or both.  Valid values for slot-
+     description and token-label are available from output of the command:
 
            # cryptoadm list -v
 
      The ${METASLOT_ENABLED} environment variable is used to specify whether
      the user wants to turn the metaslot feature on or off.  Only two values

@@ -68,11 +68,11 @@
 
      Plug-ins are added to libpkcs11 by the pkcs11conf class action script
      during execution of pkgadd(1M).  The available mechanisms are
      administered by the cryptoadm(1M) utility.
 
-     Plug-ins must have all of their library dependancies specified, including
+     Plug-ins must have all of their library dependencies specified, including
      libc(3LIB).  Libraries that have unresolved symbols, including those from
      libc(3LIB), will be rejected and a message will be sent to syslog(3C) for
      such plug-ins.
 
      Due to U.S. Export regulations, all plug-ins are required to be

@@ -144,14 +144,10 @@
      The SUNW Extension functions are MT-Safe.  The PKCS#11 Standard functions
      are MT-Safe with exceptions.  See Section 2.5.3 of PKCS#11 Cryptographic
      Token Usage Guide v2.40 and Section 5.1.5 of PKCS#11 Cryptographic Token
      Interface Base Standard v2.40
 
-STANDARD
-     The PKCS#11 Standard functions conform to PKCS#11 Cryptographic Token
-     Interface Profiles v2.40 Extended Provider.
-
 SEE ALSO
      cryptoadm(1M), pkgadd(1M), Intro(3), syslog(3C),
      SUNW_C_GetMechSession(3EXT), attributes(5), pkcs11_kernel(5),
      pkcs11_softtoken(5)
 

@@ -163,20 +159,21 @@
      http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/pkcs11-profiles-v2.40.html.
 
      PKCS#11 Cryptographic Token Interface Usage Guide v2.40,
      http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/pkcs11-ug-v2.40.html.
 
+STANDARDS
+     The PKCS#11 Standard functions conform to PKCS#11 Cryptographic Token
+     Interface Profiles v2.40 Extended Provider.
+
 NOTES
      If an application calls C_WaitForSlotEvent() without the CKF_DONT_BLOCK
      flag set, libpkcs11 must create threads internally.  If, however,
      CKF_LIBRARY_CANT_CREATE_OS_THREADS is set, C_WaitForSlotEvent() returns
      CKR_FUNCTION_FAILED.
 
-     The PKCS#11 library does not work with Netscape 4.x but does work with
-     more recent versions of Netscape and Mozilla.
-
-     Because C_Initalize() might have been called by both an application and a
-     library, it is not safe for a library or its plugins to call
+     Because C_Initialize() might have been called by both an application and
+     a library, it is not safe for a library or its plugins to call
      C_Finalize().  A library can be finished calling functions from
      libpkcs11, while an application might not.
 
-illumos                        October 19, 2016                        illumos
+illumos                         August 27, 2019                        illumos