Add spell check

Author: marcbaque

.github/workflows/build.yml

@@ -17,8 +17,12 @@ jobs:
       - uses: actions/setup-node@v3
         with:
           node-version: 18
-      - run: yarn
-      - run: yarn run build
+      - name: Install dependencies
+        run: yarn
+      - name: Spell check
+        run: yarn run spell-check
+      - name: Build
+        run: yarn run build
 
   test_snippets:
     name: Test snippets

cspell.json

@@ -5,20 +5,37 @@
     "bloock",
     "quickstart",
     "msvc",
+    "permissionless",
+    "notaritzation",
     "timestamping",
     "proto",
     "totp",
     "ipfs",
     "pkcs",
     "encrypter",
     "decrypter",
+    "ciphertext",
     "struct",
     "merkle",
     "protobuf",
     "keccak",
     "gomarkdoc",
     "keypair",
     "staticmethod",
-    "Qma1t4uzbnB93E4rasNdu5UWMDh5qg3wMkPm68cnEyfnoM"
+    "dokka",
+    "packagist",
+    "graphglue",
+    "validproof",
+    "polygonid",
+    "iden3",
+    "didcomm",
+    "SEPA",
+    "IBAN",
+    "CCPA",
+    "PPRO",
+    "Qma1t4uzbnB93E4rasNdu5UWMDh5qg3wMkPm68cnEyfnoM",
+    "QmadTvnNKvj2fBDgen35uAp1TfP9pSPVCNeDWw4fitqqne",
+    "2q544HUegzeRpwr3V2qu9eMwgrAmF5x4E1NCPzbQc4",
+    "2qCU58EJgrELSJT6EzT27Rw9DhvwamAdbMLpePztYq"
   ]
-}
+}

docs/guides/billing/subscription/manage-payment-method.mdx

@@ -47,6 +47,6 @@ The Single Euro Payments Area (SEPA) is an initiative of the European Union to s
 In order to debit a SEPA payment, BLOOCK must collect their customer's name and bank account number in IBAN format. During the payment flow, customers must accept a mandate that gives to BLOOCK an authorization to debit the account.
 This is the mandate you are accepting when you make a SEPA payment, it will appear below the Subscribe button.
 
-By providing your IBAN and confirming this payment, you authorise (A) Enchainté Tech SL and Stripe, our payment service provider and/or PPRO, its local service provider, to send instructions to your bank to debit your account and (B) your bank to debit your account in accordance with those instructions. You are entitled to a refund from your bank under the terms and conditions of your agreement with your bank. A refund must be claimed within 8 weeks starting from the date on which your account was debited.
+By providing your IBAN and confirming this payment, you authorize (A) BLOOCK HUB SL and Stripe, our payment service provider and/or PPRO, its local service provider, to send instructions to your bank to debit your account and (B) your bank to debit your account in accordance with those instructions. You are entitled to a refund from your bank under the terms and conditions of your agreement with your bank. A refund must be claimed within 8 weeks starting from the date on which your account was debited.
 
 ![7- Manage payment method](/static/docs/guides/billing/manage-payment-method/1-sepa-payment.png)

docs/guides/platform/certifier.mdx

