[GNUnet-SVN] [www] branch master updated: p ul -> ul

[gnunet]

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

ng0 pushed a commit to branch master
in repository www.

The following commit(s) were added to refs/heads/master by this push:
     new 3442b1c  p ul -> ul
3442b1c is described below

commit 3442b1c3c1f501372e85af92472cc1c7662cdc8c
Author: ng0 <address@hidden>
AuthorDate: Thu Jul 11 13:57:34 2019 +0000

    p ul -> ul
---
 template/engage.html.j2 | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/template/engage.html.j2 b/template/engage.html.j2
index 6d2cadb..2fa2fe9 100644
--- a/template/engage.html.j2
+++ b/template/engage.html.j2
@@ -53,17 +53,17 @@
       </p>
      <h2>Report bugs!</h2>
       <p>
-        While using GNUnet you will find bugs. Here are some notes on how to 
do that the most effective way: 
-          <ul>
-            <li>Run 'gnunet-bugreport'</li>
-            <li>Report the output into our <a 
href="https://bugs.gnunet.org/";>bug tracker</a>. Add more details e.g. what 
happened and what you expected to happen. </li>
-            <li>If you do not want to use the public bug tracker, you can also 
eMail to address@hidden.</li>
-            <li>Please inform us if your operating system or package manager 
applies any vendor changes to GNUnet which you know about (to exclude potential 
problems introduced by third parties).</li>
-            <li>Wait until your bug report is acknowledged/replied to. Note 
that only volunteers work on this, responses may take a while.</li>
-            <li>Please follow up with eventual questions about the bug. </li>
-            <li>Once a fix is there: Check if it's working as expected, so 
that we can properly close the bug report and/or give you credits :)</li>
-         </ul>
+        While using GNUnet you will find bugs. Here are some notes on how to 
do that the most effective way:
       </p>
+      <ul>
+        <li>Run 'gnunet-bugreport'</li>
+        <li>Report the output into our <a href="https://bugs.gnunet.org/";>bug 
tracker</a>. Add more details e.g. what happened and what you expected to 
happen. </li>
+        <li>If you do not want to use the public bug tracker, you can also 
eMail to address@hidden.</li>
+        <li>Please inform us if your operating system or package manager 
applies any vendor changes to GNUnet which you know about (to exclude potential 
problems introduced by third parties).</li>
+        <li>Wait until your bug report is acknowledged/replied to. Note that 
only volunteers work on this, responses may take a while.</li>
+        <li>Please follow up with eventual questions about the bug. </li>
+        <li>Once a fix is there: Check if it's working as expected, so that we 
can properly close the bug report and/or give you credits :)</li>
+      </ul>
     <h2>Contribute!</h2>
       <p>
         There are various ways to contribute. We especially need coders with C 
skills and knowledge of crypto. Development work on this this website, it's 
translations, the bibliography, our wide documentation, and other efforts are 
most welcome, too.<br>

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