16441: Typo fix, used 'zzzzz' in examples.

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz@curii.com>

diff --git a/doc/admin/link-accounts.html.textile.liquid b/doc/admin/link-accounts.html.textile.liquid
index 1b0c42531576c573941671a5ba0576d5e0398828..19fbafd025ceaf565d497c3d79ad49ffc104713b 100644 (file)
--- a/doc/admin/link-accounts.html.textile.liquid
+++ b/doc/admin/link-accounts.html.textile.liquid
@@ -19,19 +19,19 @@ Account linking works by recording in the database that a log in to the "old" ac
 
 The "old" account is the Arvados account that will be redirected.
 
-The "new" account is the user that the "old" account is redirected to.  As part of account linking any Arvados records owned the "old" account is also transferred to the "new" account.
+The "new" account is the user that the "old" account is redirected to.  As part of account linking any Arvados records owned by the "old" account is also transferred to the "new" account.
 
 Counter-intuitively, if you do not want the account uuid of the user to change, the "new" account should be the pre-existing account, and the "old" account should be the redundant second account that was more recently created.  This means "old" and "new" are opposite from their expected chronological meaning.  In this case, the use of "old" and "new" reflect the direction of transfer of ownership -- the login was associated with the "old" user account, but will be associated with the "new" user account.
 
-In the example below, @x1u39-tpzed-3kz0nwtjehhl0u4@ is the "old" account (the pre-existing account we want to keep) and @x1u39-tpzed-fr97h9t4m5jffxs@ is the "new" account (the redundant account we want to merge into the existing account).
+In the example below, @zzzzz-tpzed-3kz0nwtjehhl0u4@ is the "old" account (the pre-existing account we want to keep) and @zzzzz-tpzed-fr97h9t4m5jffxs@ is the "new" account (the redundant account we want to merge into the existing account).
 
 h3. Step 2: Create a project
 
 Create a project owned by the "new" account that will hold any data owned by the "old" account.
 
 <pre>
-$ arv --format=uuid group create --group '{"group_class": "project", "name": "Data from old user", "owner_uuid": "x1u39-tpzed-fr97h9t4m5jffxs"}'
-x1u39-j7d0g-mczqiguhil13083
+$ arv --format=uuid group create --group '{"group_class": "project", "name": "Data from old user", "owner_uuid": "zzzzz-tpzed-fr97h9t4m5jffxs"}'
+zzzzz-j7d0g-mczqiguhil13083
 </pre>
 
 h3. Step 3: Merge "old" user to "new" user
@@ -40,9 +40,9 @@ The @user merge@ method redirects login and reassigns data from the "old" accoun
 
 <pre>
 $ arv user merge  --redirect-to-new-user \
-  --old-user-uuid=x1u39-tpzed-3kz0nwtjehhl0u4 \
-  --new-user-uuid=x1u39-tpzed-fr97h9t4m5jffxs \
-  --new-owner-uuid=x1u39-j7d0g-mczqiguhil13083 \
+  --old-user-uuid=zzzzz-tpzed-3kz0nwtjehhl0u4 \
+  --new-user-uuid=zzzzz-tpzed-fr97h9t4m5jffxs \
+  --new-owner-uuid=zzzzz-j7d0g-mczqiguhil13083 \
 </pre>
 
 Note that authorization credentials (API tokens, ssh keys) are also transferred to the "new" account, so credentials used to access the "old" account work with the "new" account.