From d81466a0c7d8e62b74a135a5ec01202f01a16cc5 Mon Sep 17 00:00:00 2001
From: Achilleas Pipinellis <axilleas@axilleas.me>
Date: Mon, 22 Feb 2016 01:10:49 +0200
Subject: [PATCH] Reword pages daemon intro

---
 doc/pages/administration.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/doc/pages/administration.md b/doc/pages/administration.md
index 019ead46f67c3..f3340f10ab583 100644
--- a/doc/pages/administration.md
+++ b/doc/pages/administration.md
@@ -44,11 +44,12 @@ probably want to read the [user documentation](README.md).
 ## The GitLab Pages daemon
 
 Starting from GitLab EE 8.5, Pages make use of a separate tool ([gitlab-pages]),
-a simple HTTP server written in Go that serves GitLab Pages with CNAMEs and SNI
-using HTTP/HTTP2. You are encouraged to read its [README][pages-readme] to fully
-understand how it works.
+a simple HTTP server written in Go that can listen on an external IP address
+and provide support for custom domains and custom certificates. The GitLab
+Pages Daemon supports dynamic certificates through SNI and exposes pages using
+HTTP2 by default.
 
-What is supported when using the pages daemon:
+Here is a brief list with what it is supported when using the pages daemon:
 
 - Multiple domains per-project
 - One TLS certificate per-domain
@@ -56,6 +57,9 @@ What is supported when using the pages daemon:
   - Validation of certificate chain
   - Validation of private key against certificate
 
+You are encouraged to read its [README][pages-readme] to fully understand how
+it works.
+
 ---
 
 In the case of custom domains, the Pages daemon needs to listen on ports `80`
-- 
GitLab