From: ng0 <ng0@infotropique.org>
Date: Wed, 6 Sep 2017 08:11:56 +0000 (+0000)
Subject: doc: gnunet-c-tutorial: done?
X-Git-Tag: gnunet-0.11.0rc0~121
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=706017af17667401fb5d555fc9b789a2525eb642;p=oweals%2Fgnunet.git

doc: gnunet-c-tutorial: done?
---

diff --git a/doc/gnunet-c-tutorial.texi b/doc/gnunet-c-tutorial.texi
index 46ad98480..880364444 100644
--- a/doc/gnunet-c-tutorial.texi
+++ b/doc/gnunet-c-tutorial.texi
@@ -1122,7 +1122,7 @@ running @command{configure}. More details about logging can be found under
 @uref{https://gnunet.org/logging}.
 
 You should also probably enable the creation of core files, by setting
-@code{ulimit}, and echo'ing 1 into @file{/proc/sys/kernel/core\_uses\_pid}.
+@code{ulimit}, and echo'ing @code{1} into @file{/proc/sys/kernel/core\_uses\_pid}.
 Then you can investigate the core dumps with @command{gdb}, which is often
 the fastest method to find simple errors.