Adjust 'See Also' in multi-signing setup

Co-authored-by: Maria Shodunke <maria-robobug@users.noreply.github.com>

_code-samples/multisigning/js/set-up-multi-signing.js

@@ -84,7 +84,7 @@ if (accountInfoResp.result.signer_lists) {
     }
   }
 } else {
-  console.error(`❌ No signer lists associated with ${wallet.address}`)
+  console.error(`No signer lists associated with ${wallet.address}`)
   client.disconnect()
   process.exit(1)
 }

_code-samples/multisigning/py/set-up-multi-signing.py

@@ -22,7 +22,7 @@ algorithm = "ed25519"
 signer_addresses = []
 for i in range(3):
     signer = Wallet.create(algorithm=algorithm)
-    print(f"""Generated regular key pair:
+    print(f"""Generated key pair for signer {i + 1}:
   Address: {signer.address}
   Seed: {signer.seed}
   Algorithm: {algorithm}
@@ -46,7 +46,7 @@ print(
 )
 try:
     response = submit_and_wait(signer_list_set_tx, client, wallet)
-except err:
+except Exception as err:
     print("Submitting SignerListSet transaction failed with error", err)
     exit(1)
 
@@ -64,7 +64,7 @@ try:
     account_info_resp = client.request(
         AccountInfo(account=wallet.address, ledger_index="validated", signer_lists=True)
     )
-except err:
+except Exception as err:
     print("Error requesting account_info:", err)
     exit(1)
 if not account_info_resp.is_successful():
@@ -80,5 +80,5 @@ if account_info_resp.result.get("signer_lists"):
             se = se_wrapper["SignerEntry"]
             print(f"    Signer {se['Account']} Weight = {se['SignerWeight']}")
 else:
-    print(f"❌ No signer lists associated with {wallet.address}")
+    print(f"No signer lists associated with {wallet.address}")
     exit(1)

docs/tutorials/best-practices/key-management/set-up-multi-signing.md

@@ -70,7 +70,7 @@ To get started, import the client library and instantiate an API client. For thi
 
 ### 3. Prepare signer keys
 
-Each signer on your list needs a key pair they can use to sign transactions. As the account owner, you only need to know the addresses, not the secret keys, of each signer. (One party knowing all the secret keys might defeat the purpose of multi-signing, depending on your use case.) These addresses _can_ have funded accounts in the ledger, but they don't have to.
+Each signer on your list needs a key pair they can use to sign transactions. As the account owner, you only need to know the addresses, not the secret keys, of each signer. One party knowing all the secret keys might defeat the purpose of multi-signing, depending on your use case. These addresses _can_ have funded accounts in the ledger, but they don't have to.
 
 Each signer should securely generate and store their own key pair, as you would any time you generate keys for an XRP Ledger account.
 
@@ -134,10 +134,11 @@ At this point, you can [send a multi-signed transaction](send-a-multi-signed-tra
 - **Concepts:**
    - [Cryptographic Keys](../../../concepts/accounts/cryptographic-keys.md)
    - [Multi-Signing](../../../concepts/accounts/multi-signing.md)
+   - [Reliable Transaction Submission](../../../concepts/transactions/reliable-transaction-submission.md)
 - **Tutorials:**
    - [Send a Multi-signed Transaction](send-a-multi-signed-transaction.md)
    - [Assign a Regular Key Pair](assign-a-regular-key-pair.md)
-   - [Reliable Transaction Submission](../../../concepts/transactions/reliable-transaction-submission.md)
+   - [Disable Master Key Pair](disable-master-key-pair.md)
 - **References:**
    - [account_info method][]
    - [SignerListSet transaction][]