fix typo and update man pages

man/man1/git-secret-add.1

@@ -21,7 +21,7 @@ git secret add [\-i] <pathspec>\.\.\.
 If there\'s no users in the \fBgit\-secret\fR\'s keyring, when adding a file, an exception will be raised\.
 .
 .P
-Use the \fBgit secret add\fR command to add filenames to thie file\.
+Use the \fBgit secret add\fR command to add filenames to this file\.
 .
 .br
 It is not recommended to add filenames directly into \fB\.gitsecret/paths/mapping\.cfg\fR\.

man/man1/git-secret-add.1.ronn

@@ -13,7 +13,7 @@ them in .gitignore, since they must be secure and not be committed into the remo
 
 If there's no users in the `git-secret`'s keyring, when adding a file, an exception will be raised.
 
-Use the `git secret add` command to add filenames to thie file.  
+Use the `git secret add` command to add filenames to this file.  
 It is not recommended to add filenames directly into `.gitsecret/paths/mapping.cfg`.
 
 

man/man7/git-secret.7

@@ -16,10 +16,10 @@ Before starting, make sure you have created \fBgpg\fR RSA key\-pair: public and
 Begin with an existing or new git repository\. You\'ll use the \'git secret\' commands to add the keyrings and information to make the git\-secret hide and reveal files in this repository\.
 .
 .IP "3." 4
-Initialize the \fBgit\-secret\fR repository by running \fBgit secret init\fR command\. the \fB\.gitsecret/\fR folder will be created, \fBNote\fR that the contents of the \fB\.gitsecret/\fR folder should all be checked in, with the exception of the random_seed file\. In other words, only the random_seen file should be mentioned in your \.gitignore file]
+Initialize the \fBgit\-secret\fR repository by running \fBgit secret init\fR command\. the \fB\.gitsecret/\fR folder will be created, \fBNote\fR all the contents of the \fB\.gitsecret/\fR folder should be checked in, /except/ the \fBrandom_seed\fR file\. In other words, of the files in \.gitsecret, only the random_seed file should be mentioned in your \.gitignore file\.
 .
 .IP "4." 4
-Add first user to the git\-secret repo keyring by running \fBgit secret tell your@gpg\.email\fR\.
+Add the first user to the git\-secret repo keyring by running \fBgit secret tell your@gpg\.email\fR\.
 .
 .IP "5." 4
 Now it\'s time to add files you wish to encrypt inside the \fBgit\-secret\fR repository\. It can be done by running \fBgit secret add <filenames\.\.\.>\fR command\. Make sure these files are ignored by mentions in \.gitignore, otherwise \fBgit\-secret\fR won\'t allow you to add them, as these files could be stored unencrypted\.
@@ -52,10 +52,10 @@ The newly added user cannot yet read the encrypted files\. Now, re\-encrypt the
 .IP "" 0
 .
 .P
-Note that it is possible to add yourself to the git\-secret repo without decrypting existing files\. It will be possible to decrypt them after reencrypting them with the new keyring\. So, if you don\'t want unexpected keys added, make sure to configure some server\-side security policy with the \fBpre\-receive\fR hook\.
+Note that it is possible to add yourself to the git\-secret repo without decrypting existing files\. It will be possible to decrypt them after reencrypting them with the new keyring\. So, if you don\'t want unexpected keys added, you can configure some server\-side security policy with the \fBpre\-receive\fR hook\.
 .
 .SH "Configuration"
-You can configure the version of gpg used, or the extension your encrypted files uses, to suit your workflow better\. To do so, just set the required variable to the value you need\. This can be done in your shell environment file or with each \fBgit\-secret\fR command\.
+You can configure the version of gpg used, or the extension your encrypted files use, to suit your workflow better\. To do so, just set the required variable to the value you need\. This can be done in your shell environment file or with each \fBgit\-secret\fR command\.
 .
 .P
 The settings available to be changed are: