gnunet-svn
[Top][All Lists]
Advanced

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

[gnunet-scheme] 05/05: doc: Fix cross-reference from NSE to configuratio


From: gnunet
Subject: [gnunet-scheme] 05/05: doc: Fix cross-reference from NSE to configuration.
Date: Thu, 01 Sep 2022 15:39:59 +0200

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

maxime-devos pushed a commit to branch master
in repository gnunet-scheme.

commit 6853e8263f8d32a8b945f978bbe2f8da47ea572f
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Thu Sep 1 15:39:04 2022 +0200

    doc: Fix cross-reference from NSE to configuration.
    
    * doc/configuration.tm: Insert label.
    * doc/network-size-estimation.tm: Use it, and use semantic tags.
---
 doc/configuration.tm           | 13 +++++++------
 doc/network-size-estimation.tm | 11 +++++------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/doc/configuration.tm b/doc/configuration.tm
index 3ac8261..b86ed42 100644
--- a/doc/configuration.tm
+++ b/doc/configuration.tm
@@ -6,12 +6,13 @@
 
 <\body>
   There are a number of modules for accessing GNUnet
-  configurations<index|configuration>.<space|1em>Firstly, there is <scm|(gnu
-  gnunet config db)><index|(gnu gnunet config db)>, which is the module
-  library code would typically use.<space|1em>For testing, one can create an
-  empty configuration with the procedure 
<scm|hash-\<gtr\>configuration><index|hash-\<gtr\>configuration>
-  from that module and <scm|make-hashtable> from <scm|(rnrs hashtables)>,
-  using <scm|hash-key><index|hash-key> as hash function and
+  configurations<index|configuration><label|configuration>.<space|1em>Firstly,
+  there is <scm|(gnu gnunet config db)><index|(gnu gnunet config db)>, which
+  is the module library code would typically use.<space|1em>For testing, one
+  can create an empty configuration with the procedure
+  <scm|hash-\<gtr\>configuration><index|hash-\<gtr\>configuration> from that
+  module and <scm|make-hashtable> from <scm|(rnrs hashtables)>, using
+  <scm|hash-key><index|hash-key> as hash function and
   <scm|key=?><index|key=?> as comparison function:
 
   <\scm-code>
diff --git a/doc/network-size-estimation.tm b/doc/network-size-estimation.tm
index d2f6ac1..9167a27 100644
--- a/doc/network-size-estimation.tm
+++ b/doc/network-size-estimation.tm
@@ -10,12 +10,11 @@
   peers.<space|1em>The module <scm|(gnu gnunet nse client)><index|(gnu gnunet
   nse client)> can be used to interact with this service.<space|1em>The
   connection is made with the procedure 
<scm|connect><subindex|connect|NSE><label|nse:connect>,
-  which is accepts a <with|font-shape|italic|configuration> (see
-  <todo|reference>) and some optional keyword arguments.<space|1em>This
-  procedure can be called as <scm|(connect config #:updated updated
-  #:connected connected #:disconnected disconnected)>.<space|1em>It returns a
-  <with|font-shape|italic|NSE server object><index|NSE server
-  object><subindex|server object|NSE>.
+  which is accepts a <em|<reference|configuration>> and some optional keyword
+  arguments.<space|1em>This procedure can be called as <scm|(connect config
+  #:updated updated #:connected connected #:disconnected
+  disconnected)>.<space|1em>It returns a <with|font-shape|italic|NSE server
+  object><index|NSE server object><subindex|server object|NSE>.
 
   The connection is made asynchronuously; the thunk <var|connected> will be
   called when the connection has actually been made.<space|1em>Whenever a new

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

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