commit e0e69811d2f49683dc18e1231715e3ee23fc8f2a
parent 36bba29282a8b64f2f1715782676e5d9d999db40
Author: Özgür Kesim <oec-taler@kesim.org>
Date: Sun, 30 Jul 2023 14:56:20 +0200
-typos
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/design-documents/045-kyc-inheritance.rst b/design-documents/045-kyc-inheritance.rst
@@ -6,7 +6,7 @@ Summary
This document presents and discusses a mechanism by which a reserve A can
provide KYC attestation for another reserve B, whenever A's KYC attestation is
-the result of a proper KCY-process and not inherited itself. During the
+the result of a proper KYC-process and not inherited itself. During the
transitive attestation process, A can change the birthday for reserve B become
younger, i.e. choose a date closer to the current date than the original
birthday.
@@ -53,7 +53,7 @@ number of attestations that a (KYC'ed) reserve can provide for other reserves.
.. code:: none
- [kcy-legitimization-inheritance]
+ [kyc-legitimization-inheritance]
MAXIMUM_ATTESTATIONS = [number]
@@ -153,7 +153,7 @@ For the wallet: TODO.
Alternatives
============
-* KYC for a reserve can only be provided by a full KCY legitimization process.
+* KYC for a reserve can only be provided by a full KYC legitimization process.
Drawbacks
=========
