Update README.md

README.md

@@ -32,7 +32,7 @@ Use launch option `c` (below) as the quickest way to get started with Boomerang.
 There are three separate options for launching Boomerang. When selecting an option (a, b, or c), you must leave the parameters for the other options blank.
 
 1. **a - Event Document Name Contains** (use with Outbound EIBs) - This is the direct replacement for the legacy `WebServiceRequester` integration. The parameter may be left blank when being used with an EIB; the integration will pick up the deliverable document from the EIB output.  If there are multiple deliverable documents, use this parameter to match the name of the desired deliverable document.
-2. **a - Custom Transformation** (optional) - If the event document has not been transformed, the xslt attachment in this parameter can be used to convert the XML into an xslt request.  This parameter is useful for boomerang chains. Generate a boomerang chain using an EIB. For a boomerang chain, do not use an XSLT file in the EIB.  Select 'None' for the transformation.  Create multiple integration steps in the EIB business process and attach different XSLT documents in this parameter to generate different transformations.  Boomerang chains are useful when generating different requests using the same report.  For example, it is possible to create new supervisory orgs in one integration step, and in the next integration step, assign the manager roles -- all from the same report input.
+2. **a - Custom Transformation** (optional) - If the report input has not been transformed in the EIB, the xslt attachment in this parameter can be used to convert the XML into a SOAP request.  This parameter is useful for boomerang chains. To create a boomerang chain, select 'None' for the transformation in the EIB.  Create multiple integration steps in the EIB business process and attach different XSLT documents in this parameter to generate different transformations.  Boomerang chains are useful when generating different requests using the same report input.  For example, it is possible to create new supervisory orgs in one integration step, and in the next integration step, assign the manager roles.  The trick is to use different xslt documents for each boomernag step, which can be done with this parameter.
 3. **b - Input Document** (use with a document that has already been transformed to a request) - A fully formed SOAP request document can be attached at runtime. For this option, the boomerang integration can be run in standalone mode and does not need to be connected to an EIB.
 4. **c - Custom Report** and **c - Custom Transformation** (no need for an EIB with this option) - This option allows you to run the Boomerang as a standalone integration. An EIB is not needed because Boomerang will extract your report data and perform the tranformation. Select a Workday report, then attach the XSLT document to be used to transform the report output. Boomerang does not support reports with prompts at this time.
 5. **Validate Only** - When this box is checked, the integration will run, but the SOAP API call to Workday will not be performed.