From 539d0fc2c0f89f765e92e033be9f0fec4f67ddc6 Mon Sep 17 00:00:00 2001
From: Sebastian Graf <SebastianGraf@t-online.de>
Date: Sun, 15 May 2016 16:41:22 +0200
Subject: [PATCH] One back tick too much

... that broke a code block.
---
 doc/faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/faq.md b/doc/faq.md
index 0221d8f053..1a2011cb96 100644
--- a/doc/faq.md
+++ b/doc/faq.md
@@ -93,7 +93,7 @@ $ stack exec -- cabal exec -- cabal <command>
 However, virtually all `cabal` commands have an equivalent in stack, so this should not be necessary. In particular, `cabal` users may be accustomed to the `cabal run` command. In stack:
 ```
 $ stack build && stack exec <program-name>
-````
+```
 Or, if you want to install the binaries in a shared location:
 ```
 $ stack install