Skip to content

docs: fix incorrect ✅ symbols and typo in introduction pages #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alelpoan wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs: fix incorrect ✅ symbols and typo in introduction pages #29

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
332f05d
docs: fix incorrect symbols for problem statements in fhenix.mdx
alelpoan May 18, 2026
7411adc
docs: fix typo "experince" in compatibility.mdx
alelpoan May 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion get-started/introduction/compatibility.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ When working with CoFHE components:
- **Check release notes**: Review breaking changes and migration guides when upgrading

<Tip>
For the best development experince, use the latest versions of all components. They are designed to work together seamlessly and include the latest features and security improvements.
For the best development experience, use the latest versions of all components. They are designed to work together seamlessly and include the latest features and security improvements.
</Tip>

## Network Compatibility
Expand Down
6 changes: 3 additions & 3 deletions get-started/introduction/fhenix.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ Blockchain is often praised for its **decentralization, immutability, and transp
In public blockchains like Ethereum, every transaction, smart contract interaction, and account balance is **completely visible** to anyone. This radical transparency, while crucial for establishing trust and enabling verification, creates significant privacy challenges. FHE solves this fundamental tradeoff by allowing data to remain **fully encrypted** while still maintaining the network's ability to verify its accuracy and authenticity. This means sensitive information can be processed and validated without ever being exposed, combining the best of both worlds - **bulletproof privacy with trustless verification**.

**Real-world consequences of blockchain transparency:** \
✅ **Front-running & MEV** – Traders can analyze mempools and exploit pending transactions before they are executed. \
✅ **Confidentiality leaks** – Sensitive financial transactions, payroll information, or business logic are exposed. \
✅ **Enterprise adoption hurdles** – Companies are reluctant to use public blockchains if competitors can access proprietary data.
🔴 **Front-running & MEV** – Traders can analyze mempools and exploit pending transactions before they are executed. \
🔴 **Confidentiality leaks** – Sensitive financial transactions, payroll information, or business logic are exposed. \
🔴 **Enterprise adoption hurdles** – Companies are reluctant to use public blockchains if competitors can access proprietary data.

These challenges can all be mitigated by using FHE in your smart contracts.

Expand Down