Merge pull request #60 from dermatz/fix-typos

Fix typos in documentation files

pages/bank-integration-m1.md

@@ -19,7 +19,7 @@ In the following sections, you will find explanations for the use of each of the
 3. The module performs the matching process to Magento orders (see: The bank/order coupling page):
     1. Extract a Magento order identifier or the IBAN (in case that the Itabs_Debit module is active) from one of the fields (fixed per bank) of the bank file.
     2. Calculate the open order amount for each open Magento order in case that a part of the total sum has already been payed or a creditmemo has been created.
-    3. If the order identifier and the order amount match, the coupling is set to Certain. It is also set to Certain, if the IBAN and the amount match. If both tries faile, the module checks for the order amount and the name of the sender. If these match an existing order, the coupling is also set to Certain.
+    3. If the order identifier and the order amount match, the coupling is set to Certain. It is also set to Certain, if the IBAN and the amount match. If both tries fail, the module checks for the order amount and the name of the sender. If these match an existing order, the coupling is also set to Certain.
     4. If only the amount, the identifier or the name match, the coupling is set to Guess. All guessed bank items can be reviewed and set to Certain manually.
     5. Otherwise, the coupling has to be performed manually.
 
@@ -43,7 +43,7 @@ On the review bankdata pages, you can see the results of the imported bank files
 * The action Export selected entries allow you to export the bankdata back to a comma separated values (CSV) file. This can be useful for your own bank administration.
 * The actions Delete selected entries will remove bank entries from the Magento data-base. They can be re-added by uploading the bank data again. These options are recommended for debug/testing purposes only. Instead, we recommend to ignore unwanted bank entries.
 * On the Ignored items page, ignored data can be un-ignored (Accept). This includes data filtered out automatically by the filters (see Filter settings).
-* On the Processed items page, coupled data can be un-coupled (Decouple). This reverses the coupling process so you can select another order to asign. Please note, that the order status is not reversed, as this is impossible for several statuses according to Magento logic.
+* On the Processed items page, coupled data can be un-coupled (Decouple). This reverses the coupling process so you can select another order to assign. Please note, that the order status is not reversed, as this is impossible for several statuses according to Magento logic.
 
 ## The Bank Payments Tab
 On the bank payments tab you will have an overview of all transactions made to a single order. This gives you a perorder overview of processed bankdata.

pages/mass-update-tier-prices-m2.md

@@ -26,7 +26,7 @@ Select "Mass Update Tier Prices". Add and configure as many tier prices as neede
 
 You will now be notified, that the tier price changes are scheduled for update and added to the queue. They get processed via the cronjob, which may take a few minutes, depending on your cronjob settings. You need to make sure, that your cronjob is running correctly. You can check the status of the updates under System > Action Logs > Bulk Actions. 
 
-If you don't run cronjobs, e.g. in a local devolpment environment, see [Configuration - Running Mass Updates without Cronjob](#running-mass-updates-without-cronjob).
+If you don't run cronjobs, e.g. in a local development environment, see [Configuration - Running Mass Updates without Cronjob](#running-mass-updates-without-cronjob).
 
 ![Queue Notification]({{ "images/mass-update-tier-prices-m2/queue.jpg" }} "Queue Notification")