feat(docs): Update custom detectors guide

docs/hacking/custom-detector.md

@@ -8,6 +8,8 @@ Detectors are designed to be dynamically loaded by the Misti driver, and they ar
 
 ## Creating a Detector
 
+### Example implementation
+
 You can create a new custom detector by executing Misti with the `--new-detector` option: `misti --new-detector implicitInit`.
 
 This will create the `implicitInit.ts` file, which contains the template code for writing your own custom detector logic leveraging the Misti API.
@@ -46,8 +48,11 @@ export class ImplicitInit extends ASTDetector {
 
 ```
 
-### Testing the detector
-To run Misti with only your new detector, use the `--detectors` option, specifying the path to the detector and the Detector class name: `misti path/to/your/tact.config.json --detectors path/to/implicitInit.ts:ImplicitInit`.
+### Running detector
+To run Misti with only your new detector, use the `--enabled-detectors` (`-de`) option, specifying the path to the detector and the Detector class name:
+```bash
+misti path/to/src/contracts -de path/to/implicitInit.ts:ImplicitInit
+```
 
 That's a good way to test the detector on the first run. You could also use the `--verbose` CLI option and set the environment variable `MISTI_TRACE=1` to facilitate debugging.
 
@@ -62,7 +67,10 @@ After testing the detector, you can specify it in your configuration to enable i
 }
 ```
 
-After this, you could run Misti specifying a path to a custom configuration `misti --config path/to/misti.config.json path/to/your/tact.config.json`.
+After this, you could run Misti specifying a path to a custom configuration which is less verbose when you have a few custom detectors:
+```bash
+misti --config path/to/misti.config.json path/src/contracts
+```
 
 ## Example Detectors