Fix comments

Signed-off-by: Mathias Kende <mathias.kende@mistral.ai>

Author: mathias-kende

docs/content/multiprocess/_index.md

@@ -10,10 +10,12 @@ it's common to have processes rather than threads to handle large workloads.
 To handle this the client library can be put in multiprocess mode.
 This comes with a number of limitations:
 
-- Registries can not be used as normal
+- Registries can not be used as normal:
+  - all instantiated metrics are collected
   - Registering metrics to a registry later used by a `MultiProcessCollector`
     may cause duplicate metrics to be exported
-  - Filtering on metrics works but might be inefficient
+  - Filtering on metrics works if and only if the constructor was called with
+    `support_collectors_without_names=True` and it but might be inefficient.
 - Custom collectors do not work (e.g. cpu and memory metrics)
 - Gauges cannot use `set_function`
 - Info and Enum metrics do not work