From 5f83a5500a0b2816ec48055e38ac003a06445079 Mon Sep 17 00:00:00 2001 From: Steven Allen Date: Fri, 28 Dec 2018 12:29:05 +0000 Subject: [PATCH] chore: apply suggestions from code review Co-Authored-By: vasco-santos --- naming/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/naming/README.md b/naming/README.md index 00422e2f2..4740cfd00 100644 --- a/naming/README.md +++ b/naming/README.md @@ -40,7 +40,7 @@ IPNS is based on [SFS](http://en.wikipedia.org/wiki/Self-certifying_File_System) # IPNS Record -An IPNS record is a data structure composed by: +An IPNS record is a data structure containing the following fields: - 1. **Value** (bytes) - It can be a path to another IPNS record, a `dnslink` path (`/ipns/example.com`) or an IPFS path (`/ipfs/Qm...`) @@ -48,8 +48,8 @@ An IPNS record is a data structure composed by: - Expiration date of the record using [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) with nanoseconds precision. - Note: Currently, the expiration date is the only available type of validity. - 3. **Validity Type** (uint64) - - Allows us to define if the record is valid under certain conditions - - Only supporting expiration date with `validityType = 0` for now + - Allows us to define the conditions under which the record is valid. + - Only supports expiration date with `validityType = 0` for now. - 4. **Signature** (bytes) - Concatenate value, validity field and validity type - Sign the concatenation result with the provided private key