From 0bf20f91f0fb45138021480f346ee386ec64de79 Mon Sep 17 00:00:00 2001
From: liaz-af <61788924+liaz-af@users.noreply.github.com>
Date: Wed, 15 Jan 2025 15:12:19 +0200
Subject: [PATCH] Update purchase-connector.md - fix in-app events wording

---
 docs/purchase-connector.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/purchase-connector.md b/docs/purchase-connector.md
index fa452e2..c1bb687 100644
--- a/docs/purchase-connector.md
+++ b/docs/purchase-connector.md
@@ -13,7 +13,7 @@ order: 13
 The AppsFlyer ROI360 purchase connector is used to validate and report in-app purchase and subscription revenue events. It’s part of the ROI360 in-app purchase and subscription revenue measurement solution.
 
 - Using the purchase connector requires an ROI360 subscription.
-- If you use this in-app purchase and subscription revenue measurement solution, you shouldn’t send [in-app events](https://dev.appsflyer.com/hc/docs/inappevents) with revenue or execute [`validateAndLogInAppPurchase`](https://dev.appsflyer.com/hc/docs/validate-and-log-purchase-ios), as doing so results in duplicate revenue being reported.
+- If you use this in-app purchase and subscription revenue measurement solution, you shouldn’t send [in-app purchase events](https://dev.appsflyer.com/hc/docs/inappevents) with revenue or execute [`validateAndLogInAppPurchase`](https://dev.appsflyer.com/hc/docs/validate-and-log-purchase-ios), as doing so results in duplicate revenue being reported.
 - Before implementing the purchase connector, the ROI360 in-app purchase and subscription revenue measurement needs to be integrated with Google Play and the App Store. [See instructions (steps 1 and 2)](https://support.appsflyer.com/hc/en-us/articles/7459048170769)
 
 ## Prerequisites