diff --git a/getting-started.md b/getting-started.md
index cd4390c..7ec8166 100644
--- a/getting-started.md
+++ b/getting-started.md
@@ -10,7 +10,7 @@ This is the AID generated by the Signify Client from the user's passcode.  All S
 the same manner to enable portability between clients.  To do this, the following procedure is used.
 
 1. Prepend the 128 bit random salt derivation code ('0A') plus the blank qualified base 64 character ('A') to the provided 21 character passcode
-2. Stretch the passcode derivation using Argon2 to generate an Ed25519 private key from the provided "tier" and paths of `signify:controller00` and `signify:controller01` for the signing key and rotation key respectively.
+2. Stretch the passcode derivation using Argon2 to generate an Ed25519 private key from the provided "tier" and paths of `signify:controller00` and `signify:controller10` for the signing key and rotation key respectively.
 3. Use the qualified base64 of the signing public key and the qualified base64 of the Blake3 digest of the rotation public key in the inception event.
 
 Using this Python code with the SignifyPy client:
diff --git a/protocol.md b/protocol.md
index bf458e2..6c0c976 100644
--- a/protocol.md
+++ b/protocol.md
@@ -17,7 +17,7 @@ To initiate a connection between a Signify Client and a KERIA agent, the two sid
 The Signify Client generates the client AID as a transferable AID with a single signing key and single rotation key and provides the signed inception event out-of-bands to the KERIA service through the Boot interface. The HTTP request must be signed by the client AID using Signify Request Authentication described below.  The algorithm for generating the signing and rotation key pairs for Client AID is as follows:
 
 1. Prepend the 128 bit random salt derivation code ('0A') plus the blank qualified base 64 character ('A') to the provided 21 character passcode
-2. Stretch the passcode derivation using Argon2 to generate an Ed25519 private key from the provided "tier" and paths of `signify:controller00` and `signify:controller01` for the signing key and rotation key respectively.
+2. Stretch the passcode derivation using Argon2 to generate an Ed25519 private key from the provided "tier" and paths of `signify:controller00` and `signify:controller10` for the signing key and rotation key respectively.
 3. Use the qualified base64 of the signing public key and the qualified base64 of the Blake3 digest of the rotation public key in the inception event.
 
 The follow is an example of a Client AID generated by the SignifyPy (Python implementation) Signify Client with a passcode of `0123456789abcdefghijk`
@@ -283,4 +283,4 @@ Document `Signify-Resource` and `Signify-Timestamp` headers here.
 Document the `Signagture-Input` header here with link to https://httpwg.org/http-extensions/draft-ietf-httpbis-message-signatures.html
 
 ### Signature Header
-Docuemnt the signing method and `Signature` header.
\ No newline at end of file
+Docuemnt the signing method and `Signature` header.