gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [gnunet] branch master updated: Doc RPS: Fix writing style


From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: Doc RPS: Fix writing style of GNUnet
Date: Sat, 22 Jun 2019 00:12:47 +0200

This is an automated email from the git hooks/post-receive script.

julius-buenger pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new bda8f61b0 Doc RPS: Fix writing style of GNUnet
bda8f61b0 is described below

commit bda8f61b0f2f54a3aa675a966ef0954b8fff0d6e
Author: Julius B√ľnger <address@hidden>
AuthorDate: Sat Jun 22 00:09:29 2019 +0200

    Doc RPS: Fix writing style of GNUnet
---
 doc/handbook/chapters/keyconcepts.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/handbook/chapters/keyconcepts.texi 
b/doc/handbook/chapters/keyconcepts.texi
index 42718b245..c5cc395c8 100644
--- a/doc/handbook/chapters/keyconcepts.texi
+++ b/doc/handbook/chapters/keyconcepts.texi
@@ -338,7 +338,7 @@ of random peers in the whole network like gathering 
statistics,
 spreading and aggregating information in the network, load balancing and
 overlay topology management.
 
-The approach chosen in the rps implementation in gnunet follows the
+The approach chosen in the rps implementation in GNUnet follows the
 Brahms@uref{https://bib.gnunet.org/full/date.html\#2009_5f0} design.
 
 The current state is "work in progress". There are a lot of things that
@@ -350,7 +350,7 @@ and request random peers that will be returned when they 
represent a
 random selection from the whole network with high probability.
 
 An additional feature to the original Brahms-design is the selection of
-sub-groups: The gnunet implementation of rps enables clients to ask for
+sub-groups: The GNUnet implementation of rps enables clients to ask for
 random peers from a group that is defined by a common shared secret.
 (The secret could of course also be public, depending on the use-case.)
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]