summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Seidel <gridaphobe@gmail.com>2016-01-22 16:16:46 +0100
committerBen Gamari <ben@smart-cactus.org>2016-01-22 18:50:27 +0100
commit6e5f8285005895fe4f1915ddea99b72f8ee91834 (patch)
tree49ce035ee80c7b870f907fc3fe4fd34bb26ffb44
parent65881c014f81f62f90dcb0977528411010b1d1a7 (diff)
downloadhaskell-6e5f8285005895fe4f1915ddea99b72f8ee91834.tar.gz
Fix a formatting error in the user's guide
``` ``CallStack``s ``` seems to confuse ReST into producing an extended code-span ``` ``CallStack``\s ``` fixes it, but there may be a better solution Test Plan: build the user's guide and inspect the last paragraph of "9.14.4.5. Implicit CallStacks" Reviewers: bgamari Reviewed By: bgamari Projects: #ghc Differential Revision: https://phabricator.haskell.org/D1798
-rw-r--r--docs/users_guide/glasgow_exts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index 4323b3a3e2..d4ca508142 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -8125,7 +8125,7 @@ ordinary implicit parameters.
``GHC.Stack`` additionally exports a function ``freezeCallStack`` that
allows users to freeze a ``CallStack``, preventing any future push
operations from having an effect. This can be used by library authors
-to prevent ``CallStack``s from exposing unecessary implementation
+to prevent ``CallStack``\s from exposing unecessary implementation
details. Consider the ``head`` example above, the ``myerror`` line in
the printed stack is not particularly enlightening, so we might choose
to surpress it by freezing the ``CallStack`` that we pass to ``myerror``.