Clarity needed while setting identities for authenticated state and marking them primary

Issue in ./help/tutorial-web-sdk/create-identities.md

Hi Team,

I was reading through document: **https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/tags-configuration/create-identities** that explains the process of setting identities for authenticated state and tracking web event data into ExpereinceEvent schema.

Its is mentioned that
"Adobe recommends sending identities that represent a person, such as **Luma CRM Id, as the primary identity**.
**If the identity map contains the person identifier (for example, Luma CRM Id), then the person identifier becomes the primary identity. Otherwise, ECID becomes the primary identity**."

There is a similar tutorial documentation: **https://experienceleague.adobe.com/en/docs/platform-learn/getting-started-for-data-architects-and-data-engineers/ingest-streaming-data#add-the-crm-id-to-the-identity-map-data-element**, that clearly says to leave the primary checkbox unchecked with a reason stating that:-

"**Leave Primary unchecked.** Since the CRM Id is not present for most visitors to the Luma website, **you definitely do not want to override the ECID as the primary identifier**. It would be a rare use case to use anything other than the ECID as the primary identifier. Usually I don’t mention the default settings in these instructions, but I am calling this one out to help you avoid headaches later on in your own implementation."

Can you please clarify following:
1. For any given schema there can be only one primary identifier. Particularly for ExperienceEvent schema, it make sense to keep ECID as primary schema and CRM id as secondary identity, which may be set post authentication. Why are you recomending to make both ECID and CRMID as primary contextually, will it not cause issues?
2. Which version of explanation is correct: your document or **https://experienceleague.adobe.com/en/docs/platform-learn/getting-started-for-data-architects-and-data-engineers/ingest-streaming-data#add-the-crm-id-to-the-identity-map-data-element** that says to leave primary checkbox unchecked?

Start with help/tutorial-web-sdk/create-identities.md and compare its primary-identity guidance with the linked ingest-streaming-data section on adding the CRM ID to the identity map. Verify the intended ECID and CRM ID behavior with the documented ExperienceEvent identity rules, then update the affected explanations so they are consistent and explicitly answer both questions.

Written by the indexing model from the issue text.