[gnome-shell-extensions/wip/fmuellner/markdown: 2/2] Update HACKING as well

[Florian Müllner <fmuellner src gnome org>]

commit 064a02a4097366bbdf1bcbe0c6f9d92c84b1cc47
Author: Florian Müllner <fmuellner gnome org>
Date:   Sat Nov 25 03:52:27 2017 +0100

    Update HACKING as well

 HACKING => HACKING.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/HACKING b/HACKING.md
similarity index 77%
rename from HACKING
rename to HACKING.md
index 3bc2444..ca40429 100644
--- a/HACKING
+++ b/HACKING.md
@@ -1,4 +1,4 @@
---- Creating a New Extension ---
+## Creating a New Extension
 
 To create a new extension, add a subdirectory in extensions.
 Then create a Makefile.am like the one in example, replacing
@@ -15,12 +15,10 @@ The Gettext domain you should choose is gnome-shell-extensions,
 not gnome-shell, unless you're sure there is the string you
 need in gnome-shell.
 
---- Coding Style ---
+## Coding Style
 
-Generally, we follow GJS coding style (you can find it at
-http://git.gnome.org/browse/gjs/tree/doc/Style_Guide.txt), which
-in short is: indent 4 spaces, no tabs, space after comma, no space
-after function call.
+Generally, we follow [GJS coding style][coding-style], which in short is:
+indent 4 spaces, no tabs, space after comma, no space after function call.
 
 The Emacs mode line for this
 /* -*- mode: js2; js2-basic-offset: 4; indent-tabs-mode: nil -*- */
@@ -29,3 +27,5 @@ Imports should be at the top, in two groups, one for standard
 imports (like imports.lang or imports.dbus) and introspection,
 the other for Shell API. Within the same group, put everything
 in alphabetic order.
+
+[coding-style]: GNOME/gjs/doc/Style_Guide.txt