summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorTobias Geerinckx-Rice <me@tobias.gr>2019-06-09 03:29:59 +0200
committerTobias Geerinckx-Rice <me@tobias.gr>2019-06-09 15:33:03 +0200
commit940511257c83538f8cd7631292d173c8ce927152 (patch)
treec4b380b85520488c1c498be218401b68f2b802af /doc
parent2d1d59ab57587e7853658fefd59f8532502d09fa (diff)
downloadguix-940511257c83538f8cd7631292d173c8ce927152.tar.gz
doc: Fix typos.
* doc/guix.texi (Version Control Services): Fix typos & edit surrounding
text.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index bd0f3e8fd5..a9cd66ce87 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -22723,10 +22723,10 @@ Extra options will be passed to @code{git daemon}, please run
 @end deftp
 
 The @code{git://} protocol lacks authentication.  When you pull from a
-repository fetched via @code{git://}, you don't know that the data you
-receive was modified is really coming from the specified host, and you
-have your connection is subject to eavesdropping.  It's better to use an
-authenticated and encrypted transport, such as @code{https}.  Although Git allows you
+repository fetched via @code{git://}, you don't know whether the data you
+receive was modified or is even coming from the specified host, and your
+connection is subject to eavesdropping.  It's better to use an authenticated
+and encrypted transport, such as @code{https}.  Although Git allows you
 to serve repositories using unsophisticated file-based web servers,
 there is a faster protocol implemented by the @code{git-http-backend}
 program.  This program is the back-end of a proper Git web service.  It