Volunteer-Registration-and-Administration.md

@@ -7,7 +7,7 @@
 3. [Background Checks](#background-checks)
 4. [inLeague System Access and Eligibility Rules](#inleague-system-access-and-eligibliity-rules)
 5. [Youth Volunteers](#youth-volunteers)
-6. [Merging Duplicate Volunteers](#Merging Duplicate Volunteers)
+6. [Merging Duplicate Volunteers](https://gitlab.inleague.io/content/guides-and-documents/-/wikis/Volunteer-Registration-and-Administration#merging-duplicate-volunteers)
 
 ## Introduction to Volunteer Membership
 
@@ -105,11 +105,11 @@ Youth referees who turn 18 during the season will need to return to inLeague and
 inLeague presents a number of obstacles to the creation of duplicate users (and duplicate players) but ultimately does not forbid the existence of two people with the same name and date of birth. Duplicate accounts were more of an issue in the past during large data migrations from historical AYSO providers; these days, they are rare, but they do occur in two flavors with different resolution mechanisms.
 
 1. **inLeague Duplicates** in which both accounts have the same AYSO ID (or no AYSO ID) and need to be merged on the inLeague side
-2. **AYSO Duplicates** in which two distinct volunteer records with different AYSO IDs exist; or, the discovery of a user with a name like **Franklin_Dup-merged** 
+2. **AYSO Duplicates** in which two distinct volunteer records with different AYSO IDs exist; or, the discovery of a user with a name like **Franklin_Dup-merged**
 
 ### inLeague Duplicates
 
-Designate one record as the 'good' record. This is typically the record that is already in the correct family, or the record that has coaching or referee history. If neither record has any associated family or volunteer history, select the one with the most accurate or up-to-date information. 
+Designate one record as the 'good' record. This is typically the record that is already in the correct family, or the record that has coaching or referee history. If neither record has any associated family or volunteer history, select the one with the most accurate or up-to-date information.
 
 Select **User Search** and navigate to the user record of the "good" user. Select **Merge User** and then enter the name or email address matching the "bad" record (the one to be merged into the good one). The user merge utility will show the record you want to keep and then the record to be merged; confirm your selection, and all the volunteer history and financial transactions associated with the 'bad' record will be transferred to the 'good' one. The "bad" record will then be deleted.
 
@@ -119,7 +119,7 @@ The **-merged** suffix on an inLeague user record occurs when the AYSO Associati
 
 The solution is to temporarily detach the inLeague user record from Affinity; correct their name and date of birth; and then re-attach the record to Affinity. This requires **registrar** or **system administrator** permissions.
 
-1. In the user editor, select the **Reset Assoc. Data** button next to the user's AYSO ID: 
+1. In the user editor, select the **Reset Assoc. Data** button next to the user's AYSO ID:
 
    ![image.png](uploads/0f2124cfb306ea6b4d5658547aca53a6/image.png)
 2. A warning popup will appear indicating that this function is intended only to resolve duplicates. Select **I understand: Reset this record**.