Fix typos

diff --git a/docs/tans.rst b/docs/tans.rst
index d3fe8360cf1bfad9bebd4f220ff8c429e01755d7..52d55d3ca5393cefaed9fc32a32c7d99e9d012f2 100644 (file)
--- a/docs/tans.rst
+++ b/docs/tans.rst
@@ -5,7 +5,7 @@ Working with TANs
 
 Many operations in FinTS will require a form of two-step authentication, called TANs. TANs are
 mostly required for operations that move money or change details of a bank account. TANs can be
-generated with a multidue of methods, including paper lists, smartcard readers, SMS messages, and
+generated with a multitude of methods, including paper lists, smartcard readers, SMS messages, and
 smartphone apps.
 
 TAN methods

diff --git a/docs/trouble.rst b/docs/trouble.rst
index 264123b211c91f0b7361ed0ee47bbfcaf78f1fc1..35a2247cc9a8467362e7ecaafecd163c21fa087c 100644 (file)
--- a/docs/trouble.rst
+++ b/docs/trouble.rst
@@ -3,7 +3,7 @@ Troubleshooting and bug reporting
 
 The FinTS specification is long and complicated and in many parts leaves things open to interpretation -- or sometimes
 implementors interpret things differently even though they're not really open to interpretation. This is valid for us,
-but also for the banks. Making the library work with many diffrent banks is hard, and often impossible without access
+but also for the banks. Making the library work with many different banks is hard, and often impossible without access
 to a test account. Therefore, we ask you for patience when reporting issues with different banks -- and you need to be
 ready that we might not be able to help you because we do not have the time or bank account required to dig deeper.
 

diff --git a/docs/upgrading_1_2.rst b/docs/upgrading_1_2.rst
index 6342a7343fe39a1b5a063a1cfa2246dff16de2a7..35741f7bf4506ff6bb4149639649c3e6a837b26c 100644 (file)
--- a/docs/upgrading_1_2.rst
+++ b/docs/upgrading_1_2.rst
@@ -15,12 +15,12 @@ important changes to know:
 
 * The ``start_sepa_debit`` method was renamed to ``sepa_debit`` and no longer takes a TAN method and TAN
   medium description as an argument. The new parameter ``pain_descriptor`` should be passed with the version of the
-  PAIN format, e.g. ``urn:iso:std:iso:20022:tech:xsd:pain.008.003.01``. Also, a new paramter ``cor1`` is optionally
+  PAIN format, e.g. ``urn:iso:std:iso:20022:tech:xsd:pain.008.003.01``. Also, a new parameter ``cor1`` is optionally
   available. → :ref:`debits`
 
 * Working with TANs has changed a lot. ``get_tan_methos`` has been renamed to ``get_tan_mechanisms`` and has a new
   return data type. The chosen TAN method is now set on a client level with ``set_tan_mechanism`` and
-  ``set_tan_medium``. You can find more informations in the chapter :ref:`tans` and a full example in the chapter
+  ``set_tan_medium``. You can find more information in the chapter :ref:`tans` and a full example in the chapter
   :ref:`transfers`.
 
 * Debug logging output now contains parsed syntax structures instead of data blobs and is much easier to read.

diff --git a/fints/hhd/flicker.py b/fints/hhd/flicker.py
index 8d3c830a5581b9c7505667fb3b3043fddac89a72..598ecd3a2b7ba23f47203072c409588698a4a22a 100644 (file)
--- a/fints/hhd/flicker.py
+++ b/fints/hhd/flicker.py
@@ -34,7 +34,7 @@ def clean(code):
         code = code[res.challenge_hhd_uc.index('@', 2) + 1:]
     code = code.replace(" ", "").strip()
     if "CHLGUC" in code and "CHLGTEXT" in code:
-        # Sometimes, HHD 1.3 codes are not transfered in the challenge field but in the free text,
+        # Sometimes, HHD 1.3 codes are not transferred in the challenge field but in the free text,
         # contained in CHLGUCXXXX<code>CHLGTEXT
         code = "0" + code[code.index("CHLGUC") + 11:code.index("CHLGTEXT")]
     return code