diff --git a/gitea2rss.1.adoc b/gitea2rss.1.adoc
index e2a9a6f..e8fff6f 100644
--- a/gitea2rss.1.adoc
+++ b/gitea2rss.1.adoc
@@ -2,7 +2,7 @@
 :doctype:       manpage
 :Author:        tastytea
 :Email:         tastytea@tastytea.de
-:Date:          2019-04-17
+:Date:          2019-04-18
 :Revision:      0.0.0
 :man source:    gitea2rss
 :man version:   {revision}
@@ -28,21 +28,23 @@ slash. For example: _https://git.example.com_. The *QUERY_STRING* must contain
 _repo=user/project_. The feed-URL for alice's project, cooltool, would be:
 `https://rss.example.com/?repo=alice/cooltool`.
 
+The generated RSS feed contains the *channel* elements _title_, _link_,
+_description_, _generator_ and _lastBuildDate_ and the *item* elements _title_,
+_link_, _guid_, _pubDate_ and _description_. Since Gitea has no individual pages
+for each release, _link_ elements in *item* are set to the overview page for
+releases.
+
+== GITEA INTEGRATION
+
 You can let Gitea automatically insert links to your RSS feeds by editing
 `${GITEA_CUSTOM}/templates/custom/header.tmpl` and putting something like
 this in it:
 
 [source,html]
 ----
-<link rel="alternate" type="application/rss+xml" title="Releases of {{.Repository.Name}}" href="https://rss.example.com/?repo={{.Repository.Owner.Name}}/{{.Repository.Name}}" />
+{{if .Repository.Name}}<link rel="alternate" type="application/rss+xml" title="Releases of {{.Repository.Name}}" href="https://rss.example.com/?repo={{.Repository.Owner.Name}}/{{.Repository.Name}}" />{{end}}
 ----
 
-The generated RSS feed contains the *channel* elements _title_, _link_,
-_description_, _generator_ and _lastBuildDate_ and the *item* elements _title_,
-_link_, _guid_, _pubDate_ and _description_. Since Gitea has no individual pages
-for each release, _link_ elements in *item* are set to the overview page for
-releases.
-
 == PROXY SERVERS
 
 Since gitea2rss is built on libcurl, it respects the same proxy environment