Ignores *.1 and *.7 files, closes #690 (#691)

* Ignores `*.1` and `*.7` files, closes #690

* Now adds `*.1` files to test them

Author: sobolevn

.gitattributes

@@ -1,6 +1,10 @@
 # Excluding from GitHub languages:
 vendor/ linguist-vendored
 
+# Excluding from GitHub diff:
+*.1 linguist-generated
+*.7 linguist-generated
+
 # Excluding from `git diff`:
 *.1 -diff
 *.7 -diff

man/man1/git-secret-hide.1

@@ -9,7 +9,7 @@ git-secret-hide - encrypts all added files with the inner keyring.
 ## DESCRIPTION
 `git-secret-hide` creates an encrypted version (typically called `filename.txt.secret`)
 of each file added by `git-secret-add` command.
-Now anyone enabled via 'git secret tell' can can decrypt these files. Under the hood,
+Now anyone enabled via `git secret tell` can can decrypt these files. Under the hood,
 `git-secret` uses the keyring in `.gitsecret/keys` and user's secret keys to decrypt the files.
 
 It is recommended to encrypt (or re-encrypt) all the files in a `git-secret` repo each

man/man1/git-secret-hide.1.md

@@ -7,7 +7,7 @@ These steps cover the basic process of using `git-secret`:
 
 0. Before starting, [make sure you have created a `gpg` RSA key-pair](#using-gpg): a public and a secret key identified by your email address.
 
-1. Begin with an existing or new git repository. You'll use the 'git-secret' commands to add the keyrings and information
+1. Begin with an existing or new git repository. You'll use the `git-secret` commands to add the keyrings and information
 to make `git-secret` hide and reveal files in this repository.
 
 2. Initialize the `git-secret` repository by running `git secret init` command. The `.gitsecret/` folder will be created.