[DOC] Make explicit the config path for filtering events from output

Fixes #2820

Author: LeonardoMor

docs/sources/index.md

@@ -128,10 +128,10 @@ application dell_poweredge_cmc[sc4s-network-source] {
 
 ### Filtering events from output
 
-In some cases specific events may be considered "noise" and functionality must be implemented to prevent forwarding of these events to Splunk
-In version 2.0.0 of SC4S a new feature was implemented to improve the ease of use and efficiency of this progress.
+In some cases specific events may be considered "noise" and functionality must be implemented to prevent forwarding of these events to Splunk.
+In version 2.0.0 of SC4S a new feature was implemented to improve the ease of use and efficiency of this process.
 
-The following example will "null_queue" or drop cisco IOS device events at the debug level. Note Cisco does not use the PRI to indicate DEBUG a message filter is required.
+The following `/opt/sc4s/local/config/app_parsers/cisco_ios_debug-postfilter.conf` example will "null_queue" or drop cisco IOS device events at the debug level. Note Cisco does not use the PRI to indicate DEBUG; a message filter is required.
 
 ```c
 block parser cisco_ios_debug-postfilter() {
@@ -239,4 +239,4 @@ sets:
 vendor = < example vendor >
 product = < example product >
 tag = .source.s_EAMPLEVENDOR_EXAMPLEPRODUCT_GROUP01-002
-```
+```