gnunet

commit 3bdb01b86cfb632e5f976e3b91c6885504de6694
parent b08dbfe7c216533fc1da2d1311d5786ae8db1087
Author: Schanzenbach, Martin <martin.schanzenbach@aisec.fraunhofer.de>
Date:   Tue, 11 Sep 2018 15:05:59 +0200

fix docs

Diffstat:
M
doc/documentation/chapters/user.texi
 | 
15
+++++++++++----

1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
@@ -1983,8 +1983,15 @@ This behaviour is _exactly the same_ as with other IdPs.
 @node Using the OpenID-Connect IdP
 @subsection Using the OpenID-Connect IdP
 
-@node Preliminaries
-@subsection Preliminaries
+@menu
+* Setting up reclaim.io::
+* For Users::
+* For Service Providers::
+@end menu
+
+
+@node Setting up reclaim.io
+@subsubsection Setting up reclaim.io
 
 @example
 $ gnunet-identity -C id
@@ -2024,7 +2031,7 @@ server @{
 This will expose the REST API of GNUnet at https://reclaim.id/api.
 
 @node For Users
-@subsection For Users
+@subsubsection For Users
 
 To use the OpenID Connect Identity Provider as an end user, you must first intall the User Interface from TODOINSERTURLHERE.
 
@@ -2050,7 +2057,7 @@ server @{
 You can thest your setup by accessing https://reclaim.id in your browser through the GNS proxy.
 
 @node For Service Providers
-@subsection For Service Providers
+@subsubsection For Service Providers
 
 To setup an OpenID Connect client, it must first be registered.
 In reclaim, client registration is done by creating a client identity and adding the redirect URI and client description into its namespace: