Rework the Monoid explanation when referring to its newtypes

Author: JordanMartinez

src/Data/Monoid.purs

@@ -32,16 +32,15 @@ import Type.Data.RowList (RLProxy(..))
 -- | ### Newtypes for Monoid
 -- |
 -- | Some types (e.g. `Int`, `Boolean`) can implement multiple law-abiding
--- | instances for `Monoid`. For example, `<>` could be `+` and `mempty` could
--- | be `0`. Likewise, `<>` could be `*` and `mempty` could be `1`.
--- | To workaround these ambiguous situations, one should use newtypes
--- | to specify which instance should be used:
--- | - `Additive`: use `Semiring`'s `plus`/`+` and `zero` for `<>` and `mempty`.
--- | - `Multiplicative`: use `Semiring`'s `mul`/`*` and `one` for `<>` and `mempty`.
--- | - `Conj`: use `HeytingAlgebra`'s `conj`/`&&` and `tt` for `<>` and `mempty`.
--- | - `Disj`: use `HeytingAlgebra`'s `disj`/`||` and `ff` for `<>` and `mempty`.
--- | - `Endo`: use `Category`'s `compose`/`<<<` and `identity` for `<>` and `mempty`.
--- | - `Dual`: use `Category`'s `composeFlipped`/`>>>` and `identity` for `<>` and `mempty`.
+-- | instances for `Monoid`. Let's use `Int` as an example
+-- | 1. `<>` could be `+` and `mempty` could be `0`
+-- | 2. `<>` could be `*` and `mempty` could be `1`.
+-- |
+-- | To clarify these ambiguous situations, one should use the newtypes
+-- | defined in `Data.Monoid.<NewtypeName>` modules.
+-- |
+-- | In the above ambiguous situation, we could use `Additive`
+-- | for the first situation or `Multiplicative` for the second one.
 class Semigroup m <= Monoid m where
   mempty :: m