Updated Language Conventions (markdown)

Dominik Schürmann 2015-08-21 13:14:50 +02:00
parent 4981a206fd
commit 2704685e15
1 changed files with 1 additions and 1 deletions

@ -9,7 +9,7 @@ We try to provide a better terminology when we think that the traditional one is
| Traditional/technical phrase | Replacement in OpenKeychain | Comment | | Traditional/technical phrase | Replacement in OpenKeychain | Comment |
|------- |---- |--- | |------- |---- |--- |
| User ID | Identity | | | User ID | Identity | |
| Key ID | - | Don't mention key IDs, they serve no purpose, see https://github.com/open-keychain/open-keychain/wiki/OpenPGP-Security#key-ids-arent-displayed | | Key ID | - | Don't mention key IDs, [they serve no purpose](https://github.com/open-keychain/open-keychain/wiki/OpenPGP-Security#key-ids-arent-displayed) |
| Passphrase | Password | People don't know what a passphrase is, but they know passwords. Renaming passwords to passphrases doesn't help to increase their strength. | | Passphrase | Password | People don't know what a passphrase is, but they know passwords. Renaming passwords to passphrases doesn't help to increase their strength. |
| Public/private key | Key | Don't try to explain the concept of public key cryptography. People don't want to know it, it should work seamlessly | | Public/private key | Key | Don't try to explain the concept of public key cryptography. People don't want to know it, it should work seamlessly |
| Sign/Certify key | Confirm key | Key signing makes no sense without knowing public key crypto. Certify is more appropriate, but also difficult to understand. | | Sign/Certify key | Confirm key | Key signing makes no sense without knowing public key crypto. Certify is more appropriate, but also difficult to understand. |