CIP-0011 | Adjust preamble and structure w.r.t CIP-0001 (cardano-foundation#654)

* first draft remediation of CIP-0011

* according to CIP-0084 "Ledger era" is not capitalised

* spelled NA instead of standard N/A

* canonical inter-CIP links

* some trial and error: square brackets appear not to work outside main branch

* use relative CIP link syntax that will also work on Dev Portal

* best guess of what will work both on GitHub and Dev Portal

* aha, that's the common link syntax: imitating CIP-0001

* CIP should also cover tool stack, not just wallets

Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>

* yet another missing full stop in the Copyright section

Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>

---------

Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>

Author: rphair

CIP-0011/README.md

@@ -1,42 +1,33 @@
 ---
 CIP: 11
 Title: Staking key chain for HD wallets
-Authors: Sebastien Guillemot <sebastien@emurgo.io>, Matthias Benkort <matthias.benkort@iohk.io>
-Comments-URI: https://forum.cardano.org/t/staking-key-chain-for-hd-wallets/41857
 Status: Active
-Type: Standards
+Category: Wallets
+Authors:
+  - Sebastien Guillemot <sebastien@emurgo.io>
+  - Matthias Benkort <matthias.benkort@iohk.io>
+Implementors: N/A
+Discussions:
+  - https://github.com/cardano-foundation/CIPs/pull/33
+  - https://forum.cardano.org/t/staking-key-chain-for-hd-wallets/41857
+  - https://github.com/cardano-foundation/CIPs/pull/37
 Created: 2020-11-04
 License: CC-BY-4.0
 ---
 
 ## Abstract
 
-Starting with the Shelley hardfork, Cardano makes use of both the *UTXO model* and the *account model*. To support both transaction models from the same master key, we allocate a new chain for [CIP1852](https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/README.md)
+Starting with the Shelley hardfork, Cardano makes use of both the *UTXO model* and the *account model*. To support both transaction models from the same master key, we allocate a new chain for [CIP-1852].
 
-## Terminology
-
-### Meaning of *account*
-
-The term "account" is unfortunately an overloaded term so we clarify all its uses here
-
-#### 1) "Account" as a BIP44 derivation level
-
-BIP44 uses the term "account" as one derivation level to mean the following
-
-> This level splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.
-To differentiate this from other usage, we sometimes refer to it as an `account'` (the bip32 notation) or a BIP44 Account.
-
-#### 2) "Account" as a transaction model
-
-Blockchains like Ethereum does not use the UTXO model and instead uses the [*Account model*](https://github.com/ethereum/wiki/wiki/Design-Rationale#accounts-and-not-utxos) for transactions.
-
-## Motivation
+## Motivation: why is this CIP necessary?
 
 Generally it's best to only use a cryptographic key for a single purpose, and so it's best to make the staking key be separate from any key used for UTXO addresses.
 
 ## Specification
 
-Recall that [CIP1852](https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/README.md) specifies the following derivation path
+> **Note** The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
+
+Recall that [CIP-1852] specifies the following derivation path:
 
 ```
 m / purpose' / coin_type' / account' / chain / address_index
@@ -52,7 +43,7 @@ Wallets that use multiple staking keys are REQUIRED to use sequential indexing w
 
 *Note*: an observer looking at the blockchain will be able to tell if two staking keys belong to the same user if they are generated from the same wallet with different `address_index` values because the payment keys inside the *base addresses* will be the same.
 
-## Test vectors
+### Test vectors
 
 recovery phrase
 ```
@@ -69,6 +60,36 @@ reward address (with `network_id=1`)
 stake1uy8ykk8dzmeqxm05znz65nhr80m0k3gxnjvdngf8azh6sjc6hyh36
 ```
 
+## Rationale: how does this CIP achieve its goals?
+
+### Meaning of *account*
+
+The term "account" is unfortunately an overloaded term so we clarify all its uses here:
+
+#### 1) "Account" as a BIP44 derivation level
+
+BIP44 uses the term "account" as one derivation level to mean the following
+
+> This level splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.
+To differentiate this from other usage, we sometimes refer to it as an `account'` (the bip32 notation) or a BIP44 Account.
+
+#### 2) "Account" as a transaction model
+
+Blockchains like Ethereum does not use the UTXO model and instead uses the [*Account model*](https://github.com/ethereum/wiki/wiki/Design-Rationale#accounts-and-not-utxos) for transactions.
+
+## Path to Active
+
+### Acceptance Criteria
+
+- [x] All notable wallet and tooling providers follow this method of key derivation.
+
+### Implementation Plan
+
+- [x] This method of key derivation has been agreed as canonical and has been included in [CIP-1852].
+- [x] This method of key derivation has been supported by all wallet and tool providers beginning with the Shelley ledger era.
+
 ## Copyright
 
-This CIP is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode)
+This CIP is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+[CIP-1852]: https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/README.md