diff --git a/docs/introduction.md b/docs/introduction.md index 4f36d56e..fd6e6e61 100644 --- a/docs/introduction.md +++ b/docs/introduction.md @@ -54,7 +54,7 @@ A [Wallet](./wallet/wallet-overview.md) plays a crucial role in the seamless exc ## What Can you Achieve Using Privado ID? -1. **Privacy using Zero-Knowledge Proofs**: An Identity Holder, using zero-knowledge proofs, can keep thier personal data private. During the process of VC verification, it just needs to show a proof that they are the owner of a VC that matches certain criteria without letting the Verifier know of the actual VC. For example, an Identity Holder can prove to a Verifier authority that they are above 18 years of age by presenting the proof without revealing their actual age. This ensures minimum data exposure and hence confirms the safety of any sensitive data. +1. **Privacy using Zero-Knowledge Proofs**: An Identity Holder, using zero-knowledge proofs, can keep their personal data private. During the process of VC verification, it just needs to show a proof that they are the owner of a VC that matches certain criteria without letting the Verifier know of the actual VC. For example, an Identity Holder can prove to a Verifier authority that they are above 18 years of age by presenting the proof without revealing their actual age. This ensures minimum data exposure and hence confirms the safety of any sensitive data. Another aspect of privacy comes from the fact that the Issuer would not be able to track the usage of VCs by an individual once it has been issued. 2. **Off-Chain and On-Chain Verification**: Verification of proofs can be done either off-chain or on-chain via Smart Contracts. For example, developers can set up a contract that airdrops tokens only to users that meet certain criteria based on their VCs. diff --git a/docs/issuer-node/issuer-node-guide.md b/docs/issuer-node/issuer-node-guide.md index c5f92cfd..dcc93307 100644 --- a/docs/issuer-node/issuer-node-guide.md +++ b/docs/issuer-node/issuer-node-guide.md @@ -58,7 +58,7 @@ You can create your own schemas and import them to the Issuer Node. Here's how y ## Credentials -The Credentials main page shows information about all the credentials that have been granted. Each of one those credentials can be revoked by clicking on the 3 dots at the end of the row. +The Credentials main page shows information about all the credentials that have been granted. Each of those credentials can be revoked by clicking on the 3 dots at the end of the row.
diff --git a/docs/mumbai-to-amoy-migration.md b/docs/mumbai-to-amoy-migration.md index f6040ffe..589d64cc 100644 --- a/docs/mumbai-to-amoy-migration.md +++ b/docs/mumbai-to-amoy-migration.md @@ -21,7 +21,7 @@ To migrate to the Amoy testnet, developers must set up a new Issuer node configu 1. Setting up a new Issuer node using the latest configuration guidelines. - To set up a new issuer node, please refer to [this installation guide](https://github.com/0xPolygonID/issuer-node/tree/develop). It includes the latest configuration for the Amoy testnet. - - An Issuer will need to create a new identity for Amoy, through the core API specifying the proper "network": "amoy". If you do it with the make generate-issuer-did command, then the program will ge the variables from the .env files that must be properly filled. (.env-samples are available at [Issuer Node GitHub repository](https://github.com/0xPolygonID/issuer-node/tree/main)). + - An Issuer will need to create a new identity for Amoy, through the core API specifying the proper "network": "amoy". If you do it with the make generate-issuer-did command, then the program will get the variables from the .env files that must be properly filled. (.env-samples are available at [Issuer Node GitHub repository](https://github.com/0xPolygonID/issuer-node/tree/main)). - Here you can find more details about issuer configuration ([advanced Issuer Node configuration](https://devs.polygonid.com/docs/issuer/issuer-configuration)). 2. Deprecating and shutting down existing Issuer nodes configured for the Mumbai testnet. diff --git a/docs/wallet/wallet-sdk/polygonid-sdk/credential/save-claims.md b/docs/wallet/wallet-sdk/polygonid-sdk/credential/save-claims.md index 8d4cbf3c..8dfaf8da 100644 --- a/docs/wallet/wallet-sdk/polygonid-sdk/credential/save-claims.md +++ b/docs/wallet/wallet-sdk/polygonid-sdk/credential/save-claims.md @@ -2,7 +2,7 @@ id: save-claims title: Save credentials sidebar_label: Save Credentials -description: Store a list of ClaimEntity associated with an identity in the the Polygon ID Sdk. +description: Store a list of ClaimEntity associated with an identity in the Polygon ID Sdk. keywords: - docs - polygon id @@ -14,7 +14,7 @@ keywords: - credential --- -Store a list of `ClaimEntity` in the the Polygon ID SDK associated to an identity. +Store a list of `ClaimEntity` in the Polygon ID SDK associated to an identity. ```dart Future> saveClaims( diff --git a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/add-did-profile-info.md b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/add-did-profile-info.md index 2306ea37..f9d0453e 100644 --- a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/add-did-profile-info.md +++ b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/add-did-profile-info.md @@ -25,7 +25,7 @@ Future addDidProfileInfo({ }); ``` -`did` is the DID we interactedd with. +`did` is the DID we interacted with. The `privateKey` is the key used to access all the sensitive information from the identity and also to realize operations like generating proofs. diff --git a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info-list.md b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info-list.md index 82d68030..a803f5a9 100644 --- a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info-list.md +++ b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info-list.md @@ -24,7 +24,7 @@ Future>> getDidProfileInfoList({ }); ``` -`did` is the DID we interactedd with. +`did` is the DID we interacted with. The `privateKey` is the key used to access all the sensitive information from the identity and also to realize operations like generating proofs. diff --git a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info.md b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info.md index 94dd9496..7f668d6a 100644 --- a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info.md +++ b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-did-profile-info.md @@ -24,7 +24,7 @@ Future> getDidProfileInfo({ }); ``` -`did` is the DID we interactedd with. +`did` is the DID we interacted with. The `privateKey` is the key used to access all the sensitive information from the identity and also to realize operations like generating proofs. diff --git a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-interactions.md b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-interactions.md index 292b8c15..02b02f2b 100644 --- a/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-interactions.md +++ b/docs/wallet/wallet-sdk/polygonid-sdk/iden3comm/api/get-interactions.md @@ -3,7 +3,7 @@ id: get-interactions title: Get Interactions sidebar_label: Get Interactions description: "Get a list of `InteractionEntity` associated to the identity previously stored - in the the Polygon ID Sdk." + in the Polygon ID Sdk." keywords: - docs - polygon id @@ -15,7 +15,7 @@ keywords: - Interaction Entity --- -Get a list of `InteractionEntity` associated to the identity previously stored in the the Polygon ID SDK. +Get a list of `InteractionEntity` associated to the identity previously stored in the Polygon ID SDK. ```dart Future> getInteractions({