Update webhooks docs

doc/user/project/integrations/webhooks.md

@@ -6,6 +6,16 @@ Starting from GitLab 8.5:
 - the `project.ssh_url` key is deprecated in favor of the `project.git_ssh_url` key
 - the `project.http_url` key is deprecated in favor of the `project.git_http_url` key
 
+Project webhooks allow you to trigger a URL if for example new code is pushed or
+a new issue is created. You can configure webhooks to listen for specific events
+like pushes, issues or merge requests. GitLab will send a POST request with data
+to the webhook URL.
+
+In most cases, you'll need to setup your own [webhook receiver](#example-webhook-receiver)
+to receive information from GitLab, and send it to another app, according to your needs.
+We already have a [built-in receiver](http://docs.gitlab.com/ce/project_services/slack.html)
+for sending [Slack](https://api.slack.com/incoming-webhooks) notifications _per project_.
+
 ## Overview
 
 [Webhooks](https://en.wikipedia.org/wiki/Webhook) are "_user-defined HTTP
@@ -16,13 +26,13 @@ configured for the webhook. The action taken may be anything.
 Common uses are to trigger builds with continuous integration systems or to
 notify bug tracking systems.
 
-Webhooks are available **per project** for GitLab Community Edition,
+Webhooks can be used to update an external issue tracker, trigger CI jobs,
+update a backup mirror, or even deploy to your production server.
+They are available **per project** for GitLab Community Edition,
 and **per project and per group** for **GitLab Enterprise Edition**.
 
-In most cases, you'll need to setup your own [webhook receiver](#example-webhook-receiver)
-to receive infomation from GitLab, and send it to another app, according to your needs.
-We already have a [built-in receiver](http://docs.gitlab.com/ce/project_services/slack.html)
-for sending [Slack](https://api.slack.com/incoming-webhooks) notifications _per project_.
+Navigate to the webhooks page by going to your project's
+**Settings ➔ Integrations**.
 
 ## Use-cases
 
@@ -32,19 +42,6 @@ for sending [Slack](https://api.slack.com/incoming-webhooks) notifications _per
 every time an issue is created for a specific project or group within GitLab
 - You can use them to [automatically assign labels to merge requests](https://about.gitlab.com/2016/08/19/applying-gitlab-labels-automatically/).
 
-## Description
-
-Project webhooks allow you to trigger a URL if for example new code is pushed or
-a new issue is created. You can configure webhooks to listen for specific events
-like pushes, issues or merge requests. GitLab will send a POST request with data
-to the webhook URL.
-
-Webhooks can be used to update an external issue tracker, trigger CI jobs,
-update a backup mirror, or even deploy to your production server.
-
-Navigate to the webhooks page by going to your project's
-**Settings ➔ Integrations**.
-
 ## Webhook endpoint tips
 
 If you are writing your own endpoint (web server) that will receive