mirrors/age
1
0
Fork 0
mirror of https://github.com/FiloSottile/age.git synced 2026-01-06 12:06:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: fix typos

Browse Source
This commit is contained in:
a1346054
2022-08-01 20:29:16 +00:00
committed by Filippo Valsorda
parent bbac0a501c
commit 3f2209cab9
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.github/CONTRIBUTING.md vendored
View File

@@ -22,11 +22,11 @@ In particular, I'm unlikely to merge into the main repo anything I don't use mys
age itself is not community maintained, but its ecosystem very much is, and that's where a lot of the strength of age is! Here are some ideas for ways to contribute to age and its ecosystem, besides contributing to this repository.
* **Write an article about how to use age for a certain community or use case.** The number one reason people don't use age is because they haven't heard about it and existsing tutorials present more complex alternatives.
* **Write an article about how to use age for a certain community or use case.** The number one reason people don't use age is because they haven't heard about it and existing tutorials present more complex alternatives.
* Integrate age into existing projects that might use it, for example replacing legacy alternatives.
* Build and maintain an [age plugin](https://c2sp.org/age-plugin) for a KMS or platform.
* Watch the [discussions](https://github.com/FiloSottile/age/discussions) and help other users.
* Provide bindings in a langauge or framework that doesn't support age well.
* Provide bindings in a language or framework that doesn't support age well.
* Package age for an ecosystem that doesn't have packages yet.
If you build or write something related to age, [let me know](https://github.com/FiloSottile/age/discussions/new?category=general)! 💖

2
doc/age.1.ronn
View File

@@ -229,7 +229,7 @@ to use the `-j` flag.
full length of the input.
If an error occurs during decryption, partial output might still be generated,
but only if it was possible to securely authenticate it. No unauthenticathed
but only if it was possible to securely authenticate it. No unauthenticated
output is ever released.
## BACKWARDS COMPATIBILITY