typos

Author: cheungaryk

modules/ROOT/pages/apm-tutorial-td.adoc

@@ -220,7 +220,7 @@ From the list, click *AS2*.
 +
 From the list, click *Send*.
 +
-The <<img-endpoint-add>> expands to enable configuraton of additional settings.
+The <<img-endpoint-add>> expands to enable configuration of additional settings.
 
 
 . Select *Default for AcmeHomeSupply*.

modules/ROOT/pages/edi-schema-language-reference.adoc

@@ -103,7 +103,7 @@ Group definitions are shown in expanded form, with key-value pairs on separate l
 * M for Mandatory
 * O for Optional
 * U for Unused
-|count |mMximum repetition count value, which may be a number or the special value `>1` meaning any number of repeats (optional, count value of 1 is used if not specified)
+|count |Maximum repetition count value, which may be a number or the special value `>1` meaning any number of repeats (optional, count value of 1 is used if not specified)
 |items |List of segments (and potentially nested groups) making up the group
 |===
 

modules/ROOT/pages/edi-tradacoms.adoc

@@ -419,7 +419,7 @@ Defaults are specified in these fields:
 
 You can set the following options if needed:
 
-* *Fail when value length outside allowed range* - Fail when the receive value lengthis outside the allowed range. If `true`, a transmission with this error is rejected; if `false`, the value is used anyway and the transmission is not rejected. In either case, the error is logged and reported in the returned error list.
+* *Fail when value length outside allowed range* - Fail when the receive value length is outside the allowed range. If `true`, a transmission with this error is rejected; if `false`, the value is used anyway and the transmission is not rejected. In either case, the error is logged and reported in the returned error list.
 * *Fail when unknown segment in transmission* - Fail when an unknown segment is present in a transmission. If `true`, a transmission with this error is rejected; if `false`, the segment is ignored and the transmission is not rejected. In either case the error is logged and reported in the returned error list.
 * *Fail when unused segment included in transmission* - Fail when a segment marked as Unused is included in a transmission. If `true`, a transmission with this error is rejected; if `false`, the transmission is not rejected and the unused segment is ignored. In either case the error is logged and reported in the returned error list.
 * *Fail when segment out of order in transmission* - Fail when a segment is out of order in a transmission. If `true`, a transmission with this error is rejected; if `false` and the segment can be reordered the transmission is not rejected. In either case the error is logged and reported in the returned error list.

modules/ROOT/pages/lookup-tables.adoc

@@ -72,7 +72,7 @@ The *Add Lookup Table Field* box appears; enter a name for a field you want to a
 +
 The *Add Lookup Table Field* box closes.
 +
-The <<img-lookup-table>> displays the key or keys you have addded.
+The <<img-lookup-table>> displays the key or keys you have added.
 The new field name appears in the *Name* column of the table.
 +
 To add another field, repeat this step.
@@ -96,7 +96,7 @@ Any fields added for this table appear.
 +
 The *Add Lookup Table Key* box closes.
 +
-The <<img-lookup-table>> displays the key or keys you have addded.
+The <<img-lookup-table>> displays the key or keys you have added.
 
 == Working with Lookup Table Data
 

modules/ROOT/pages/working-with-environments.adoc

@@ -42,9 +42,9 @@ Importing partners involves a series of steps, starting from the partners list s
 
 . Find the "New Partner" on the top right. Click on the little arrow pointing down next to the button and select "Import". This will pop up the "Import" window. You can hit "Dismiss" to cancel the process.
 . Select the "target environment", this is the environment into which the partners will be imported. Hit "Next".
-. Select the file with the partners (which was previoulsy exported) by hitting "Choose File" and browsing through your file system. At this point you can hit "Back" to change the selected target environment, if needed.
-. Select whether the partners being imported will keep their identifiers when matching existing or previoulsy imported partners on the target environment.
-. Select whether the partners being imported will keep their AS2 certificates or use the certificates from the matching existing, or previoulsy imported partners on the target environment. Hit import to start the process.
+. Select the file with the partners (which was previously exported) by hitting "Choose File" and browsing through your file system. At this point you can hit "Back" to change the selected target environment, if needed.
+. Select whether the partners being imported will keep their identifiers when matching existing or previously imported partners on the target environment.
+. Select whether the partners being imported will keep their AS2 certificates or use the certificates from the matching existing, or previously imported partners on the target environment. Hit import to start the process.
 
 == Promoting Partners Into A Specific Environment
 
@@ -54,14 +54,14 @@ Only users with the appropriate role or permissions will be able to promote part
 . Select one or more partners to promote from the list.
 . Hit the "Promote" button. This will pop up the "Promote" window listing the partners to be promoted. You can hit "Dismiss" to cancel the process.
 . Select the "target environment", this is the environment into which the partners will be promoted. Hit "Next" to go to the next step. Alternatively, you can hit "Back" to change the selected target environment, if needed.
-. Select whether the partners being promoted will keep their identifiers when matching existing or previoulsy imported partners on the target environment.
-. Select whether the partners being imported will keep their AS2 certificates or use the certificates from the matching existing, or previoulsy promoted partners on the target environment. Hit import to start the process.
+. Select whether the partners being promoted will keep their identifiers when matching existing or previously imported partners on the target environment.
+. Select whether the partners being imported will keep their AS2 certificates or use the certificates from the matching existing, or previously promoted partners on the target environment. Hit import to start the process.
 ////
 
 == Promotion Scenarios
 Promotion of partners is a more complex procedure than import.
 Suppose a partner was created on an Environment ENV_A and then promoted to ENV_B. Subsequently, the same partner can be promoted over and over again from ENV_A to ENV_B. Each time promotion happens, the values for the partner in the target environment will be updated using the values of that partner in the source environment.
-However, depending on certain conditions, not all of the values will be updated (specifically Identifiers and AS2 Certificates) or even the promotion can be rejected altogether. These conditions are grouped into specific scenarios, afecting the result of the promotion process. Following is a description of the possible scenarios and their outcomes:
+However, depending on certain conditions, not all of the values will be updated (specifically Identifiers and AS2 Certificates) or even the promotion can be rejected altogether. These conditions are grouped into specific scenarios, affecting the result of the promotion process. Following is a description of the possible scenarios and their outcomes:
 
 === Certificates and promotions
 
@@ -100,4 +100,5 @@ Please note that in this scenario, should the target environment P2 have _any_ o
 ==== Scenario 4: Conflicting Identifiers and Promotions
 * Suppose there's a partner P1 on the source environment E1. Suppose P1 has a set of identifiers (types and values) for AS2, EDI X12 and EDIFACT.
 * And suppose there is a partner P2 on some target environment E2. Suppose P2 has, for whatever reason, the exact same set of identifiers as P1 on E1
-* Promoting P1 from E1 to E2, while selecting "Keep Existing Identifiers", will try to "copy" P1 into E2. This will cause that a set of identifiers be created in E2. However, having the same identifier values more than once is illegal, so promotion will fail. The "Promotion" window will display a message informing about this situation.
+* Promoting P1 from E1 to E2, while selecting "Keep Existing Identifiers", will try to "copy" P1 into E2. This will cause that a set of identifiers be created in E2. However, having the same identifier values more than once is illegal, so promotion will fail. The "Promotion" window will display a message informing about this situation.
+////