Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: fix some readme grammar #126

Merged
merged 1 commit into from
Jun 13, 2017
Merged

chore: fix some readme grammar #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ on Linux/UNIX systems.
To add an mount point to an existing store add an entry to the `mounts` object
of the store.

gopass tries to read it's configuration from `$HOME/.config/gopass/config.yml` if present.
gopass tries to read its configuration from `$HOME/.config/gopass/config.yml` if present.
You can override this location by setting `GOPASS_CONFIG` to another location.

Mounting new stores can be done through gopass:
Expand Down Expand Up @@ -282,15 +282,15 @@ This makes it easy to e.g. generate database passwords or use templates for cert

### GnuPG

`gopass` use `gpg` to encrypt it's secrets. This makes it easy to build a software we feel comfortable
with trusting our credentials, but `gpg` isn't know for being the most user-friendly software.
`gopass` uses [gpg](https://www.gnupg.org) to encrypt its secrets. This makes it easy to build a software we feel comfortable
trusting our credentials with, but `gpg` isn't known for being the most user-friendly software.

We try to work around some of the useability limitations of `gpg` but we always have to keep the security
goals in mind, so some features have to trade some useability against security and vice versa.
We try to work around some of the usability limitations of `gpg` but we always have to keep the security
goals in mind, so some features have to trade some usability against security and vice-versa.

### git history and local files

Please keep in mind that by default `gopass` stores it's encrypted secrets in git. *This is a deviation
Please keep in mind that by default `gopass` stores its encrypted secrets in git. *This is a deviation
from the behavior of `pass`, which does not force you to use `git`.* Furthermore, the decision has some important
properties.

Expand Down