Fix spelling errors

.github/codespell_ignore_words.txt

@@ -1,3 +1,4 @@
 Feitian
 GOST
 signatur
+lokale

DNIe-(OpenDNIe).md

@@ -225,5 +225,5 @@ Current implementation of DNIe OpenSC driver consists in:
 * `pkcs15-dnie.c` emulator layer,
 * `cwa14890.c` card-independent implementation for CWA14890 standard for Secure Messaging,
 * `cwa-dnie.c` DNIe Data provider for cwa14890.c, that provides (local) keys and certificates required to complain with cwa14890 SM protocol,
-* a wrap funcion for sc_transmit_apdu() method, that catches al apdu requests, and translates into SM format when required,
+* a wrap function for sc_transmit_apdu() method, that catches al apdu requests, and translates into SM format when required,
 * several glue patches.

Feitian-PKI-card.md

@@ -2,7 +2,7 @@
 
 [Feitian](http://www.ftsafe.com/) offers the "ePass PKI token", also called Feitian FTCOS/PK-01C token.
 
-The Feitian PKI card is a cryptographic smartcard, which complies wih PKCS#15 and ISO 7816 standards and can be used used for:
+The Feitian PKI card is a cryptographic smartcard, which complies which PKCS#15 and ISO 7816 standards and can be used used for:
 authentication, electronic signature, email encryption, single logon, VPN, SSL and disc encryption.
 
 The cards comes blank in PVC, so that it can be printed using retransfer printers or offset.

German-ID-Cards.md

@@ -24,7 +24,7 @@ As of May 2011 you may get signature cards from the following Trust centers in G
 
 ## TeleSec, NetKey cards
 
-TeleSec GmbH is the manufacturer of cards and they offer [TCOS](TCOS-based-preformatted-cards) based signature cards, i.e. NetKey E4 cards. Until the end of 2007 theses card were TCOS2 based with a maximal key length of 1024 bit. Since October 2007 TeleSec offers 2048 bit signature cards which are TCOS3 based.
+TeleSec GmbH is the manufacturer of cards and they offer [TCOS](TCOS-based-preformatted-cards) based signature cards, i.e. NetKey E4 cards. Until the end of 2007 these card were TCOS2 based with a maximal key length of 1024 bit. Since October 2007 TeleSec offers 2048 bit signature cards which are TCOS3 based.
 
 TCOS2 cards work well with OpenSC 0.10.0 or later. There was a problem in 0.12.0 and 0.12.1 which as fixed in 0.12.2 (ticket #256). TCOS3 support was added in December 2007 and is included in OpenSC 0.11.5. Unfortunately the 2048 bit NetKey card contains one key (the one that conforms to the German signature law) that can be used only over a secure channel. So if you want to use this particular key with OpenSC you must wait until OpenSC supports Secure Messaging.
 

Home.md

@@ -48,8 +48,8 @@ OpenSC effort consists of various sub-projects that can be used independently as
 
 * [libp11](https://github.com/OpenSC/libp11) is a wrapper library for PKCS#11 modules with OpenSSL interface,
 * [pkcs11-helper](https://github.com/OpenSC/pkcs11-helper) is a wrapper library for PKCS#11 modules with extended callback mechanisms for user and token interaction,
-* [PAM-PKCS#11](https://github.com/OpenSC/pam_pkcs11/wiki) is a feature rich plugable authentication module (PAM) for authentication via PKCS#11 modules, which includes various tools to controls the login process,
-* [pam_p11](https://github.com/OpenSC/pam_p11) is a simple plugable authentication module (PAM) for authentication via PKCS#11 modules,
+* [PAM-PKCS#11](https://github.com/OpenSC/pam_pkcs11/wiki) is a feature rich pluggable authentication module (PAM) for authentication via PKCS#11 modules, which includes various tools to controls the login process,
+* [pam_p11](https://github.com/OpenSC/pam_p11) is a simple pluggable authentication module (PAM) for authentication via PKCS#11 modules,
 * [OpenCT](https://github.com/OpenSC/openct/wiki) implements a reader driver interface for various non-standard readers on Linux,
 * [OpenSC-Java](https://github.com/CardContact/opensc-java) is a Java PKCS#11 wrapper and JCE Provider,
 * [OpenSC.tokend](https://github.com/OpenSC/OpenSC.tokend) is the open source tokend implementation from OpenSC.

Mailing-lists.md

@@ -22,4 +22,4 @@ reviewed it. This is an emergency procedure only, subscription is assumed.
 
 ## Bug reports
 
-Please file bug reports using the [Issues](https://github.com/OpenSC/OpenSC/issues) link (after reading about [ReportingBugs](How-to-write-a-good-bug-report). [Security releated issues](https://github.com/OpenSC/OpenSC/security/advisories/new) can be filed without public visibility.
+Please file bug reports using the [Issues](https://github.com/OpenSC/OpenSC/issues) link (after reading about [ReportingBugs](How-to-write-a-good-bug-report). [Security related issues](https://github.com/OpenSC/OpenSC/security/advisories/new) can be filed without public visibility.

OpenSC-Release-Howto.md

@@ -79,7 +79,7 @@ Optionally, discuss changes to _NEWS_ by opening a [new issue](https://github.co
     * Select appropriate tag (when pushed before) or create new one in GitHub (for lightweight tags only)
       * For final releases, select the existing tag, e.g. _0.20.0_; for release candidates choose a new tag, e.g. _0.20.0-rc1_
     * Upload the build artifacts to the new release
-      * release tarball, OSX installer, 2 variants (default, light) of Windows intaller for both 64b and 32b + separate debug archives
+      * release tarball, OSX installer, 2 variants (default, light) of Windows installer for both 64b and 32b + separate debug archives
       * For final releases, download signed Windows installers from Signpath.io instead of unsigned installers from AppVeyor (i.e. Nightly builds):
 
         1. Navigate to [Signpath's outstanding Signing Requests](https://app.signpath.io/Web/8d2463fe-39bd-4a41-bb72-f008b4b1fe17/SigningRequests)

OpenSC-Services.md

@@ -24,7 +24,7 @@ The mailing lists are hosted at the OpenSC project at SourceForge: [http://sourc
 
 * [opensc-announce](https://lists.sourceforge.net/lists/listinfo/opensc-announce): announcements of new releases, bugfixes and security warnings. Low volume.
 * [opensc-commits](https://lists.sourceforge.net/lists/listinfo/opensc-commits): commit notifications
-* [opensc-devel](https://lists.sourceforge.net/lists/listinfo/opensc-devel): discussion of developement of OpenSC and related projects
+* [opensc-devel](https://lists.sourceforge.net/lists/listinfo/opensc-devel): discussion of development of OpenSC and related projects
 
 **You have to subscribe to the new lists yourself.**
 

OpenSC-security-advisories.md

@@ -17,4 +17,4 @@ Software often contains bugs, so does OpenSC. Be aware of the following security
 * 27.08.2008 security advisory coded as [CVE-2008-3972](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-3972)
 * 31.07.2008 security advisory coded as [CVE-2008-2235](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2235)
 
-If you have other [security releated issues](https://github.com/OpenSC/OpenSC/security/advisories/new) to report, they can be filed without public visibility.
+If you have other [security related issues](https://github.com/OpenSC/OpenSC/security/advisories/new) to report, they can be filed without public visibility.