From 001aa5391cda775188ac06b306dfa78fccb5c2be Mon Sep 17 00:00:00 2001
From: Teo Camarasu <teofilcamarasu@gmail.com>
Date: Sun, 8 Jan 2023 13:04:12 +0000
Subject: [PATCH] Fix formatting in whereFrom docstring

Previously it used markdown syntax rather than Haddock syntax for code quotes
---
 libraries/ghc-internal/src/GHC/Internal/InfoProv.hsc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/libraries/ghc-internal/src/GHC/Internal/InfoProv.hsc b/libraries/ghc-internal/src/GHC/Internal/InfoProv.hsc
index 12384ddb7250..da5f39eca110 100644
--- a/libraries/ghc-internal/src/GHC/Internal/InfoProv.hsc
+++ b/libraries/ghc-internal/src/GHC/Internal/InfoProv.hsc
@@ -94,13 +94,13 @@ peekInfoProv infop = do
     }
 
 -- | Get information about where a value originated from.
--- This information is stored statically in a binary when `-finfo-table-map` is
+-- This information is stored statically in a binary when @-finfo-table-map@ is
 -- enabled.  The source positions will be greatly improved by also enabled debug
--- information with `-g3`. Finally you can enable `-fdistinct-constructor-tables` to
+-- information with @-g3@. Finally you can enable @-fdistinct-constructor-tables@ to
 -- get more precise information about data constructor allocations.
 --
 -- The information is collect by looking at the info table address of a specific closure and
--- then consulting a specially generated map (by `-finfo-table-map`) to find out where we think
+-- then consulting a specially generated map (by @-finfo-table-map@) to find out where we think
 -- the best source position to describe that info table arose from.
 --
 -- @since base-4.16.0.0
-- 
GitLab