Update src/personas/faqs.md

Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>

Author: pwseg

src/personas/faqs.md

@@ -72,7 +72,7 @@ The trait and audience will automatically update going forward as historical eve
 Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`, and so on). The simplified algorithm works as follows:
 
 1. Segment first searches the Identity Graph for incoming external IDs.
-2. If Segment find no matching profile(s), it creates one.
+2. If Segment finds no matching profile(s), it creates one.
 3. If Segment finds one profile, it merges the incoming event with that profile. (This means that Segment adds the external IDs on the incoming message and resolves the event to the profile.)
 4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile.
 5. Segment then applies [Personas default profile limits](/docs/personas/product-limits/#identity) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.