@@ -7,7 +7,7 @@ sidebar_position: 3
 You can learn more about Certifier here or watch a demonstration of its use through our [YouTube channel.](https://youtu.be/vLzZnNDOCXk?si=tHLeU-Sq47WuZ4yo)
 :::
 
-The Certifier tool allows you to test BLOOCK's suite of products modularly without needing integration. Seal your documents, sign, generate access control mechanisms, and host your documents simply and securely.
+The Certifier tool allows you to test BLOOCK's suite of products without needing integration. Seal your documents, sign, generate access control mechanisms, and host your documents simply and securely.
 
 This is the latest version of the Certifier tool, designed for visual testing. It allows users to upload files and perform modular testing across multiple BLOOCK products without the need for integration via SDK or API.
 
@@ -33,7 +33,7 @@ In this case, the system inserts metadata into the file to validate the signatur
 
 ![5 - Certifier](/static/docs/guides/platform/certifier/5-certifier.png)
 
-In the third step of the process with Descentralized Storage, users can activate the option to save the files to ensure their availability. If this option is selected, the system can generate an automatic validation link.
+In the third step of the process with Decentralized Storage, users can activate the option to save the files to ensure their availability. If this option is selected, the system can generate an automatic validation link.
 
 ![6 - Certifier](/static/docs/guides/platform/certifier/6-certifier.png)
 

docs/guides/platform/products.mdx

@@ -5,7 +5,7 @@ sidebar_position: 4
 
 In this section, users can find product dashboards for every product. In these specific sections, users can visualize detailed information about each product's usage, control integration, and access functionalities that visually enable the creation of tools for managing each of them.
 
-## Decentralized Timesptamping
+## Decentralized Timestamping
 
 The Decentralized Timestamping product ensures data integrity through a tamper-proof system to securely seal information fingerprints. This process verifies data existence by leveraging permissionless distributed ledgers. To delve deeper into this product, you can review the Decentralized Timestamping section.
 
@@ -33,7 +33,7 @@ Also, users can find detailed information about each of these anchors, such as g
 
 ## Digital Identity
 
-Self-sovereign identity (SSI) capabilities enable secure, non-repudiable, and privacy-preserving authentications that can be reused across multiple platforms. For more information about this product and its integration, you can review the Digital Identity section.
+Self-sovereign identity (SSI) capabilities enable secure, undeniable, and privacy-preserving authentications that can be reused across multiple platforms. For more information about this product and its integration, you can review the Digital Identity section.
 
 In this section of BLOOCK's management, users can access general metrics regarding the usage of this product, such as the number of credentials issued during this billing period and the number of credential revocations.
 
@@ -51,7 +51,7 @@ In the Issuers tab of the Digital Identity homepage, users can access more detai
 
 ![Issuer Details page](https://cdn.bloock.com/hosting/v1/hosted/56602754-a8d1-4976-b911-62259a6c201a)
 
-**Creadential Schemas**
+**Credential Schemas**
 
 The next tab displays the Credential Schemas created by the user. These schemas serve as templates for the credentials that issuers will issue. In this section, we can see the schema name, its URL, and the creation date. Additionally, we have the option to archive these schemas once they are no longer in use.
 

docs/guides/platform/setup.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 
 The first step for using BLOOCK's management system is to create an account. Create yours in [dashboard.bloock.com](https://dashboard.bloock.com/).
 
-![Signup](https://cdn.bloock.com/hosting/v1/hosted/41b6d2d8-28f9-4ff6-ae00-e53697b06899)
+![Sign-up](https://cdn.bloock.com/hosting/v1/hosted/41b6d2d8-28f9-4ff6-ae00-e53697b06899)
 
 ![enter image description here](https://cdn.bloock.dev/hosting/v1/hosted/d6e39f1e-1f27-4e9e-bf0a-8a8ca7f9f8e8)
 

docs/guides/products/availability/features/download.mdx

@@ -5,7 +5,7 @@ sidebar_position: 2
 
 import SdkCodeBlock from '/docs/partials/_sdk-code-block.mdx';
 
-# Dowload data
+# Download data
 
 ### Hosted
 

docs/guides/products/identity/concepts/functional-flow.mdx

@@ -89,4 +89,4 @@ If you want to use our verification process, here is how it works:
 
 Finally, Issuer may decide to revoke or invalidate any credential. Therefore, you will have to execute the [revocation](./core.mdx#revocation) process.
 Having a credential revoked what it means is that the Holder will not be able to generate any [proof](./core.mdx#proofs).
-When you revoke a credential what we are doing is generate a new [Sparse Merkle Tree Proof](./core.mdx#sparse-merkle-tree-proof) of revoation. Therefore, we need the [Issuer's state](./core.mdx#state-transition) to be processed once the revocation action is executed. And obviously this state transition will be marked by the [interval](./core.mdx#issuer-intervals) we have set. **It is important to note that the effect of the revocation will not be visible until this Issuer state transition is executed**.
+When you revoke a credential what we are doing is generate a new [Sparse Merkle Tree Proof](./core.mdx#sparse-merkle-tree-proof) of revocation. Therefore, we need the [Issuer's state](./core.mdx#state-transition) to be processed once the revocation action is executed. And obviously this state transition will be marked by the [interval](./core.mdx#issuer-intervals) we have set. **It is important to note that the effect of the revocation will not be visible until this Issuer state transition is executed**.

docs/guides/products/identity/features/credential-revocation.mdx

@@ -5,7 +5,7 @@ sidebar_position: 5
 
 Finally, Issuer may decide to revoke or invalidate any credential. Therefore, you will have to execute the [revocation](#revocation) process.
 Having a credential revoked what it means is that the Holder will not be able to generate any [proof](#proofs).
-When you revoke a credential what we are doing is generate a new [Sparse Merkle Tree Proof](#proof) of revoation. Therefore, we need the [Issuer's state](#state-transition) to be processed once the revocation action is executed. And obviously this state transition will be marked by the [interval](#issuer-intervals) we have set. **It is important to note that the effect of the revocation will not be visible until this Issuer state transition is executed**.
+When you revoke a credential what we are doing is generate a new [Sparse Merkle Tree Proof](#proof) of revocation. Therefore, we need the [Issuer's state](#state-transition) to be processed once the revocation action is executed. And obviously this state transition will be marked by the [interval](#issuer-intervals) we have set. **It is important to note that the effect of the revocation will not be visible until this Issuer state transition is executed**.
 
 ## Examples
 

docs/guides/products/identity/overview.mdx

@@ -9,7 +9,7 @@ Welcome to our Digital Identity solution, where privacy-first digital identities
 
 #### Privacy-First Digital Identities:
 
-- Utilize self-sovereign identity capabilities to enable secure, non-repudiable, and privacy-preserving authentications usable across multiple platforms.
+- Utilize self-sovereign identity capabilities to enable secure, undeniable, and privacy-preserving authentications usable across multiple platforms.
 - Provision digital identities at scale, ensuring absolute privacy and security without compromising decentralization.
 
 #### Scalable Identity Provisioning:
@@ -29,7 +29,7 @@ Welcome to our Digital Identity solution, where privacy-first digital identities
 
 #### Transparency and Accountability:
 
-- Obtain non-repudiable and verifiable traceability of all user authentications and digital interactions, preventing identity theft and bolstering identifications.
+- Obtain undeniable and verifiable traceability of all user authentications and digital interactions, preventing identity theft and bolstering identifications.
 - Guarantee adherence to tailored access policies, strengthening access control and security measures.
 - Strengthen authentication security and non-repudiation by gathering undeniable evidence of access and interactions.