fix wording

Author: terence1988

src/connections/destinations/catalog/actions-linkedin-conversions/index.md

@@ -43,9 +43,9 @@ Your inputs must meet the following criteria:
   - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID`
   - `ACXIOM_ID`
   - `ORACLE_MOAT_ID`
-- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) formatted timestamp, and converts it to valid epoch timestamp value.
+- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} formatted timestamps, and converts it to a valid epoch timestamp.
 
 Any deviations from this specification might lead to failed inputs.
 
 ### Why LinkedIn still shows "no integration data" after I successfully sent the data?
-LinkdedIn won't reject events due to the lack ofcurrency and amount data, but they will not correctly recogonize the events you sent via Segment. Please ensure your payload has the data or try "Validate" for other undocumented errors.
+LinkdedIn won't reject events due to the lack of currency and amount data, but they will not correctly recogonize the events you sent via Segment. Please ensure your payload has the data or try [Event Tester](/docs/connections/test-connections/#ensuring-an-event-is-successfully-making-it-to-a-specific-destination) for other causes.