diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ghci/ghci.tex | 2 | ||||
| -rw-r--r-- | docs/rts/rts.tex | 2 | ||||
| -rw-r--r-- | docs/users_guide/glasgow_exts.rst | 6 |
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/ghci/ghci.tex b/docs/ghci/ghci.tex index e4fbb0b771..e102cdadd9 100644 --- a/docs/ghci/ghci.tex +++ b/docs/ghci/ghci.tex @@ -122,7 +122,7 @@ visibility. Subsequent sections elaborate who can see what. is @compile@'s private cache of information about package modules. \item {\bf Persistent Linker State (PLS)} (owner: @link@) is - @link@'s private information concerning the the current + @link@'s private information concerning the current state of the (in-memory) executable image. \end{itemize} diff --git a/docs/rts/rts.tex b/docs/rts/rts.tex index 4337bb1f8e..2260b079d1 100644 --- a/docs/rts/rts.tex +++ b/docs/rts/rts.tex @@ -2049,7 +2049,7 @@ The only label associated with a thunk is its info table: \Subsubsection{Byte-code objects}{BCO} -A Byte-Code Object (BCO) is a container for a a chunk of byte-code, +A Byte-Code Object (BCO) is a container for a chunk of byte-code, which can be executed by Hugs. The byte-code represents a supercombinator in the program: when Hugs compiles a module, it performs lambda lifting and each resulting supercombinator becomes a diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst index 6c444cc873..603dbc5eb9 100644 --- a/docs/users_guide/glasgow_exts.rst +++ b/docs/users_guide/glasgow_exts.rst @@ -3583,7 +3583,7 @@ declaration, to generate a standard instance declaration for specified class. GHC extends this mechanism along several axes: * The derivation mechanism can be used separtely from the data type - declaration, using the the `standalone deriving mechanism + declaration, using the `standalone deriving mechanism <#stand-alone-deriving>`__. * In Haskell 98, the only derivable classes are ``Eq``, @@ -6326,7 +6326,7 @@ Overlapping instances In general, as discussed in :ref:`instance-resolution`, *GHC requires that it be unambiguous which instance declaration should be used to -resolve a type-class constraint*. GHC also provides a way to to loosen +resolve a type-class constraint*. GHC also provides a way to loosen the instance resolution, by allowing more than one instance to match, *provided there is a most specific one*. Moreover, it can be loosened further, by allowing more than one instance to match irrespective of @@ -7243,7 +7243,7 @@ defaults to ``*`` if omitted. An example is :: Parameters can also be given explicit kind signatures if needed. We call the number of parameters in a type family declaration, the family's arity, and all applications of a type family must be fully saturated -with respect to to that arity. This requirement is unlike ordinary type synonyms +with respect to that arity. This requirement is unlike ordinary type synonyms and it implies that the kind of a type family is not sufficient to determine a family's arity, and hence in general, also insufficient to determine whether a type family application is well formed. As an |