Repository : ssh://darcs.haskell.org//srv/darcs/ghc On branch : master
http://hackage.haskell.org/trac/ghc/changeset/caa2863cf66bf914a42cd031d7084d6885ecda59 >--------------------------------------------------------------- commit caa2863cf66bf914a42cd031d7084d6885ecda59 Author: Simon Marlow <[email protected]> Date: Thu Nov 24 14:36:33 2011 +0000 Fix markup (non-validate-breaking) >--------------------------------------------------------------- docs/users_guide/safe_haskell.xml | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/users_guide/safe_haskell.xml b/docs/users_guide/safe_haskell.xml index 3575b3c..a8352ae 100644 --- a/docs/users_guide/safe_haskell.xml +++ b/docs/users_guide/safe_haskell.xml @@ -545,7 +545,7 @@ </para> </sect3> - <sec3 id="trustworthy-guarantees"> + <sect3 id="trustworthy-guarantees"> <title>Trustworthy Requirements</title> <indexterm><primary>trustworthy</primary></indexterm> @@ -554,7 +554,7 @@ exposed by its export list) can't be used in an unsafe manner. This mean that symbols exported should respect type safety and referential transparency. - </sec3> + </sect3> <sect3 id="safe-package-trust"> <title>Package Trust</title> @@ -582,7 +582,7 @@ </sect2> - <sec2 id="safe-inference"> + <sect2 id="safe-inference"> <title>Safe Haskell Inference</title> <indexterm><primary>safe inference</primary></indexterm> @@ -619,7 +619,7 @@ user of the library would have to wrap it in a shim that simply re-exported your API through a trustworthy module, an annoying practice. </para> - </sec2> + </sect2> <sect2 id="safe-flag-summary"> <title>Safe Haskell Flag Summary</title> _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
