[DOC] Fix grammar

Thanks to Patrick Chkoreff.

Signed-off-by: Sergey Matveev <stargrave@stargrave.org>

diff --git a/doc/download.texi b/doc/download.texi
index ea2e04fba02606bb673325808e9adef9d13562b3..5168e341a3f33a963bb5323a4616c54eb4b87017 100644 (file)
--- a/doc/download.texi
+++ b/doc/download.texi
@@ -29,11 +29,11 @@ You can obtain releases source code prepared tarballs from the links below:
 
 @end multitable
 
-Also you can try it's @ref{Contacts, .onion} version.
+Also you can try its @ref{Contacts, .onion} version.
 Sourceforge.net also provides mirror for the files above:
 @url{http://sourceforge.net/projects/govpn/files/}.
 
-You can obtain it's development source code by cloning
+You can obtain its development source code by cloning
 Git repository: @code{git clone https://github.com/stargrave/govpn.git}.
 Pay attention that it does not contain compiled documentation and is not
 recommended for porters because of that.

diff --git a/doc/handshake.texi b/doc/handshake.texi
index 6f1e37e32a72098cb00abb3b28238fe8ae1cfcf2..7e0cc5301e903239d82a6300a80d568f2edef84e 100644 (file)
--- a/doc/handshake.texi
+++ b/doc/handshake.texi
@@ -64,9 +64,9 @@ symmetric encryption.
     @item Server decrypts @code{RS}, @code{RC}, @code{SC},
     @code{Sign(DSAPriv, K)}.
 
-    @item Compares @code{RS} with it's own one sent before. Server
+    @item Compares @code{RS} with its own one sent before. Server
     decrypts @code{RS}, @code{RC}, @code{SC} with key @code{K}, compares
-    @code{RS} with it's own one sent before.
+    @code{RS} with its own one sent before.
 
     @item Verifies @code{K} signature with verifier @code{DSAPub}.
 
@@ -80,7 +80,7 @@ symmetric encryption.
 @item
 @itemize @bullet
 @item Client decrypts @code{RC}
-@item Compares with it's own one sent before.
+@item Compares with its own one sent before.
 @item Computes final session encryption key as server did.
 @end itemize
 

diff --git a/doc/news.texi b/doc/news.texi
index 75ec725137b1b9640dd0dc3bb7e0b1505ff05aa8..7160587c17152a4e30c8c9f1d4f2abee5d75244d 100644 (file)
--- a/doc/news.texi
+++ b/doc/news.texi
@@ -23,7 +23,7 @@ packets became smaller
 
 @item
 Ability to hide underlying packets lengths by appending noise, junk
-data during transmission. Each packet can be fill up-ed to it's
+data during transmission. Each packet can be fill up-ed to its
 maximal MTU size.
 
 @item

diff --git a/doc/precautions.texi b/doc/precautions.texi
index 93b179e427f6829246d6a45e4b70bb0cb0f8068e..cd759ea72708dd0503cb77fd01d3f226c0b6f3f5 100644 (file)
--- a/doc/precautions.texi
+++ b/doc/precautions.texi
@@ -3,13 +3,13 @@
 
 The very important precaution is the @strong{cryptographically good}
 pseudo random number generator. GoVPN uses native operating system PRNG
-as entropy source. You have no way to check it's quality in closed
+as entropy source. You have no way to check its quality in closed
 source code operating systems, so it is recommended not to use them if
 you really needs security. Moreover it is possible that those OS leaks
 information about possible PRNG states. And at least Apple OS X and
 Microsoft Windows are already known to have weak CSPRNGs.
 
-GoVPN could use it's own PRNG implementation like
+GoVPN could use its own PRNG implementation like
 @url{https://www.schneier.com/fortuna.html, Fortuna}, but it is
 much easier to use the right OS, to use free software.
 
@@ -19,6 +19,6 @@ If it fails, produces equal values at least once, then all you traffic
 related to that key could be decrypted.
 
 We use password (passphrase) authentication, so overall security fully
-depends on it's strength. So you should use long, high-entropy
+depends on its strength. So you should use long, high-entropy
 passphrases. Also remember to keep passphrase on temporary file as
 described in @ref{Verifier}.

diff --git a/doc/verifierstruct.texi b/doc/verifierstruct.texi
index 3b969dc07ac09f57752f228fcc38216e41473002..b508b483536d4b9e4aebef987362d126b42abe5d 100644 (file)
--- a/doc/verifierstruct.texi
+++ b/doc/verifierstruct.texi
@@ -3,7 +3,7 @@
 
 Verifier is a derivative of the password. It is resistant to
 dictionary attacks and can not be used for authentication (only
-it's verifying).
+its verifying).
 
 @verbatim
 SOURCE = PBKDF2(SALT=PeerId, PASSWORD, 1<<16, SHA512)