docs(help): typo in documents (#10064)

This commit is contained in:
Masatoshi Ogiwara
2026-07-08 12:41:17 +09:00
committed by GitHub
parent aadb6e3a01
commit afd63db043
2 changed files with 3 additions and 3 deletions

View File

@@ -21,7 +21,7 @@ On all three platforms we use the same exact library for all cryptographic funct
> info Fun story
>
> When we first added encryption, we used AES-GCM-256 across platforms but the cross-platform compatbility was abyssmal. That is when I found out about the great libsodium. Written in C, wrappers available for all platforms...what more could I want?
> When we first added encryption, we used AES-GCM-256 across platforms but the cross-platform compatibility was abyssmal. That is when I found out about the great libsodium. Written in C, wrappers available for all platforms...what more could I want?
## Process
@@ -65,7 +65,7 @@ On iOS and Android, the encryption key is stored in the phone's keychain.
### 4. Data encryption
Encryption only takes place when you sync. Each item in the database is encrypted seperately using XChaCha-Poly1305-IETF.
Encryption only takes place when you sync. Each item in the database is encrypted separately using XChaCha-Poly1305-IETF.
#### How it works

View File

@@ -29,7 +29,7 @@ The first step to recovering your account consists of requesting an account reco
5. On the next page, your email should be prefilled. If it isn't, fill it out.
![](/static/account-recovery/step-2.png)
6. Click on `Send recovery email`
7. If everything goes well, you should recieve an email from Notesnook in your inbox:
7. If everything goes well, you should receive an email from Notesnook in your inbox:
![](/static/account-recovery/recovery_email.png)
> info What if I didn't receive an email?
>