diff --git a/docs/configuration.md b/docs/configuration.md
index fb42aca..86b3bc0 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -180,7 +180,8 @@ This is useful if you want to be alerted in case your AS starts announcing somet
 >      group: default
 > ```
 > If in config.yml monitorAS is enabled, you will receive alerts every time a prefix not already part of the prefixes list is announced by AS58302.
-> If AS58302 starts announcing 45.230.23.0/24 an alert will be triggered. This happens because such prefix is not already monitored (it's not a sub prefix of 50.82.0.0/20).
+> 
+>If AS58302 starts announcing 45.230.23.0/24 an alert will be triggered. This happens because such prefix is not already monitored (it's not a sub prefix of 50.82.0.0/20).
 
 You can generate the options block in the prefixes list automatically. Refer to the options `-s` and `-m` in the [auto genere prefixes documentation](prefixes.md#generate).
 
diff --git a/docs/prefixes.md b/docs/prefixes.md
index 261c0d2..07e9334 100644
--- a/docs/prefixes.md
+++ b/docs/prefixes.md
@@ -93,7 +93,7 @@ The `options` entry allows the configuration of additional monitoring options di
 
 #### monitorASns
 
-Allows for generic monitoring (not related to specific prefix) of Autonomous Systems. Please, refer to [monitorAS](configuration.md#monitoras) for more information.
+Allows for generic monitoring (not related to specific prefixes) of Autonomous Systems.
 
 An example of monitorASns configuration is:
 
@@ -107,6 +107,7 @@ monitorASns:
 
 The AS2914 and AS3333 will be monitored. The alerts related to AS2914 will be sent to the "ntt" user group and the alerts for AS3333 to the "ripencc" user group.
 
+The monitor in charge of doing this type of detection is [monitorAS (click for more information)](configuration.md#monitoras).
 
 ### Optimized regular expressions for AS path matching