Editing the documents #14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng to the same md file. Im not sure if there is a file missing by mistake or if I should create a new file
…app is not working
…very minor grammar errors and addign references to JWT (JSON Web Token)
Yes, currently they refer to the sam MD file, maybe later we can have a brief introduction about the Litentry registrar.
We are not focusing on this project anymore. The playground is offline. The datServer.md is missing, I will delete the API of the data server
We are not supporting those Dapps now. In the further, we will remove this article from the Litentry document.
There are several registrars in Kusama. The index is used to present the registrar on the chain. For instance, the index of web3 registrar is 0. You can set the fee when you submit the identity judgment request.
update url link
|
Updated the Litentry Registrar section with Mel changes and my changes. |
update Element room URL link
We service only for the Kusama at the moment.
update the explain of `Decentralization of Identity Data Allocating`
update some comments
update some explanation to make it explicitly
add comments in the file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have fixed grammar errors where I could and areas that I did not understand have been marked with a tag so that they will be highlighted and I have added comments to this using the ** so that my comments within the will be italicised. These docs are not in a final state and as such I originally created a branch for them. The idea was that we could answer these questions and get everything done prior to merging into the main branch. I am not entirely sure what your workflow is with git. My experience with version control was from before Git using svn and cvs before that. I have just reentered the tech field after a very long sabbatical (git was just popping up its head when I left) and have therefore only being using git for my personal projects and not for collaborating across bigger teams.