summaryrefslogtreecommitdiff
path: root/Best-Practices.md
diff options
context:
space:
mode:
authorBrian Exelbierd2019-07-27 21:44:47 +0200
committerBrian Exelbierd2019-07-27 21:44:47 +0200
commit6c0e96fcfb661f492b24c9e7fb9f35e14835ca70 (patch)
tree7823c823b87a3a9c2efcb707528c59c8243e4f7c /Best-Practices.md
parent83130d35183dfd77aaf84f5985b179dfe7af9dd1 (diff)
fix link format
Diffstat (limited to 'Best-Practices.md')
-rw-r--r--Best-Practices.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Best-Practices.md b/Best-Practices.md
index f16561a..3047b12 100644
--- a/Best-Practices.md
+++ b/Best-Practices.md
@@ -2,7 +2,7 @@ A collection of wisdom and best practices. Use this after careful consideration
* Don't backup your `gocryptfs.conf` file to public sources.
- See [https://github.com/rfjakob/gocryptfs/issues/50](Issue 50) for reasons. In short, you should consider not saving this file in public cloud-style backups and instead make sure you have backed it up elsewhere and stored your master key (visible when you ran `gocryptfs -init`).
+ See [Issue 50](https://github.com/rfjakob/gocryptfs/issues/50) for reasons. In short, you should consider not saving this file in public cloud-style backups and instead make sure you have backed it up elsewhere and stored your master key (visible when you ran `gocryptfs -init`).
* Do backup you `gocryptfs.diriv`