From 7729e31b1bd0bcff87701808d5ab6c9d2239e778 Mon Sep 17 00:00:00 2001 From: ng0 Date: Wed, 18 Oct 2017 16:03:23 +0000 Subject: [PATCH] attempt to fix buildbot system being super precise about wrong syntax. Inside comment blocks. Wow. --- doc/gnunet-c-tutorial.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/gnunet-c-tutorial.texi b/doc/gnunet-c-tutorial.texi index 2e3069638..432d2b47b 100644 --- a/doc/gnunet-c-tutorial.texi +++ b/doc/gnunet-c-tutorial.texi @@ -364,8 +364,8 @@ PASS: test_gnunet_prefix GNUnet is organized in layers and services. Each service is composed of a main service implementation and a client library for other programs to use the service's functionality, described by an API. This approach is shown in -@c** FIXME: enable this once the commented block below works: -@c** figure~\ref{fig:service}. +@c FIXME: enable this once the commented block below works: +@c figure~\ref fig:service. Some services provide an additional command line tool to enable the user to interact with the service. @@ -373,10 +373,10 @@ Very often it is other GNUnet services that will use these APIs to build the higher layers of GNUnet on top of the lower ones. Each layer expands or extends the functionality of the service below (for instance, to build a mesh on top of a DHT). -@c** FXIME: See comment above. -@c** See figure ~\ref{fig:interaction} for an illustration of this approach. +@c FXIME: See comment above. +@c See figure ~\ref fig:interaction for an illustration of this approach. -@c ** @image{filename[, width[, height[, alttext[, extension]]]]} +@c ** @image filename[, width[, height[, alttext[, extension]]]] @image{images/gnunet-tutorial-service,,5in,Service with API and network protocol,.png} -- 2.25.1