# HG changeset patch
# User Wuzzy
# Date 1522842060 -3600
# Node ID 6ea7b43554b871e9ff9b30ecc7fa392f63fbfd7f
# Parent  1cc36d9f13945e9772aa15bfdb51392d5e5d87dd
Releasing: fix syntax

diff -r 1cc36d9f1394 -r 6ea7b43554b8 Releasing.wiki
--- a/Releasing.wiki	Wed Apr 04 13:39:56 2018 +0200
+++ b/Releasing.wiki	Wed Apr 04 12:41:00 2018 +0100
@@ -1,7 +1,8 @@
 #summary How releases are done in Hedgewars
+= Relasing Hedgewars =
 This page is a checklist of things to do in order to do a proper Hedgewars release.
 
-## Getting ready for release
+== Getting ready for release ==
 
  * Bump protocol number
  * Bump Hedgewars version number (if it hasn't already)
@@ -11,7 +12,7 @@
     * For Lua: Run `tools/update_lua_locale_files.sh` and grab a coffee
  * Announce string freeze in News and wait
  
-## Releasing
+== Releasing ==
 
  * Add a tag for the relevant commit
  * Create a Windows build (usually done by unC0Rr)
@@ -24,7 +25,7 @@
      * In lobby, use command `/global Hedgewars X.Y.Z has just been released!` (requires server admin rights)
  * Notify package managers of GNU/Linux distributions
  
-## For release candidates
+== For release candidates ==
 
  * Create a Windows build
  * Remember the commit ID to which the release canditate refers to