[commit: ghc] ghc-8.2: Correct optimization flags documentation (5eb4a35)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : ghc-8.2
Link       : http://ghc.haskell.org/trac/ghc/changeset/5eb4a35bcc6743fce33eaf42b15d17e48936e41f/ghc

>---------------------------------------------------------------

commit 5eb4a35bcc6743fce33eaf42b15d17e48936e41f
Author: Santiago Munin <santimunin at gmail.com>
Date:   Thu Jun 8 15:03:58 2017 -0400

    Correct optimization flags documentation
    
    In a previous change (commit 4fd6207ec6960c429e6a1bcbe0282f625010f52a),
    the users guide was moved from XML to the RST format. This process
    introduced a typo: "No -O*-type option specified:" was changed to "-O*"
    (which is not correct). This change fixes it.
    
    See result in: https://prnt.sc/fh332n
    
    Fixes ticket #13756.
    
    Reviewers: austin, bgamari
    
    Reviewed By: bgamari
    
    Subscribers: rwbarton, thomie
    
    GHC Trac Issues: #13756
    
    Differential Revision: https://phabricator.haskell.org/D3631
    
    (cherry picked from commit b2b416014e4276ebb660d85c3a612f7ca45ade78)


>---------------------------------------------------------------

5eb4a35bcc6743fce33eaf42b15d17e48936e41f
 docs/users_guide/using-optimisation.rst | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/docs/users_guide/using-optimisation.rst b/docs/users_guide/using-optimisation.rst
index dbdd957..e2e7887 100644
--- a/docs/users_guide/using-optimisation.rst
+++ b/docs/users_guide/using-optimisation.rst
@@ -45,11 +45,9 @@ optimisation to be performed, which can have an impact on how much of
 your program needs to be recompiled when you change something. This is
 one reason to stick to no-optimisation when developing code.
 
-.. ghc-flag:: -O*
-
-    This is taken to mean: “Please compile quickly; I'm not
-    over-bothered about compiled-code quality.” So, for example:
-    ``ghc -c Foo.hs``
+**No ``-O*``-type option specified:** This is taken to mean “Please 
+compile quickly; I'm not over-bothered about compiled-code quality.”
+So, for example, ``ghc -c Foo.hs``
 
 .. ghc-flag:: -O0