Merge pull request #3144 from DebianWall/guaketilda

[i3/i3] / docs / hacking-howto

diff --git a/docs/hacking-howto b/docs/hacking-howto
index 9c89947b280d99c2702ad4360ba70d8f2cf0e1c8..2ca44a5ffadff9acec79766f4a1a4e8a94ad76fa 100644 (file)
--- a/docs/hacking-howto
+++ b/docs/hacking-howto
@@ -8,9 +8,7 @@ touching i3’s source code. It should contain all important information to help
 you understand why things are like they are. If it does not mention something
 you find necessary, please do not hesitate to contact me.
 
-== Using git / sending patches
-
-=== How to build?
+== Building i3
 
 You can build i3 like you build any other software package which uses autotools.
 Here’s a memory refresher:
@@ -23,7 +21,7 @@ Here’s a memory refresher:
 (The autoreconf -fi step is unnecessary if you are building from a release tarball,
  but shouldn’t hurt either.)
 
-==== Build system features
+=== Build system features
 
 * We use the AX_ENABLE_BUILDDIR macro to enforce builds happening in a separate
   directory. This is a prerequisite for the AX_EXTEND_SRCDIR macro and building
@@ -51,11 +49,11 @@ Here’s a memory refresher:
 * Coverage reports are now generated using “make check-code-coverage”, which
   requires specifying --enable-code-coverage when calling configure.
 
-=== Introduction
+== Using git / sending patches
 
 For a short introduction into using git, see
-http://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
-or, for more documentation, see http://git-scm.com/documentation
+https://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
+or, for more documentation, see https://git-scm.com/documentation
 
 Please talk to us before working on new features to see whether they will be
 accepted. A good way for this is to open an issue and asking for opinions on it.
@@ -158,7 +156,7 @@ workspace, the split container we are talking about is the workspace.
 
 To get an impression of how different layouts are represented, just play around
 and look at the data structures -- they are exposed as a JSON hash. See
-http://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
+https://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
 example.
 
 == Files