From 09ae062927c6c16aa075e57d48765db6923f1376 Mon Sep 17 00:00:00 2001 From: Elliot Lee Date: Mon, 4 Mar 2019 11:25:39 -0800 Subject: [PATCH] Update assign-a-regular-key-pair.md --- .../manage-account-settings/assign-a-regular-key-pair.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/manage-account-settings/assign-a-regular-key-pair.md b/content/tutorials/manage-account-settings/assign-a-regular-key-pair.md index 92101bde17..060e886c20 100644 --- a/content/tutorials/manage-account-settings/assign-a-regular-key-pair.md +++ b/content/tutorials/manage-account-settings/assign-a-regular-key-pair.md @@ -396,7 +396,7 @@ Note that the response contains a `hash` of the transaction, which you can use t To verify that your account has the regular key pair set correctly, submit an [AccountSet transaction][] from your account, signing it with the regular private key you assigned to your account in step 2. -As discussed in step 2, transmitting your master private key is dangerous. It is equally risky to transmit your regular private key, though the consequences of being comprised might be less severe. Therefore, we'll complete this transaction in two steps to keep transaction signing separate from transaction submission to the network. +As discussed in step 2, transmitting your master private key is dangerous. It is equally risky to transmit your regular private key. Therefore, we'll complete this transaction in two steps to keep transaction signing separate from transaction submission to the network. ### Sign Your Transaction