fix OpenVASP docs typos

trisacrypto · Jul 3, 2024 · 5b3ba77 · 5b3ba77
1 parent c9dfcda
commit 5b3ba77
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/content/openvasp/_index.en.md b/docs/content/openvasp/_index.en.md
@@ -31,7 +31,7 @@ Therefore, as you implement your TRP integration, you need to consider the follo
 
 1. **mTLS is a core part of TRP, however, TRP does not specify a Certificate Authority.** Your implementation must consider whether it wants to perform TRP only with TRISA issued certificates or if it is willing to allow other public CAs such as Verisign or Google.
 2. **There is no directory of TRP VASPs, TRP discovery is facilitated by Travel Addresses.** TRP uses [Travel Addresses](https://www.21analytics.ch/blog/how-the-trp-travel-address-solves-the-fatf-travel-rule/) to solve counterparty identification. The TRISA bridge is able to parse both LNURLs and the newer Travel Address format, however for complete TRP integration, you will have to supply your accounts with Travel Addresses so that other TRP implementers can reach you as a beneficiary counterparty.
-3. **TRP only supports transport-level cryptography, not payload-level cryptography.** There are three levels of cryptography supported by the TRISA bridge: no-cryptography, partial, insecure TRISA envelopes (encrypted but not sealed), and full TRISA compatibility. The first level is plain-vanill TRP and the second two levels are implemented using [TRP Extensions](https://gitlab.com/OpenVASP/travel-rule-protocol/-/tree/master/extensions).
+3. **TRP only supports transport-level cryptography, not payload-level cryptography.** There are three levels of cryptography supported by the TRISA bridge: no-cryptography, partial, insecure TRISA envelopes (encrypted but not sealed), and full TRISA compatibility. The first level is plain-vanilla TRP and the second two levels are implemented using [TRP Extensions](https://gitlab.com/OpenVASP/travel-rule-protocol/-/tree/master/extensions).
 
 ### For TRP Implementers
 

diff --git a/docs/content/openvasp/client.en.md b/docs/content/openvasp/client.en.md
@@ -31,7 +31,7 @@ type TRPInfo struct {
 }
 ```
 
-The `APIVersion` field is automatically populated with the defeault version, and any extensions are populated from the `Inquiry` itself, so these can be ignored.
+The `APIVersion` field is automatically populated with the default version, and any extensions are populated from the `Inquiry` itself, so these can be ignored.
 
 The `Address` field can be one of:
 
@@ -93,7 +93,7 @@ type TRPInfo struct {
 }
 ```
 
-The `APIVersion` field is automatically populated with the defeault version, and any extensions are populated from the `Confirmation` itself, so these can be ignored.
+The `APIVersion` field is automatically populated with the default version, and any extensions are populated from the `Confirmation` itself, so these can be ignored.
 
 The client returns a `TravelRuleResponse` however, a simple [204 No Content](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204) response is expected for a confirmation, so there is no JSON body to parse.