awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-07 22:27:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1519 from Grraahaam/fix/typo

Browse Source 
chore(doc): fix typo
This commit is contained in:
Maidul Islam
2024-03-02 16:36:26 -05:00
committed by GitHub
parent 5feb942d79 60134cf8ac
commit 846e2f21cc
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/documentation/platform/project-upgrade.mdx
+1 -2
View File
@@ -2,7 +2,6 @@
title: "Enhancing Security and Usability: Project Upgrades" title: "Enhancing Security and Usability: Project Upgrades"
--- ---
At Infisical, we're constantly striving to elevate the security and usability standards of our platform to better serve our users. At Infisical, we're constantly striving to elevate the security and usability standards of our platform to better serve our users.
With this commitment in mind, we're excited to introduce our latest addition, non-E2EE projects, aimed at addressing two significant issues while enhancing how clients interact with Infisical programmatically. With this commitment in mind, we're excited to introduce our latest addition, non-E2EE projects, aimed at addressing two significant issues while enhancing how clients interact with Infisical programmatically.
@@ -11,7 +10,7 @@ Additionally, our API lacked the capability to interact with projects without de
These obstacles made API driven automation and collaboration a painful experience for a majority of our users. These obstacles made API driven automation and collaboration a painful experience for a majority of our users.
To overcome these limitations, our upgrade focuses on disabling end-to-end encryption (E2EE) for projects. To overcome these limitations, our upgrade focuses on disabling end-to-end encryption (E2EE) for projects.
While this may raise eyebrows, it's important to understand that this decision is a strategic move to make Infisical easer to use and interact with. While this may raise eyebrows, it's important to understand that this decision is a strategic move to make Infisical easier to use and interact with.
But what does this mean for our users? Essentially nothing, there are no changes required on your end. But what does this mean for our users? Essentially nothing, there are no changes required on your end.
Rest assured, all sensitive data remains encrypted at rest according to the latest industry standards. Rest assured, all sensitive data remains encrypted at rest according to the latest industry standards.