docs: various fixes for grammar, clarity, and consistency across documentation #61
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.
Changes:
1. Updated Twitter URL to x.com format
https://twitter.com) with the updatedx.comformat (https://x.com).2. Fixed typos and grammatical errors in the Encrypted Variables section
"Lets"→"Let's"in the explanation of data leakage."however"to improve sentence structure."Encrypted card values is the Player and Dealer structs are leaked and can be exploited""Encrypted card values in the Player and Dealer structs are leaked and can be exploited."3. Fixed typos and stylistic errors in the Privacy section
"Javascript"→"JavaScript"to reflect the correct capitalization of the programming language."or"in"events or metadata"for better readability.4. Grammar, clarity, and consistency improvements in Encryption & Access Control documentation
"sealed box encryption ]"→"sealed box encryption"."from NaCL"→"from NaCl"(proper case usage for the cryptographic library)."Similarly to decryption, this usage can be implemented by any compliant library, but we include direct support in fhenix.js."→
"Similar to decryption, this can be implemented by any compliant library, but direct support is included in fhenix.js.""This is done in 3 steps: generating a permit, querying the contract and unsealing the data."→
"This process involves three steps: generating a permit, querying the contract, and unsealing the data.""the caller is who he says he is."→"the caller is who they claim to be.""Simply, they are a signed message that contains the caller's public key""Out-of-the-box, Fhenix Solidity libraries come with a basic access control scheme."→
"The Fhenix Solidity libraries include a built-in access control scheme."Summary: