From 490a0bac6af1f0ddf15b936c88ee800b1530bdbe Mon Sep 17 00:00:00 2001 From: jinjingroad Date: Wed, 5 Jun 2024 15:25:24 +0800 Subject: [PATCH] chore: fix some comments Signed-off-by: jinjingroad --- app/app.go | 2 +- images/regen-sandbox/bootstrap.sh | 2 +- x/data/spec/01_concepts.md | 2 +- x/data/spec/07_client.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/app/app.go b/app/app.go index d3def5fee1..a20ed50271 100644 --- a/app/app.go +++ b/app/app.go @@ -143,7 +143,7 @@ var ( // DefaultNodeHome default home directories for regen DefaultNodeHome = os.ExpandEnv("$HOME/.regen") - // ModuleBasics is in charge of setting up basic, non-dependant module + // ModuleBasics is in charge of setting up basic, non-dependent module // elements, such as codec registration and genesis verification. ModuleBasics = module.NewBasicManager( auth.AppModuleBasic{}, diff --git a/images/regen-sandbox/bootstrap.sh b/images/regen-sandbox/bootstrap.sh index cfefe8bab6..0081e06585 100755 --- a/images/regen-sandbox/bootstrap.sh +++ b/images/regen-sandbox/bootstrap.sh @@ -121,6 +121,6 @@ do done # wait again on the regen node process so it can be terminated with ctrl+C -echo "Node started & state inialized!" +echo "Node started & state initialized!" wait $REGEN_PID diff --git a/x/data/spec/01_concepts.md b/x/data/spec/01_concepts.md index 664ba7040f..2d9a0b283d 100644 --- a/x/data/spec/01_concepts.md +++ b/x/data/spec/01_concepts.md @@ -46,7 +46,7 @@ If the data is altered in any way, both the content hash and the resulting ident ### Attest -Attesting to data is a way to validate a piece of data. Attesting to data is comparable to signing a legal document and implies the contents of the data are accepted to be true by the attestor to the best of their knowledge. When data is attested to, an attestor entry is stored on chain including the identifier ([IRI](#iri)) of the anchored data, the address of the attestor, and a timestamp representing the time at which the data was attested to. The attestor entry can be thought of as a digital signature (separate from but dependant upon a transaction signature). +Attesting to data is a way to validate a piece of data. Attesting to data is comparable to signing a legal document and implies the contents of the data are accepted to be true by the attestor to the best of their knowledge. When data is attested to, an attestor entry is stored on chain including the identifier ([IRI](#iri)) of the anchored data, the address of the attestor, and a timestamp representing the time at which the data was attested to. The attestor entry can be thought of as a digital signature (separate from but dependent upon a transaction signature). Attesting to data is only supported with data that uses deterministic, canonical encoding (i.e. the attestor must provide a [graph content hash](#graph-content-hash)). If the data has not already been anchored, attesting to data will also anchor the data. If the same attestor attempts to attest to the same piece of data, the attestation will be ignored (i.e. the previous entry will not be updated and a new entry will not be added). Any number of different attestors can attest to the same piece of data. diff --git a/x/data/spec/07_client.md b/x/data/spec/07_client.md index 9d99f1b7fc..7eafbfcac3 100644 --- a/x/data/spec/07_client.md +++ b/x/data/spec/07_client.md @@ -565,7 +565,7 @@ Example Output: ### resolver -The `resovler` endpoint allows users to query a resolver by its unique identifier. +The `resolver` endpoint allows users to query a resolver by its unique identifier. ```bash /regen/data/v1/resolver/{id} @@ -603,7 +603,7 @@ of the data. Example: ```bash -curl locahost:1317/regen/data/v1/resolvers/iri/regen:13toVgf5aZqSVSeJQv562xkkeoe3rr3bJWa29PHVKVf77VAkVMcDvVd.rdf +curl localhost:1317/regen/data/v1/resolvers/iri/regen:13toVgf5aZqSVSeJQv562xkkeoe3rr3bJWa29PHVKVf77VAkVMcDvVd.rdf ``` Example Output: