mirror of
https://github.com/beemdevelopment/Aegis.git
synced 2025-04-21 06:19:12 +00:00
Fix some typos in docs
This commit is contained in:
parent
adc9179364
commit
8a9a0856fb
3 changed files with 4 additions and 4 deletions
|
@ -115,7 +115,7 @@ Aegis supports icon packs to make it easier to assign icons to the entries in
|
|||
your vault. There are no official icon packs, but the community maintains a
|
||||
number of third-party icon packs you may want to check out. To learn how to
|
||||
create your own Aegis-compatible icon pack, see [the
|
||||
documenation](docs/iconpacks.md).
|
||||
documentation](docs/iconpacks.md).
|
||||
|
||||
- [aegis-icons](https://github.com/aegis-icons/aegis-icons)
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ is randomly generated once and stays the same across different versions.
|
|||
Every icon definition contains the filename of the icon file, relative to the
|
||||
root of the .ZIP archive. Icon definitions also have a list of strings that the
|
||||
Issuer field in Aegis is matched against for automatic selection of an icon for
|
||||
new entries. Matching is done in a case-insensitve manner. There's also a
|
||||
new entries. Matching is done in a case-insensitive manner. There's also a
|
||||
category field.
|
||||
|
||||
The following image formats are supported, in order of preference:
|
||||
|
|
|
@ -107,7 +107,7 @@ shown below:
|
|||
It starts with a ``version`` number and a ``header``. If a backwards
|
||||
incompatible change is introduced to the content format, the version number will
|
||||
be incremented. The vault contents are stored under ``db``. Its value depends on
|
||||
wheter the vault is encrypted or not. If it is, the value is a string containing
|
||||
whether the vault is encrypted or not. If it is, the value is a string containing
|
||||
the Base64 encoded (with padding) ciphertext of the vault contents. Otherwise,
|
||||
the value is a JSON object.
|
||||
|
||||
|
@ -219,7 +219,7 @@ be incremented.
|
|||
#### Entries
|
||||
|
||||
Each entry has a unique randomly generated ``UUID`` (version 4), as well as a
|
||||
``name`` and ``issuer`` to idenfity the account name and service that the token
|
||||
``name`` and ``issuer`` to identify the account name and service that the token
|
||||
is for. Entries can also have an icon. These are JPEG's encoded in Base64 with
|
||||
padding. The ``info`` object holds information specific to the OTP type. The
|
||||
``secret`` is encoded in Base32 without padding.
|
||||
|
|
Loading…
Add table
Reference in a new issue