doc/faq/fork.md: Various small changes

Apply a few changes that hopefully improve the "Did you fork the Nagios
Plugins?" FAQ item a bit.

1 files changed, 33 insertions, 30 deletions

diff --git a/web/input/doc/faq/fork.md b/web/input/doc/faq/fork.md
index 5057b80..4aab4f9 100644
--- a/web/input/doc/faq/fork.md
+++ b/web/input/doc/faq/fork.md
@@ -4,7 +4,7 @@ parent: FAQ
 
 # Did you fork the Nagios Plugins?
 
-TL;DR: No.  They forked us.
+Short answer: No.  They forked us.
 
 Long answer:
 
@@ -17,35 +17,38 @@ important anyway.
 
 However, because you asked, here's our view on the happenings.
 
-Originally, there was a Nagios Plugins project that was maintained by us;
-i.e., a [team][team] of volunteers not affiliated with [Nagios
-Enterprises][enterprises].  In 2011, we transferred the `nagios-plugins.org`
-domain to Nagios Enterprises on their request.  This transfer was coupled with
-an [agreement][agreement] that we would continue to run the project
-independently.  Early in 2014, Nagios Enterprises copied most of our web site
-and changed the DNS records to point to their web space instead, which then
-served a slightly modified version of our site including the tarballs we
-created.  This was done without prior notice.  Presumably, their
-[reasoning][reasoning] for this move was that they weren't happy with us
-[mentioning Icinga and Shinken][mentioning] on our home page.
-
-So, today there are two projects:
-
-One driven by the team that lost its domain, but that did the actual
-maintenance work in the past, and that continues to maintain the same project
-with the same infrastructure (e.g., the GitHub [repositories][repositories]
-and [trackers][trackers], the [mailing lists][support], and the [automated
-test builds][tests]) under the new name.
-
-The other project is driven by the company that controls the domain.
-
-So, if you ask us (as you did by definition when reading this): They clearly
-forked us, not vice versa.  We just see two differences to a "typical" fork
-which makes this case less obvious:
-
-1. The project that has been forked didn't own its domain name.
-2. The project that performed the fork did so without showing any previous
-   development activities.
+* Originally, there was a Nagios Plugins project that was maintained by us;
+  i.e., a [team][team] of volunteers not affiliated with [Nagios
+  Enterprises][enterprises].
+* In 2011, we transferred the `nagios-plugins.org` domain to Nagios
+  Enterprises on their request.  This transfer was coupled with an
+  [agreement][agreement] that we would continue to run the project
+  independently.
+* Early in 2014, Nagios Enterprises copied most of our web site and changed
+  the DNS records to point to their web space instead, which then served a
+  slightly modified[^changed-site] version of our site, including the tarballs
+  we created.  This was done without prior notice.  Presumably, their
+  [reasoning][reasoning] for this move was that we [mentioned Icinga and
+  Shinken][mentioning] on our home page.
+
+So today, there are two projects:
+
+* One driven by the company that controls the domain.
+* The other one driven by the team that lost its domain, but that did the
+  actual maintenance work in the past, and that continues to maintain the same
+  project with the same infrastructure (e.g., the GitHub
+  [repositories][repositories] and [trackers][trackers], the [mailing
+  lists][support], and the [automated test builds][tests]) under the new name.
+
+Thus, in our view, they clearly forked us, not vice versa.  We just see two
+differences to most other forks, which make this case less obvious:
+
+* The project that has been forked didn't own its domain name.
+* The project that performed the fork did so without showing any previous
+  development activities.
+
+[^changed-site]: In the meantime, they changed the contents and design of
+                 parts of their web site.
 
 [nagios-plugins]: http://www.nagios-plugins.org/ "Nagios Plugins"
 [monitoring-plugins]: index.html "Monitoring Plugins"