Merge pull request #388 from jhrcek/jhrcek/various-fixes

Fix few linguistic and rendering issues

Author: david-christiansen

message-index/messages/GHC-03272/bidi-comment/index.md

@@ -15,6 +15,6 @@ BiDi.hs:3:26: warning: [-Wunicode-bidirectional-format-characters] [GHC-03272]
 
 ## Explanation
 
-The phrase "bidirectional formatting" is surrounded by `U+202E RIGHT-TO-LEFT OVERRIDE (RLO)` and `U+202C POP DIRECTIONAL FORMATTING (PDF)` characters in the code that causes the warning to be emitted.
+The phrase "bidirectional format" is surrounded by `U+202E RIGHT-TO-LEFT OVERRIDE (RLO)` and `U+202C POP DIRECTIONAL FORMATTING (PDF)` characters in the code that causes the warning to be emitted.
 In software with good support for bidirectional text, the resulting comment reads "This comment contains tamrof lanoitceridib chars".
 When bidirectional layout is intended, the warning should be disabled; if bidirectional layout is not intended, the control characters should be removed.

message-index/messages/GHC-04924/example1/index.md

@@ -1,5 +1,5 @@
 ---
-title: Unknown flag in  {-\# OPTIONS_GHC \#-} pragma
+title: 'Unknown flag in  {-# OPTIONS_GHC #-} pragma'
 ---
 
 A flag was found in the `OPTIONS_GHC` pragma that was not known.

message-index/messages/GHC-04924/index.md

@@ -1,6 +1,6 @@
 ---
 title: Unknown flag in GHC options pragma
-summary:  Unknown flag in  {-\# OPTIONS_GHC \#-} pragma.
+summary:  'Unknown flag in  {-# OPTIONS_GHC #-} pragma.'
 severity: error
 introduced: 9.6.1
 ---

message-index/messages/GHC-39999/index.md

@@ -6,4 +6,4 @@ severity: error
 ---
 
 This error happens when an expression in the code has a type constraint (e.g. `Eq a => a -> a`) requiring an instance of a type class but GHC can‘t find it.
-This most commonly happens for two reasons: Either the type is to polymorphic (i.e. general) e.g. `forall a. a` and there is no type signature declaring that the type should have the instance. Or the type is specific e.g. `Bool`, but there is no instance for the desired type class defined for this type.
+This most commonly happens for two reasons: Either the type is too polymorphic (i.e. general) e.g. `forall a. a` and there is no type signature declaring that the type should have the instance. Or the type is specific e.g. `Bool`, but there is no instance for the desired type class defined for this type.

message-index/messages/GHC-47854/example2/index.md

@@ -5,7 +5,7 @@ title: Duplicate field export
 The module `Example` exports the symbol `answer` twice.
 In addition to the explicit entry in the export list it's also exported by `Example(..)`.
 
-To avoid the warning, remove one of the duplicated mention.
+To avoid the warning, remove one of the duplicated mentions.
 
 ## Error Message
 

message-index/messages/GHC-53786/case-expr-in-do-block/index.md

@@ -4,7 +4,7 @@ title: Case expression in do-block
 
 The expression in one branch of the case expression is a `do`-block that's missing a `do`. This triggers a corner case in the grammar of Haskell, and the `case`-expression is interpreted as the pattern part of a bind statement in the top-level `do`-block. 
 
-More details are available at https://gitlab.haskell.org/ghc/ghc/-/issues/984
+More details are available [on the GHC issue tracker, issue #984](https://gitlab.haskell.org/ghc/ghc/-/issues/984).
 
 ## Error Message
 

message-index/messages/GHC-69158/example/index.md

@@ -20,7 +20,7 @@ Greeting.hs:3:5: error: [GHC-69158]
 
 ## Explanation
 
-This examples defines the modules `World` and `Universe`, both of which export
+This example defines the modules `World` and `Universe`, both of which export
 an identifier named `greeting`. The `Greeting` module then imports `World` and
 `Universe` qualified, meaning it can use both identifiers named `greeting` in
 the body of `bothGreetings` without any ambiguity. However, the export of both

message-index/messages/GHC-69925/index.md

@@ -5,5 +5,5 @@ severity: error
 introduced: 9.6.1
 ---
 
-When pattern matching, unboxed string literals (with the [MagicHash](https://downloads.haskell.org/ghc/latest/docs/html/users_guide/exts/magic_hash.html?highlight=magichash) postfix) are not allowed. Unboxed string literals are essentially C strings allocated outside of the Haskell heap, and they evaluate to pointers to the resulting strings. Thus,`"foo"#` is of type `Addr#`. While `eqAddr#` can be used to compare these pointers, two identically-written unboxed string literals typically do not point the same address.
+When pattern matching, unboxed string literals (with the [MagicHash](https://downloads.haskell.org/ghc/latest/docs/html/users_guide/exts/magic_hash.html?highlight=magichash) postfix) are not allowed. Unboxed string literals are essentially C strings allocated outside of the Haskell heap, and they evaluate to pointers to the resulting strings. Thus,`"foo"#` is of type `Addr#`. While `eqAddr#` can be used to compare these pointers, two identically-written unboxed string literals typically do not point to the same address.
 

message-index/messages/GHC-70712/index.md

@@ -5,4 +5,4 @@ severity: error
 introduced: 9.6.1
 ---
 
-The double-dot syntax, which is part of the `RecordWildCards` extension, is not allowed as part of a record update, whether the extension is turned on or not.
+The double-dot syntax, which is part of the [`RecordWildCards`](https://ghc.gitlab.haskell.org/ghc/doc/users_guide/exts/record_wildcards.html) extension, is not allowed as part of a record update, whether the extension is turned on or not.

message-index/messages/GHC-75356/index.md

@@ -6,4 +6,4 @@ flag: -Wdodgy-imports
 introduced: 9.6.1
 ---
 
-When exporting identifiers from a module, all in-scope constructors (for a type) or the in-scope methods (for a typeclass) can also be exported with the `T(..)` syntax. However, if `T` does not have in-scope constructors - the type is being re-exported and does not have its constructors imported) or it has no constructors - then this export item suggests that the programmer intended for `T` to have in-scope constructors/methods when it has none.
+When exporting identifiers from a module, all in-scope constructors (for a type) or the in-scope methods (for a typeclass) can also be exported with the `T(..)` syntax. However, if `T` does not have in-scope constructors (the type is being re-exported and does not have its constructors imported) or it has no constructors - then this export item suggests that the programmer intended for `T` to have in-scope constructors/methods when it has none.