From 537f4430015ff4d258e1de16b80ad8306da7b959 Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:23:36 +0200 Subject: [PATCH 1/6] fix typos auths.md --- build-with-sismo-connect/technical-documentation/auths.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build-with-sismo-connect/technical-documentation/auths.md b/build-with-sismo-connect/technical-documentation/auths.md index 54cb2c4..c610d1d 100644 --- a/build-with-sismo-connect/technical-documentation/auths.md +++ b/build-with-sismo-connect/technical-documentation/auths.md @@ -131,7 +131,7 @@ function onClick(){ }); } -// Proofs are available in two differents types depending on usage (offchain or onchaon verification) +// Proofs are available in two different types depending on usage (offchain or onchain verification) const response: SismoConnectResponse | null = sismoConnect.getResponse(); const responseBytes: string | null = sismoConnect.getResponseBytes(); @@ -162,7 +162,7 @@ function onClick(){ }); } -// Proofs are available in two differents types depending on usage (offchain or onchaon verification) +// Proofs are available in two different types depending on usage (offchain or onchain verification) const response: SismoConnectResponse | null = sismoConnect.getResponse(); const responseBytes: string | null = sismoConnect.getResponseBytes(); From 6f0d75da8595742446c091d24ad9d922e0d73ce7 Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:25:22 +0200 Subject: [PATCH 2/6] fix typos claims.md --- build-with-sismo-connect/technical-documentation/claims.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/build-with-sismo-connect/technical-documentation/claims.md b/build-with-sismo-connect/technical-documentation/claims.md index c48401a..5265205 100644 --- a/build-with-sismo-connect/technical-documentation/claims.md +++ b/build-with-sismo-connect/technical-documentation/claims.md @@ -44,7 +44,7 @@ Requests are then verified either in a backend using the [`sismo-connect-server` ### Making a ClaimRequest - Front-end integration {% hint style="info" %} -Making an `ClaimRequest` is only possible in the front end as the request redirects users to the Sismo Vault app, where users can generate a zero-knowledge proof. +Making a `ClaimRequest` is only possible in the front end as the request redirects users to the Sismo Vault app, where users can generate a zero-knowledge proof. {% endhint %} {% tabs %} @@ -135,7 +135,7 @@ function onClick(){ }); } -// Proofs are available in two differents types depending on usage (offchain or onchaon verification) +// Proofs are available in two different types depending on usage (offchain or onchain verification) const response: SismoConnectResponse | null = sismoConnect.getResponse(); const responseBytes: string | null = sismoConnect.getResponseBytes(); @@ -166,7 +166,7 @@ function onClick(){ }); } -// Proofs are available in two differents types depending on usage (offchain or onchaon verification) +// Proofs are available in two different types depending on usage (offchain or onchain verification) const response: SismoConnectResponse | null = sismoConnect.getResponse(); const responseBytes: string | null = sismoConnect.getResponseBytes(); From fd6149744945c6945ad3edb331b93d7d7e20630c Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:30:09 +0200 Subject: [PATCH 3/6] fix typos signature.md --- build-with-sismo-connect/technical-documentation/signature.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build-with-sismo-connect/technical-documentation/signature.md b/build-with-sismo-connect/technical-documentation/signature.md index 21792f5..8286db1 100644 --- a/build-with-sismo-connect/technical-documentation/signature.md +++ b/build-with-sismo-connect/technical-documentation/signature.md @@ -44,7 +44,7 @@ If you are verifying your proofs in a smart contract, you will need to encode yo ### Making a SignatureRequest - Front-end integration {% hint style="info" %} -Making an `SignatureRequest` is only possible if it is made alongside an auth or a claim request. +Making a `SignatureRequest` is only possible if it is made alongside an auth or a claim request. {% endhint %} {% tabs %} @@ -109,7 +109,7 @@ function onClick(){ }); } -// Proofs are available in two differents types depending on usage (offchain or onchaon verification) +// Proofs are available in two different types depending on usage (offchain or onchain verification) const response: SismoConnectResponse | null = sismoConnect.getResponse(); const responseBytes: string | null = sismoConnect.getResponseBytes(); From 40a6b70c5206eeb8dd97906610e8198800a4bc05 Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:34:09 +0200 Subject: [PATCH 4/6] minor typo deploy-your-contracts.md --- build-with-sismo-connect/tutorials/deploy-your-contracts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-with-sismo-connect/tutorials/deploy-your-contracts.md b/build-with-sismo-connect/tutorials/deploy-your-contracts.md index 90e831a..31f6377 100644 --- a/build-with-sismo-connect/tutorials/deploy-your-contracts.md +++ b/build-with-sismo-connect/tutorials/deploy-your-contracts.md @@ -2,7 +2,7 @@ ## Overview -This tutorial aims at describing the process behind the deployment of Sismo Connect contracts. In this context, we will recap on what a Sismo Connect Client config is and how to impersonate accounts. Once understood, these notions will allow you to confidently deploy contracts with Sismo Connect's functionalities. +This tutorial aims to describe the process behind the deployment of Sismo Connect contracts. In this context, we will recap on what a Sismo Connect Client config is and how to impersonate accounts. Once understood, these notions will allow you to confidently deploy contracts with Sismo Connect's functionalities. {% hint style="success" %} To better understand the different notions highlighted in this tutorial, we strongly advise you to go through [**the first tutorial**](tuto.md)**,** which will show you how to leverage data aggregation in your app by [**building a Gated Airdrop for Gitcoin Passport holders**](tuto.md). From b5417b17e34411ff3f4afd963760791732a245bc Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:36:06 +0200 Subject: [PATCH 5/6] fix typo tuto.md --- build-with-sismo-connect/tutorials/tuto.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/build-with-sismo-connect/tutorials/tuto.md b/build-with-sismo-connect/tutorials/tuto.md index 17c8541..d66d873 100644 --- a/build-with-sismo-connect/tutorials/tuto.md +++ b/build-with-sismo-connect/tutorials/tuto.md @@ -93,7 +93,7 @@ Congrats on getting your airdrop! Now, let's see how this simple Sismo Connect i Go to the `front/src/app/page.tsx` {% hint style="success" %} -To use Sismo Connect in your application, you will need to create an application in the [Sismo Factory](https://factory.sismo.io/apps-explorer) and get its `appId`. You can see a quick tutorial on how to do it [here](create-a-sismo-connect-app.md). +To use Sismo Connect in your application, you will need to create an application in the [Sismo Factory](https://factory.sismo.io/apps-explorer) and get it's appId`. You can see a quick tutorial on how to do it [here](create-a-sismo-connect-app.md). For this tutorial, we will use an already existing app (appId: 0xf4977993e52606cfd67b7a1cde717069) {% endhint %} @@ -146,7 +146,7 @@ Let's add the Sismo Connect Button and request the`vaultId` of users.
-vaultId: anonymous indentifier for a user. Will be used to avoid users to claim twice +vaultId: anonymous identifier for a user. Will be used to avoid users to claim twice Sismo users have a sovereign [Data Vault](../../data-vault/what-is-the-data-vault.md) where they import Data Sources from which they will generate ZK proofs. Each Data Vault has a secret only known by its owner. @@ -284,7 +284,7 @@ contract Airdrop is ERC20, SismoConnect { } -The `vaultId` enables protection against double spends in an anonymous way. Indeed, if a user generates a second proof from the same Vault, he would not be able to claim the airdrop again since each proof generated from a Vault has the same `vaultId` associated with it. +The `vaultId` enables protection against double spending in an anonymous way. Indeed, if a user generates a second proof from the same Vault, he would not be able to claim the airdrop again since each proof generated from a Vault has the same `vaultId` associated with it. {% hint style="success" %} If you use Impersonation Mode, you will be able to claim the airdrop each time you try since the `vaultId` is randomized in this mode. From ad593d497c3501dde809e8c5df5cd67e9146fd58 Mon Sep 17 00:00:00 2001 From: iwantanode <87604944+tudorpintea999@users.noreply.github.com> Date: Fri, 10 Nov 2023 15:39:20 +0200 Subject: [PATCH 6/6] fix typo getting-started-1.md --- build-with-sismo-connect/getting-started-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-with-sismo-connect/getting-started-1.md b/build-with-sismo-connect/getting-started-1.md index b6c647a..b51ca10 100644 --- a/build-with-sismo-connect/getting-started-1.md +++ b/build-with-sismo-connect/getting-started-1.md @@ -31,7 +31,7 @@ Before anything, go to the [Sismo Factory](https://factory.sismo.io) and create ## Quick start - (1 min) -Chose and install the starter of your choice in one unique command line. +Choose and install the starter of your choice in one unique command line. 
npx create-sismo-connect-app@latest
 # or