gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [gnunet] branch master updated: RPS doc: Fix typo and formu


From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: RPS doc: Fix typo and formulation
Date: Tue, 23 Jul 2019 00:11:12 +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 b92650ab1 RPS doc: Fix typo and formulation
b92650ab1 is described below

commit b92650ab1d79cd1228dd2678bf87b9edbe37328b
Author: Julius B√ľnger <address@hidden>
AuthorDate: Mon Jul 22 22:33:11 2019 +0200

    RPS doc: Fix typo and formulation
---
 doc/handbook/chapters/developer.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/handbook/chapters/developer.texi 
b/doc/handbook/chapters/developer.texi
index c7c4e478e..39f56c7b7 100644
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -8860,9 +8860,9 @@ Preferably using annotations.
 @section RPS Subsystem
 
 In literature, Random Peer Sampling (RPS) refers to the problem of
-reliably@footnote{Reliable in the sense of having no bias, neigther
-spatial, nor spatial nor through malicious activity.} drawing random
-samples from an unstructured p2p network.
+reliably@footnote{"Reliable" in this context means having no bias,
+neither spatial, nor temporal, nor through malicious activity.} drawing
+random samples from an unstructured p2p network.
 
 Doing so in a reliable manner is not only hard because of inherent
 problems but also because of possible malicious peers that could try to

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



reply via email to

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