fix links in readme

README.md

@@ -3,7 +3,7 @@
 ## Usage
 
 Install via stack similar as xmonad and xmonad-contrib,
-see e.g. [brianbuccola][this guide].
+see e.g. [this guide][brianbuccola].
 Write `xmonad.hs` as glue code to import modules.
 
 ## Goals of this setup
@@ -22,14 +22,14 @@ Write `xmonad.hs` as glue code to import modules.
       Prevent launching with `<Control>`
     - binding programs to these workspaces (to be implemented)
 - Many keybindings for custom menus lanuching (custom) scripts,
-  e.g. `u` for stuff associated to my [uni-setup][University Setup]
+  e.g. `u` for stuff associated to my [University Setup][uni-setup]
   or `<Esc>` for reboot, hibernate, suspend etc.
   (still many missing)
-- Use [polybar][PolyBar] as status bar
+- Use [PolyBar][polybar] as status bar
 
 ### Implementational
-- Use [ezconfig][EZConfig] for all bindings to simplify code.
-- Use [submap][Submap] for menus.
+- Use [EZConfig][ezconfig] for all bindings to simplify code.
+- Use [Submap][submap] for menus.
 - separation into multiple modules to clean up the main `xmonad.hs` config file
   and increase modularization/reusability.
   E.g., it is now trivial to remove university setup keys or bind the submenu to another key.
@@ -42,7 +42,7 @@ Write `xmonad.hs` as glue code to import modules.
 - Pack modules into `.cabal` package.
   This ensures that `xmonad-custom` can be installed just as `xmonad` or `xmonad-contrib`
   (e.g. via Stack) and `xmonad.hs` can conveniently import all my stuff.
-  In particular, no [build-script][custom build script] is needed to build `xmonad`.
+  In particular, no [custom build script][build-script] is needed to build `xmonad`.
 - Use [xmonad-dbus][xmonad-dbus] for communication with PolyBar.
 
 ## Non-goals